Hi pnoble,

If you dont mind posting, what version of Exchange are you running? Include the SP and CU.

Also, did IT adjust the EWS and IIS settings?

I or my sys admin will let you know tomorrow, Brad. Thanks for your interest.

Paul

Well, whenever was said, using latest Maverics with Exchange 2013 with latest SPs.

Gues what? Why i came here? yup. same problems. and it started right after upgrade to Maverics and didn't stop yet.

sad. very sad. please fix ASAP. people claiming here for 3 months that there is problem within Mail.app and you just trying encounter everybody that this is Exchange problem? DO NOT BELIEVE.

And last. in english my nick something like "Angry beaver". never thought it will be used in such agressive reaction, but i really getting mad if someone trying to make me silly on my mind.

I'd like to add to zloibubr's comment that I too have worked both with Exchange 2010 and 2013 and the same problems are happening in both versions.

It's also worth mentioning that I only upgraded my desktop to Mavericks and still use ML on my laptop. The problems only occur in Mavericks. This is a clear indicator that the problem is not in Exchange, but in the new Mail.

It seems that Apple is not taking the appropriate actions to solve the problem. Apple support usually escalate this problem to engeneering, but an objective answer as to acknowledging as a bug never came (at least to me).

My current option is to go back to ML (I refuse to use the word "downgrade" when comparing ML with Mavs), as some other bugs are also bothering me.

I'd like to add to the din of voices hoping that Apple will address this problem.  I'm running Mavericks on a late 2013 MBPR and have my email hosted via Rackspace Exchange 2010.  Since converting to Mavericks, Mail will stall and essentially lose it's connection to the server.  I get the screen that offers to "Try Again With This Server" and clicking this seems to renew the connection and all is well for a while.  This happens at least 10 times a day, so it is more than a little annoying.  I've checked with Rackspace and they contend the problem is with Mail, not the server.  I've asked several techs on Apple JV and they have no idea.  But, interestingly, those same techs have all said that I SHOULD NOT consider switching to iCloud for my business email activity as it isn't yet reliable enough. I'm beginning to think those of us with this problem are going to have to give up on Mail and use Outlook instead. Not something I want to do, but if Apple isn't going to support Mavericks working on Exchange, I don't see an alternative.

I can confirm the issue, running OSX 10.9.1.

exchange 2013 CU3 (latest release) in combination with mail app 7.1. (1827)

push does not work. fetch setting on 1 minute does work.

iphone/ipad push works great, new email on server, directly delivered on mobile.

I think because the implementation of mail app and iphone/ipad is different, the activesync device registers itself on the exchange server (for remote wipe of the account), there for the exchange server is allways aware of the mobile device.

iphone/ipad uses  /activesync directory with a listner service.

The mail app, uses /EWS (exchange Web Services) what means it communicates stand alone to the exchange server. (like a pull mechanism. with a polling interval.

Outlook 2011 also uses ews, and the push functionality does not work also like your mobile communication. (delay is about 20 tot 30 sec.)

Outlook for windows uses a different technique (MAPI) and communicate with RPC over HTTPS and push is immediately. (uses a listner)

so, i think that or the EWS needs to be changed on the exchange server side to accomodate same principal as activesync (apple/android/windows phone devices)

or

mail app/outlook 2011 need to have a shorter pull interval automaticly configured....

i think microsoft and apple needs to work on this case to figure out the best way....

put your mac mail app client on 1 minute pull, that is the shortest work around.

regards,

Leon

please see this, ews is polling mechnisme based:

http://books.google.nl/books?id=EZwSAAAAQBAJ&pg=PT312&lpg=PT312&dq=exchange+2013 +ews+polling+interval&source=bl&ots=qul6Ay7xnx&sig=BtTPa0c8hufLe0q5Td8q2H02_Ug&h l=nl&sa=X&ei=o0vqUrHLEqOH4AS9oICIBg&ved=0CIEBEOgBMAc#v=onepage&q=exchange%202013 %20ews%20polling%20interval&f=false

see scenario 1; 2nd text block. ews is a pulling mechanism, so the client allways have to initiate the pulling...

hi bradhs, i see that you got more technical knowledge about exchange

about the ews vs rpc (like MAPI is a better understanding).

Mapi is as old as microsoft almost is, they used mapi in the time that exchange came out on the first versions. so mapi communication is figured out. EWS is introduced in 2007 with exchange 2007, so not new and not old.

the RPC communication was mainly based in the early years for internal (domain related) communication, rpc is still used all over microsoft to communicate, with file shares, domain controller sync, sql server communication, like rpc is all over the place and is the backbone of communication.

so what they did is only encapsulation of the rpc protocol in an https packet so they could travel it secure over internet.

lets turn it around, why did outlook 2008/2011/mac mail (all versions) not use a MAPI/rpc side communication?

(political issue, like giving your source code to a another company so the can build/understand i can create something?)

Ok ontopic, i think disabling of throttleing policy's in your environment is not the smartest thing to do, if you got big envirionment with a few honderd mailboxes or more, you can get in to big performance issues.

i m more intressted in how to tweak the policies so ews is working with the new mavericks mail? do you have to right settings? (with exchange shell commands?)

Just in case we feel alone on this issue (as if 32 pages of this thread wouldn't convince you), check out this article on the subject published 2 days ago:

Apple OSX Mavericks Mail App Problems: Fix Crashes, Can't Send Outgoing Emails, Exchange Servers, Inactive Accounts And More [HOW TO]

www.idesigntimes.com/articles/9490/20140128/apple-osx-mavericks-mail-app-problem s-fix-crashes-exchange.htm

Unbelieveable that the problem is so massive, yet Apple support seems to be silent on the issue...at least on this thread.  Any chance you forum guru's can step in and shed some light?

I reported the issues mentioned here and heard back from Apple a few days ago:

Mavericks Mail slowness with Exchange setup

We have a fix for this behavior set for an upcoming 10.9.2 update.  Once this fix is available in a pre-release build I will let you know so you can verify it addresses the issue.

Correct. Hopefully releases to public soon.

After over three months of serious issues for the majority of corporate Mac users, and two interim releases that did nothing to adress the issue, about bloody time, if you ask me! Hopefully 10.9.2 will fix the issue and we can all go back to living our normal digital lives!!

I'm holding my breath on the 10.9.2 update... even if it does fix the issue I have so many issues with the way Apple handled this issue.  The biggest problem is the lack of transparancy from support.

Couldn't agree more, ibrennan. This whole issue could have been put to bed by Apple weeks ago: 'We have identified an issue with Exchange compatibility. We are targeting its resolution in v.10.9.2 with an expected release in Feburary. Our appologies for the inconvenience caused'. End of story.

Instead, nearly 500 posts and 70,000 views here alone with around two dozen discussions on the subject, in total. I'm totally devoted to Apple, own a lot of their products and a great deal of their stock but am truly dissapointed by their lack of responsiveness.

Hallelujah, I'm told the latest beta build of Mavericks fixes the Exchange sendmail (with attachments) problem!!