Still having insane processor use / hogging and hence battery drain in/from Mail when connected to the corporarte network and Mail is able to reach MS Exchange.
A moment ago the Mail activity monitor showed no threads active and processing yet Mail was using beyond 150% processor. It started almost immedaitely after I connected to the corporate network via VPN (Cisco flavor) and Mail could reach exchange. It continued for quite a while (say 30 min or more) and then mysteriously settled down.
Mail is still the largest processor pig on my system, whether idling and using 10-20% (100 times more than most) or doing anything and chewing up sometimes beyond 200% (aka more than two processors). Pixelmator, Adobe products and even MS Office with it's nortoriously bad engineering design does not do this.
And, to top it off, it still refuses to quit much of the time.
BUT, as odd as it seams, it is much better in Mavericks than prior. There is progress and for that I am thankful.
Mail Update for Mavericks
[but no mention of Exchange - only Gmail]
I have just installed this update. It updates the Mail database so make a backup first (I use Mail Steward for a separate backup to Time Machine). I have not noticed any difference with my Exchange account (i.e. no worse!)
This is truly outrageous...
I have been using Apple Mail for my Exchange accounts (4-5 of them with totally ~200.000 emails) since Leopard with no problem, either locally (on the same lan as the Exchange server) or remotely (through WAN/ADSL).
The really weird thing is that it used to work perfectly with Mountain Lion on my old Macbook pro, until I got a new 2013 retina Macbook pro (with the same OS version). After that, I started experiencing exactly the same issues as mentioned in this thread; folders go missing, sync stops after fetching only eg. 1500 out of 100.000 messages, random resync of all folders after launch (I even faced a weird issue when all subfolders would suddenly get a "-2" suffix).
I have tried all proposed solutions (though connectivity was never the problem in my case) with no success.
It is a real shame to have to revert to Outlook, wich in my opinion is a disgrace to Mac software, like all the rest of Microsoft products for Mac: unbelievably slow and unresponsive even when performing the simplest tasks (like copy-paste).
For God's sake Apple, plese, plase, PLEASE fix OSX Mail. The issue has been around for more than 6 months now and it is getting frustrating! How are corporate users supposed to switch to Macs when they have to use 3rd party software for simple tasks like mail?
From Macrumours today:
"Apple has seeded the first beta of OS X Mavericks 10.9.1 to developers. The release asks testers to focus on Mail, Graphics Drivers and VoiceOver..."
Hopefully some of those testers have existing porblems with Exchange.
I just stumble on that problem and bang my head on it for a few hours .The solution i have is really not end user solution ,but i think i worth sharing for other admin having the issue
As the corporate system admin , during our exchange migration from exc2010 to 2013 , we did remove imap/pop/smtp old fashion way and move on too full https/rpc and ews setup , and we add move on to hardware ssl offloading with our loadbalancer .
Since everything was working find for all my windows/mac outlook client , thunderbird,entourage ,etc .
We did not realy supected anything network wise .
But after a few hour off tcp/ip profiling ,etc .
We found out that during the ntlm security handshake step 2 was failling with a connection error code i think it was 600 , in the message log from the MACbook , followed by a drop connection . after few test to see where the connection was reset .We found out it was drop by load balancer with a timeout errorr (waiting for initnal client request) just like SYN with no ack . It is drop by the native system of the appliance or the SNORT system that is connected into it we dont know yet.
But the fix was switch back to software iis ssl management ,that remove the unencrypt ,inspect ,rencrypt done by the loadbalancer .
There something there the mac mail client does not like , but most likely to be the add x-forward header
to a faulty ntlm implemantation in mac lion up just like the new mac smb ... can be alot of thing .
So to make it work
Open port 80/443
Full ssl support done on the iis cas server. no hardware ssl offloading or at least with kemp lm-2500, iam yet to try with netscaler or f5 sytem
Configure ews organisaton policy by default they seem not to be.
now i have all mac world client working fine .
as a extra during our test phase we found out that enabling digest login for the EWS folder will break the http conection mode for outlook 2011 for mac .
I have been seeing similar issues with Mail on ML not connecting properly with an Exchange 2007 server, being irresponsive to download mail and, worst of all, after spending 15 minutes to process and classify my mail load into folders, I very often have to redo the whole exercise because Mail doesn't properly communicate my actions with the Exchange server. It is very frustrating to see handled e-mail popping back up in the inbox!
Calendar is giving me headaches also. It typically hangs on the connection with the server, which locks me out of access to the calendar, often for 5 minutes or longer. I don't care that access to the server is slow for calendar items, just want to access my calendar. Why couldn't they decouple the GUI from the communications thread? Never heard of Grand Central Dispatch?
I have found that a good old reboot goes a long way to ameliorate the issues, but I definitely do not want to reboot on a daily basis. This is really a shame and reflects very badly on Apple. I 3-finger salute thee, Apple.
Mail Improvements in OS X 10.9.2
"Exchange reliability: Users with Exchange accounts had found that Mail checked for new messages on launch, but not afterwards; you had to either quit and reopen Mail or take your accounts offline and then check for new messages manually (as described in this Apple support article). That has now been fixed."
Here's hoping it is more than just that issue...