Exchange servers and Mavericks Mail

Well,

i did test Airmail - it work worse than native Mail app with my Exchange.

and i can mention, that all apps including outlook for windows works bad with EWS in opposite to ActivSync used before.

all mobile devices, including ios, still using ActivSync and receiving mail 3-100 seconds faster than any application using EWS.

so, what?

i do think, that this is time to start blame microsoft on bad implementation of EWS. thats it.

zloibubr wrote:

i do think, that this is time to start blame microsoft on bad implementation of EWS. thats it.

That or badly configured autodiscover services on the Exchange server.

As Microsoft still refuse to deploy ActivSync for Macs (and PC's) we are stuck with it.

We do have couple of Exchange servers distributed over the world and failover in case of malfunctiona of on of servers. So, i think, its hard to blame our admins as this still works on 15k mailbox size organization 🙂

Anyway, things got worse day by day.

The only question i have, how this was working without any issues before Maverics? Can you explain?

The same problems were reported by a minority of users when Snow Leopard, Lion and Mountain Lion came out.

From my own experience: Exchange and Mac Mail work correctly, in Mavericks and in every version of OSX back to Snow Leopard.

It was not broken before Mav, and it's not broken now.

I connect to 2 different Exchange servers, 2010 (which I host myself) and 2013 (Rackspace hosted)

I suggest that you try Touchdown for Mac, it's an Exchange client, only Exchange accounts are supported, but they are supported via ActivSync rather than EWS, Touchdown is the only client I have found that uses ActivSync on a Mac.

MS Exchange 2013.

After upgrading to 10.9.2 majority of errors gone.

I am able to send and receive mail.

sometimes it could not connect, but rarely.

however calendar app regularly makes me sad, as cant put updates to server.

What has the numbers 15.0.847 etc?

If it is the Exchange server you are speaking of that is 2013, Service Pack 1 rollup 4, it's up to date.

This link will connect you to Microsoft's Exchange connectivity analyzer, run it and post back.

https://testconnectivity.microsoft.com

Yup, that's where you should be in terms of Exchange updates. Run the site that csound1 posted above. I highly recommend you create a test account to use to run those tests.

https://testconnectivity.microsoft.com/

Csound1 wrote:

That or badly configured autodiscover services on the Exchange server.

References to documentation for "well configured" autodiscover services would be helpful.

The constant claim of "bad configuration" with zero evidence and no docs provided grows tiring.

Csound1 wrote:

The same problems were reported by a minority of users when Snow Leopard, Lion and Mountain Lion came out.

From my own experience: Exchange and Mac Mail work correctly, in Mavericks and in every version of OSX back to Snow Leopard.

It was not broken before Mav, and it's not broken now.

This thread is proof that your claim is nonsense. Funny that everyone complaining in this thread has no problem with older versions of Mail.app, and every one of them report the exact same issues with Mavericks.

Meanwhile you keep saying No Problem, No Problem. Well this thread exists because there is a problem. I can document and I can provide pcap files showing the problems in action. I have the proof. I have posted proof, and you and your buddies had those posts and the entire thread removed.

You or your buddies will remove any message which contains technical descriptions of the problem because that's how you treat people. But your ability to remove messages which contain proof you are wrong does not make you right. It just means you have Power and you're willing to Abuse it.

zloibubr wrote:

The only question i have, how this was working without any issues before Maverics? Can you explain?

They can't. They'll just insult your intelligence, and your support team with evidence-less acusations. If you post proof of the problem, they'll delete your posts. That's how it rolls here.

bradhs wrote:

Create a new user profile on your Mac. Then set up your Exchange account under that profile. Does that have any issues?

Yes. I can reproduce with a new profile. I can reinstall Mavericks from scratch and reproduce. I can go purchase a brand new Macbook with Mavericks and reproduce.

I can then wipe the Macbook and install ML and it works fine.

I received all this problems with my brand new mac pro purchaised to replace my mac air.

And Air started to receive similar issues after upgrading to Maverics.

So, looks like issues you are mentioned are disconnected.

And i did recreate account with wiping out everithing couple of weeks on mac pro, as sometimes my calendar app stacks and cannot update my meetings from exchange.

Hi Jorhett,

I believe you have a problem that is not solvable by us. I suggest you open a ticket with Apple support directly. And if you already have opened up a ticket with Apple, then I suggest you follow up on your open ticket. Also, if you want to be of additioanl help please provide your pcap and logs.

Here's a few ways for you to create logs that are helpful for Apple:

Enable HTTP Activity logging

defaults write -g LogHTTPActivity YES

Start Mac Mail is EWS Connection logging mode:

Applications/Mail.app/Contents/MacOS/Mail -LogHTTPActivity YES -LogEWSAutodiscoveryActivity YES >& ~/Desktop/EWSConnectionLog.txt &

Do not post this information here, especially the EWS Connection logging as it will contain very sensitve data.

If you have some technical evidence it will not be deleted. I would like to see it.

If you insult people or make false accusations or speculations the mods may delete. You are mighty close to that in your recent posts.

bradhs wrote:

I believe you have a problem that is not solvable by us. I suggest you open a ticket with Apple support directly.

I have those issues opened, and we've collected significantly more information than just that. I had those options back in 2013 ;-) Apple has those logs and has acknowledged open bugs about this.

As previously stated, my reason for posting here is to attempt to stop Csound1 and you from trying to both lay claim that there are no problems with Mavericks Mail.app, and also to prevent you for blaming people with the unspecified "bad configurations" ghost.