Exchange under Mountain Lion

Now an Exchange bug has appeared in ios6:

http://www.macrumors.com/2013/02/14/apple-says-ios-6-1-exchange-bug-fix-is-on-th e-way/

In this case MIcorsoft is "working with Apple on a solution "!

What about the long-suffering Mountain Lion users?

Under Mac OS 10.8, where do we enter the domain for the exchange server. I am prompted for this when setting up on my iphone, but cannot find it under 10.8 mail.app setting.

If your exchange server is setup properly, you shouldnt need it

Just username & password

Your Autodiscover CNAME should take care of the rest

What version of exchange are you running?

Do you have an autodiscover record setup? Ping "Autodiscover.YOURDOMAN.com" see if you get the correct response back

Just about to say that, but if that doesn't work login with the domain in the credentials:

ie: domain/username

you dont reed it if you put the cirrect excgange server address

Its getting worse now!!

after upgrading exchange 2010 with SP3 (prepairing for 2013 migration)

mail app does not want to sync the EWS no longer, even outlook 2011 for mac does not work anymore

OSX Mountain Lion Mail client DOES NOT WORK with Microsoft Exchange server. Period. It doesn't matter how many hours you spend trying to get it to work, or what settings you put in. They did something with the Mountain Lion update that changed a setting in a location where users can't access it.

I have spent HOURS working on this with my extremely competent high-level tech support staff at Rackspace, my MS Exchange host. I am also an advanced user that has configured countless systems to work correctly with various versions of MS Exchange server and with various exchange hosts.

When we set up Mac Mail on a LION machine using the autodiscover settings from the MS Exchange server, it works PERFECTLY. When we try to set up mail on a MOUNTAIN LION machine, we encounter numerous connection errors, incomplete mailbox synchronisations, and constant freezing in the Mac Mail program. ZERO variables changed on the server side of the connection....the only thing that is different is whether we use LION (it works) or MOUNTAIN LION (will not work.....ever......even if settings are manually input). Therefore, anyone with even limited experience in IT can tell you this problem is being caused by something on the MAC side of the connection..not on the Exchange server side. Obviously since LION works...it is something related to MOUNTAIN LION.

Many people, including myself, have reported this directly to the Apple mail team. Those who have heard back seem to be told "the problem can't possibly be with Apple's software." The test we did proves without any question that it can ONLY be on the Apple software side. Apple knows their Mac Mail client doesn't work with the single most-used mail server on earth....and they don't appear to care....or to be doing anything to fix it. I am sure they read these discussions, and also the feedback submitted directly to them.....and this problem remains unresolved since July of 2012.

You can spend hours reading through this and other threads, and testing settings etc. but you are wasting your time. This isn't going to work until Apple decides it is important to them to make their customer's expensive premium laptops work with Exchange, and does something to fix whatever broke Exchange compatibility when they updated to Mountain Lion.

If you want to do something productive, you should submit feedback directly to the Mail team using this link:

http://www.apple.com/feedback/mail.html

Perhaps if they hear from enough of their loyal customers about this, they will feel compelled to fix this MAJOR problem with OSX Mountain Lion. So far their response has just been "Thanks for all your $$$ but too bad it won't work with your server....not our problem." Not exactly the type of customer service anyone expects from the sellers of the most expensive computer hardware available.

JG in SB wrote:

OSX Mountain Lion Mail client DOES NOT WORK with Microsoft Exchange server. Period.

That's strange, I have 119 clients (in severally located offices) using Mac Mail with Exchange servers (2007, 2008SBE, 2010 and 1 Exchange server 2013)

They all work.

What version of Exchange are you connecting to?

Exchange 2010. Hosted by Rackspace. My PCs work perfectly, and a Mac LION machine works perfectly. Several different Mountain Lion machines fail to make a stable connection. How did you pull off this miraculous feat for 119 clients? And what do you think the explanation is that myself...and 47 pages of previous commentors....are all having similar issues with it NOT working?

Thats strange again

I have NO issues on Mountian Lion with Mac mail

Also, i support hunderd of Thousands of customers on AppRiver's Hosted exchange and they all work too

Are you connecting to a server located on the same internal network as your Mac? Or are you connecting to a remotely located one....like I do....or anyone does when they are out of their office using their Macbook? Csound1 seems to say he has it working from remote locations.

We have over 900 Hosted Servers, the funny part is,,mostly in Rackspaces data centers

so, yea, its all hosted,,just like you

How can you explain the fact that the lion machine works....no settings are changed on the server side at Rackspace....and the Mountain Lion machine doesn't work?

There are no miracles, only mistakes.

I am not using a hosted service for one. I manage my own Exchange servers and take care that the autodiscover settings are kept up to date, and are accurate to start with.

There are a millions of users of Exchange with Mac Mail, at an estimate a few hundred of them are reporting issues here, this after all is an 'emergency room' for problems, most people are here because of that.

Go back to your hosting service and request current server settings and authentification requirements, turn autodiscover off and try manually. If that works it is Rackspace's error.

We tried that but I will try it again.....for some reason I seem to have to work at these things until they are resolved instead of saying "screw this" and just getting a different laptop that works. Thanks for the additional input. Confirmation that this is working perfectly for people with other hosts will help me argue with Rackspace if it is in fact an issue on their side.