Exchange servers and Mavericks Mail

Well, from my point of view, I would say that what's happening is that Mail isn't finding your work (Exchange) server but can find your home server, which is the problem I was having. As I have said earlier, deleting your Exchange account, eliminating the EWS folder from your Library, not forgetting to empty the Trash, restarting your mac and then re-establishing your Exchange account ought to do the trick for this problem. Interestingly, I now do not have an EWS folder in my Library, and I think that folder only gets created because more than one conflicting file exists. Kill that folder and you ought to kill the problem.

Sorry about that, peter_watt, I guess I was so caught up in the success of regaining the use of my mail exchange account I didn't realize the massive number of interval posts. I did go back and review, and in case this helps someone, here is my experience.

My issue was initially with NO inbox deliveries, and the above solution (deleting exchange account, rebooting, reinstalling, rebuilding) worked. (Thanks to Karim2u and JLinden7 from way back on page 8). Rebuilding did take quite a while, however.

I had previously experienced slow delivery with exchange in Mountain Lion, and had already followed the suggestion from dianeof oregon and others to not have inbox subfolders, and limit the size of inbox itself by moving older mail to subfolders. This issue continues to be present, as my iOS devices receive mail well before Mail does, and I suppose I have gotten used to the delay. BTW, I recall that I had to rebuild my exchange account after upgrading to Mountain Lion as well, so I really should not have been surprised. Fool me once, fool me again I suppose...

RandyKates seems to have had the inside track in getting a real fix to this issue, and I will be curious to see the outcome. Keep posting, Randy!

Thanks to all and I hope there are indeed better times ahead.

Thanks Arby1. have received two emails from Apple Support over the past weeks saying they have all of my test data, and are in the process of scrubbing that data to make sure there are no contaminants that is causing the issues that we are seeing. Once they can get a clean version of my data set and they still experience all the same issues we have seen they will be able to make quicker progress on a resolution. It is my contention that some of the higher up developers believe the problem is related to something within our own data sets or on the back end of exchange server that is responsible for this problem but we all know that it started with Mavericks and needs to be fixed by Apple.

If anyone has a specific question to ask the developers I would be more than happy to pass those along but I cannot assure you they will answer all of them and certainly not on a timely basis.

Some of the fixes that you guys have found might be of interest to Apple. I have asked them to look at the forums but I am doubtful they would. Those fixes are workarounds as far as I am concerned because I have made a lot of the same adjustments and my system was working fine for a period of time but eventually I started having more and more problems and eventually my whole entire mailbox got corrupted and was unusable.

Happy New Year!

Randy

I've tried all the solutions for getting my subfolders under my inbox in Mail to show up again in Mavericks. The emails are there.....but you just don't see them in any subfolder. Apple told me it's an Exchange problem. I asked them how is this possible if it's working fine in Outlook for Mac? No real answer given. It was working fine in Mountain Lion and all the other predecessors of Mavericks.

My other problem is the limit size of attachments in apple mail. They told me that was a server issue in my office. Same story...I can send the attachment in Outlook for Mac without any problem, but not in Apple Mail. I can send it in my parallels window using Outlook 2013 without any problem as well.

Come on Apple.

Hey Randy:

