Exchange under Mountain Lion

the IMAP options didn't work for me. I hope the Apple folks hear our pleas for help and will address this issue soon.

the problem is that there has been a serious issue in Mail since Lion came out. So far this thread has only dealt with the fact that the server domain name changes after the account is initially created. The bigger issue is that if you have two exchange accounts on the same exchange server, Mail will work fine for a while then you will start losing folders and emails from one of the accounts. This issue has been present since Lion, so they only compounded the problem by introducing this new bug of server name chaning on it's own.

Apple has had plenty of time to resolve the first issue introduce in Lion, now they have this new issue in Mountian Lion. They have no desire to try to fix it, as far as Apple goes "It's an Exchange issue" which we all know is total BS because it works fine on the iDevices. I use the same two exchange accounts on the iPhone and iPad, no folder lost, no email lost, no server name changing. I know they can fix this issue as well as the original issue from Lion, they just don't care to do so.

I just got done tsting IMAP and Exchnage IMAP work fine for me. I was able to use the proper external domain name of our Exchange server and had no issues at all. I just don't want to use regular Exchange for Calendar/Contacts and IMAP for email.

Please Apple, Hear our complaint and at least bring it back to the way it was in Lion, that's better then nothing.

Checking use SSL on both internal and external servers on the advanced tab seemed to do the trick for me I now have email send and receive. Closed program and relauched and it still works.. It appears that the external server needed to be set to 443 (SSL) as well for it to work. I left the default server addresses in place since it always seemed to go back to those addresses anyway.

This worked fine before the upgrade so the upgrade had to of changed something.

Thats worked for me.

Delete the Exchange SMTP server and the Keychain entries and reconfigured the SMTP setting and everything works fine.

Thanks!!

Same thoughts here. Don't know how to handle this - *** does Apple not react on this...?

I just askes Scott via Twitter to check for our problem here: https://twitter.com/#!/forstall.

I discovered that it somehow to do with the SSL certificates.

Mail seems to want to connect with the Server the Certicate is signed to

E.g. if you put in your connection settings "Mymailserver" and the fully qualified Hostname for the Mailserver is "Mailserver.mybusiness.local" Mail want to connect to "Mailserver.mybusinedd.local and thanges automatically the entry in your Preferences because that's what's in the Certificate.

And so far Apple isn't responsible for singing and configuation issues related to windows server.

Changing the hosts file works fine for workstations but not for portables for security reasons.

Wondering if it might work to go back into Time Machine and re-install and older version of the Mail app.? Just worried I might lose recent e-mails. Does anyone have thoughts on this? Might be a last resort to do in a couple of weeks if Apple doesn't step up with a solution.

Joe

iMac 2010

Mountain Lion

I have tried numerous things suggested here, none seem to work. Will use OWA and hope Apple decides to fix this.

Adding resolution records to the /etc/hosts file seems to be an acceptable work-around for me for the time being (nevertheless, I feel uncomfortable knowing that something is not working well in my system and I surely hope APPLE resolves this issue properly as soon as possible). I have upgraded my laptop today but have kept my desktop system on the older version so far - so, I can spot the configuration differences between the Mail clients on the two systems: when I apply the configuration of the desktop to the laptop, it seems to work at first but gets overwritten next time I close and re-open the program. I believe that Apple engineers have somehow "improved" (always in good will...) the internal logic of their mail client in how it connects to the Microsoft Exchange platform, but there seems to be a number of Exchange servers out there that are not configured as expected and, thus, cause problems. It would be interesting to know whether there are any Apple users out there that haven't had these problems connecting to their Exchange servers after upgrading to Mountain Lion (such a fact would prove that my feeling is correct and would indicate that this is not necessarily a bug in Apple's software).

We are switching to a fresh install of Exchange this weekend and I just told the tech about the Certificate issue so he is going to reissue that removing all reference to the old .local server. (The new setup is not going to use .local domain addresses at all) I am hoping that that will fix it and will post an update as soon as I know.

This continues to be a puzzling problem. I do not have any strange entries under internal server like "local," etc. For both my internal and external server, it says what I would expect, exchange.*****.*****. I have deleted the keychain entry, deleted and re-added the account, experimented with turning on and off SSL and most other settings as well. On Thursday night, my account did not work for several hours and no changes helped. On Friday, it worked all day. Today, it worked this morning, but starting around noon, I can no longer access my Exchange account on any of my Macs. It works fine on my iPhone/iPad. I am not even sure if I am having the same problem as other users here, since I haven't noticed Mail to be changing my servers names to something unexpected.

Is it likely Apple are going to fix this.

Don't understand how it can suddenly not work if it worked fine in Lion. If it ain't broke.....

Read quite a few of these posts. I had the same problem, worked in Lion, not in ML. I did see in one of the posts, that checking the ssl box for external server may work, and that did indeed solve my problem. Thanks!

Here are copies of posts that may help

m@zo Germany

Re: Exchange under Mountain Lion

Jul 26, 2012 6:08 AM (in response to dwalthour)

I have to admit, the solution in my case was quite easy:

As opposed to Lion, my server really needs to be placed in the "external server" field, not hte internal. However, mail always fell back to the internal sever (the one not reachable) because of a stupid error: I forgot to turn on SSL for the external server. SSL is activated by default for the internal server, but not for the external server! Silly me

Thanks a lot for all your suggestions. You pointed me in the right direction!

ospreytc

Re: Exchange under Mountain Lion

Jul 27, 2012 3:27 PM (in response to m@zo)

I agree. Under my Prefs, Accounts, I went into "advanced" and saw that one of my SSL blocks was left unchecked. After checking it, I went back to “Account Info” and re-typed my server info into the correct fields (it seems to change those initially). I found a “mail-serv.” type address for my internal server, so I left that as is. The out going server had become black; so I typed an “owa” address into that area. I tried a test from and to myself at the exchange account, and it worked. It is working now for about fifteen minutes. We'll see. When I opened the accounts prefs to check the prafs, I saw that it now correctly contained SSL port info (info was blank previously). It is now listed as 443.

That was last nightS - it is still working.

Previously I used “owa” as my server addresses on my personal MacBook Pro while at work it filled the company server info.