I've been trolling this forum for weeks (around early December), ever since my Mail stopped working with Mavericks. My issue seems to be a little different. I have an outside POP server for my home email. The email account on that server WILL NOT receive or send email using MAIL - I constantly get a pop-up asking for the account password. If I enter the password, a few seconds later I get the same pop-up in an endless loop. If I cancel the request, I cannot receive or send email. I spent 2.5 hours with Apple Support attempting to solve the issue before the holidays. They ultimately stated my issue is with the server. It isn't, but I was burned out after two hours of no success. Just to be safe, I contacted the admin for the server (I'm not really tech savvy; when I have an issue I can generally pass along helpful information to tech types that can guide me to where I need to go). Server admin assured me that all his business are running off the server and he has had no issues - although hasn't upgraded to Mavericks.

Seems pretty clear the issue is with Mavericks, and it's a pity Apple can't or won't admit it and then fix it. Anyone have some suggestions on how to fix my issue? Support emptied my cache, reinstalled, worked in safe mode, etc., to no avail. I've turned to using Outlook for mail, even though I prefer Apple Mail.

Again, suggestions welcome for fixing for a novice home user, and if the issue can be relayed to Apple I'd be most appreciative.

Johnfx..I followed all of the steps and can now send attachments. However, if the attachment is on the larger size (I tried a 3.6 MB pdf), I still receive the rejection dialogue box, but all I have to do is to select my exchange server and re-send. It works the second time. It is not perfect, but at least I can send attachments now (and get back to work!). Thanks very much for your help.

Rob

Hi Robert+JohnFX.... so far so good indeed.
Robert, please ask the receipient if they received the email twice. That was constantly happening to me. Send email+attachment > Rejection Dialogue > Resend > Gone... but the receipient would tell me that he received it twice. Luckily internal only, but still...

I got the same problem than you since Maverick. I mean, the problem you seem to be happy with it.

We are 4 iMac here in an entreprise and all of them do the same thing since Maverick:

Receiving the rejection dialogue box, I have to select my exchange server and re-send. It works the second time.

That way I loose few minutes because it takes one or 2 minutes before it pop-up. It's causing problem if I send a rush email and have to go in a meeting, the email does'nt leave before the second attempt.

Switch to outlook in Office 2011, or for a simple mail app that works much better but not perfect try Airmail.

These Exchange problems do not affect all, indeed some major contributors on the forum use Exchange successfully. However your problems are real and until a tech reason is given by Microsoft or Apple, you will not get Mavericks Mail to work as it did under Mountain Lion.

I'm posting my console output again - is anyone else getting this?

Randy - have you seen this / any feedback from Apple on this?

8/01/2014 8:38:05.979 pm Mail[44981]: *** Assertion failure in -[MFEWSSyncFolderItemsResponseMessageOperation handleResponseMessage:withObject:], /SourceCache/Mail/Mail-1827/FrameworkTargets/MailFramework/EWS/MFEWSResponseOpe ration.m:573

Received error response that shouldn't apply to Mail: The request timed out. on EWS response <MFEWSSyncFolderItemsResponseMessageOperation: 0x6000002f2680> (EXECUTING)

(

0 MailCore 0x00007fff98205c8c -[MCAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141

1 MailCore 0x00007fff98205afd -[MCAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215

2 Mail 0x00007fff9b2209a1 -[MFEWSResponseOperation handleResponseMessage:withObject:] + 834

3 Mail 0x00007fff9b226b00 -[MFEWSSyncFolderItemsResponseMessageOperation executeOperation] + 409

4 MailCore 0x00007fff98256f0a -[MCMonitoredOperation main] + 211

5 Foundation 0x00007fff9860c591 -[__NSOperationInternal _start:] + 631

6 Foundation 0x00007fff9860c23b __NSOQSchedule_f + 64

7 libdispatch.dylib 0x00007fff8db542ad _dispatch_client_callout + 8

8 libdispatch.dylib 0x00007fff8db587ff _dispatch_async_redirect_invoke + 154

9 libdispatch.dylib 0x00007fff8db542ad _dispatch_client_callout + 8

10 libdispatch.dylib 0x00007fff8db5609e _dispatch_root_queue_drain + 326

11 libdispatch.dylib 0x00007fff8db57193 _dispatch_worker_thread2 + 40

12 libsystem_pthread.dylib 0x00007fff946b1ef8 _pthread_wqthread + 314

13 libsystem_pthread.dylib 0x00007fff946b4fb9 start_wqthread + 13

)

I have indeed switched to outlook which works fine. I guess it's my OCD that keeps making me try to fix mail. It's funny how contacts and iCal work fine. But how do u get FaceTime to bring up outlook contacts? Is there a way?

I dont know. I use icloud and Airmail, and the family member with Outlook is unavailable to ask. Anything that gets Mac Contacts app to have a copy of your Contacts should work if no direct method exists.

I moved to Maverick yesterday.

i fell in the Mail -Exchange trap...

Should have read this thread before.

Sync with exchange works fine on 5S and IPad...but not on my superb Mac...

What a blow to A. reputation. making your customers immediately unhappy when they upgrade to what they tought was First class.

No denial possible.

this happens when you move to Maverick.

And after reading this thread for a few weeks, my advice is either - go back to ML, or switch to Outlook. I gave up on Mail and Calendar after a few frustrating weeks and now use Outlook. I hope in Mavericks 10.9.2 I can return to Mail.

Yes, get out of Mavericks and back to ML, don't bother to call the Apple hotline or go to the genius bar. They either do not have a clue or are trained to deny that there is a problem. In my case they tried to figure out whether it was a server problem...

GM usually doesn't sell cars without wheels, and if they did they would need to call the stuff back. A computer without a functioning mail program is somehow equivalent, yet the Apple hotline or the genius bar people are just not allowed to tell you and the engineers haven't been able to fix it with the 10.9.1 update.