Yosemite mail and authentication exchange 2007

When the users started upgrading to Yosemite mail on ther Mac:s I have been seeing a lot of failed logins against Exchange. Several hundredthousands per hour.
I can see for example that the mac tries to access autodiscover/autodiscover.xml and gets a 401.
I found this post but it looks like it doesnt help for all the macs:
http://meandmymac.net/2014/10/trouble-with-yosemite-mail/
The client should authenticate with:
domain\username
but sometimes i get domain\emailaddress or cas-servername\username and they get a 401.
I have a exchange 2007 fully updated.
Anyone else who have seen this problem?

Hi,
Generally, the client side app decide how to connect to the Exchange Services. For example, Outlook has its own way (1. SCP from AD
2. DNS lookup 3. Localxml 4. SRV record)
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

Establish mail flow from Exchange 2007 to Exchange 2013

I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

Was this question answered. We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped. Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
using "Custom Settings" - manually entered IPs for DNS in the Exchange Admin Center "DNS Lookups".
Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.
Any assistance will be greatly appreciated.

Has anyone managed to create an email account on the OS X mail client with Exchange 2007?

Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen

jthurner wrote:
Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen
No workaround needed, open Mail, Contacts and Calendars (in System Preferences) select Exchange, enter your email address and password, opt to setup Contacts and Calendars as well as mail and hit enter. That should set it up (assuming your apparently witless IT dept has setup the autodiscover record correctly at their end)

I am having difficulty: we are running a windows server 2003 - mail and outlook support 2007 and upwards, how do I get the brand new apple machines to work with the 2003 version of server

I am having difficulty: we are running a windows server 2003 - mail and outlook support 2007 and upwards, how do I get the brand new apple machines to work with the 2003 version of server

I may be way out, but do you know about this product, would it help integrate the Macs for you.
https://www.thursby.com/sites/default/files/images/ADmitMacv8_SPD.pdf

Need to send mail from Microsoft Exchange 2007 account(different from Gmail) on behalf of another Gmail ID. How to configure that ?

I have a Gmail ID (e.g [email protected])
I have a Exchange ID (e.g [email protected])
I need to configure exchange account (2007) such that I can send a mail from my Exchange account but at the receiver end it looks like it was sent from ([email protected]).
Both the accounts are my accounts.
I need this because I do not have access to my Gmail account from place where I access the internet and I need to send the mails from my Gmail account only.

So you want to spoof your e-mail address.
You can make your Exchange server send as any address you want. Just create a different mailbox with that address as the primary (reply) address. It has to be a different account.
However, be aware that many systems to which you send such mail to will bounce it as suspected spam because they'll detect that your server is sending mail from Gmail but your server is not Gmail.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

HI, i need help here
I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
flow went back to normal. We then remove the program from the control panel.
Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
Much Appreciated

Symantec's support group should be able to tell you what happened.
--- Rich Matheisen MCSE&I, Exchange MVP

Mac Mail and MS Exchange Syncing Issues

I have seen this issue mentioned in the forum, but have not found any answers to help.
I have receive mail through Exchange from the university for which I work. I get the mail on my iPhone just fine. However, it does not come through on my MacBook Pro. I have to go into preferences and disable the account and then enable it again and then everything comes through. I am not sure what the problem is. I have updated my operating system to 10.9.2. This has worked fine in the past, but is not working properly now. Any help or ideas would be appreciated.

I can assure you that integration between Mail and Exchange is possible, at least in some scenarios. I am the primary Exchange system administrator for a medium-sized university that uses Exchange 2003 with an OWA (Outlook Web Access) front-end server.
I currently have Mail and Entourage 2004 running side by side on my just upgraded Mac. I used the mail account configuration wizard with ease. Go to the the Mail Preferences and click on Accounts. You can use the '+' button to add an account. Supply your full name and email address to the wizard and click continue. In the Account Type selection, choose Exchange. Type a friendly description such as "Exchange - Your Name". To get things to work correctly, you may need to know on what backend server your mailbox resides. You will also need to know what your OWA server is named on the network. You will also need to know what server is your outgoing mail server. This will likely be the same as your OWA or backend server. You should be able to retrieve those items from your Entourage settings. In my configuration, I was able to put the name of my OWA server (ex. owa.company.com) in both the Incoming Mail Server and Outlook Web Access Server fields as well as the outgoing mail server.
I am not sure how the configuration will vary with Exchange 2007 or in an environment without an OWA server. There are also issues with Address Book Integration of the Global Address List in Leopard in situations where there are multiple domains in a single forest. In that regard, contacts won't automatically resolve as they do in Entourage in many cases.

Assertion Failures using Mail.app with Exchange 2007...

We have been implementing and migrating our end-users to Exchange 2007. In doing so we found that Mail.app end-users were experiencing Assertion failures in Console.app. They used to cause Mail.app to crash and lose connectivity frequently to the Exchange 2007 server. We made a change to the firewall to allow communication to happen between domain controllers, but haven't been able to determine if this in fact resolved or helped hide the root cause. We seem to be no longer crashing Mail.app or losing connectivity, but the same logs when we would crash/lose connectivity are still happening when you look in Console.app.
*Here is an example of an Assertion failure where "The Operation couldn't be completed":*
+11/12/10 1:19:36 PM Mail[3201] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSConnection.m:374+
+Received an unexpected error: Error Domain=NSXMLParserErrorDomain Code=5 "The operation couldn’t be completed. (NSXMLParserErrorDomain error 5.)", response: (null)+
+ 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
+ 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
+ 2 Message 0x00007fff8036301b -[EWSConnection sendMessage:forRequest:] + 1117+
+ 3 Message 0x00007fff8036e5b9 -[EWSGateway sendMessage:forRequest:] + 79+
+ 4 Message 0x00007fff80381a63 -[EWSRequestOperation executeOperation] + 104+
+ 5 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
+ 6 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
+ 7 Foundation 0x00007fff8662abeb __doStart2 + 97+
+ 8 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
+ 9 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
+ 10 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
+ 11 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
*I also get this Assertion failure every time I re-open Mail.app that shows up in Console.app that says "Mail did something wrong: The specified folder could not be found in the store.":*
+11/12/10 12:44:22 PM Mail[3201] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
+Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x1012f1830> (EXECUTING)+
+ 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
+ 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
+ 2 Message 0x00007fff80382956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295+
+ 3 Message 0x00007fff80377aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88+
+ 4 CoreFoundation 0x00007fff879c26d7 __NSArrayEnumerate + 1399+
+ 5 Message 0x00007fff80377d86 -[EWSGetFolderResponseOperation executeOperation] + 445+
+ 6 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
+ 7 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
+ 8 Foundation 0x00007fff8662abeb __doStart2 + 97+
+ 9 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
+ 10 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
+ 11 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
+ 12 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
+11/12/10 12:44:22 PM Mail[3201] Recieved EWS error: Error Domain=MFEWSErrorDomain Code=79 UserInfo=0x1148c1d10 "The specified folder could not be found in the store."+
We are getting these Assertion Failures for other end-users as well that are using Mail.app and connecting to Exchange 2007 Server. I have wiped my mail.app account and started from fresh and that didn't help. I did it manually as well ensuring that preference files, caches, and passwords related to mail.app, ical.app, and Address Book.app were removed. That did not work. I just went from 10.6.4 to 10.6.5 hoping that would correct the issue, it did not. I even set up on another Mac a baseline Snow Leopard and patched it and then configured my mail account and still got the same errors.
What I am hoping for is not a miracle (Fixing the problem), but being told what these errors mean and if there is any risks to be concerned with. In other words, can I ignore these error messages or should I be concerned? Like I said it was causing us to get the sideways thunderbolt or triangle with an exclamation point and even crashing Mail.app at times. That hasn't happened since we let the all of the domain controllers talk to each other, even though they shouldn't have to.

I echo your hope for someone shedding a light on this. I too am geting Assertion failures, every few days, though without much in the way of crashes.
Here is an example of a log entry describing one recent such failure:
+5.12.2010 11:04:40 Mail[17075] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
+Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x11d80ec70> (EXECUTING)+
0 Message 0x00007fff81f7d6e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff81f7d649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff81ede956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295
3 Message 0x00007fff81ed3aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88
4 CoreFoundation 0x00007fff8448c6d7 __NSArrayEnumerate + 1399
5 Message 0x00007fff81ed3d86 -[EWSGetFolderResponseOperation executeOperation] + 445
6 Message 0x00007fff81f8bab9 -[MonitoredOperation main] + 229
7 Foundation 0x00007fff847b4de4 -[__NSOperationInternal start] + 681
8 Foundation 0x00007fff84893beb __doStart2 + 97
9 libSystem.B.dylib 0x00007fff85f6b2c4 dispatch_call_block_andrelease + 15
10 libSystem.B.dylib 0x00007fff85f49831 dispatch_workerthread2 + 239
11 libSystem.B.dylib 0x00007fff85f49168 pthreadwqthread + 353
12 libSystem.B.dylib 0x00007fff85f49005 start_wqthread + 13
Perhaps coincidentally, I am having trouble with syncing iCal with my Exchange account. Ii have only found this thread on the subject, and am in the process of trying to find there the solution to that problem:
http://discussions.apple.com/thread.jspa?threadID=2138051
Any and all insight would be greatly appreciated.

Mail and MS Exchange Server - help!

Can anyone tell me the simple way to go from Entourage to Mail 3.0? I work within an MS Exchange environment and I really want to use Mail now (the new version is exactly what I need) but my IT dept tell me integrating Mail and Exchange is impossible... Can that be true?
Does anyone have step by step instructions/stages I can take to them to get this sorted?
Thanks, Francis

I can assure you that integration between Mail and Exchange is possible, at least in some scenarios. I am the primary Exchange system administrator for a medium-sized university that uses Exchange 2003 with an OWA (Outlook Web Access) front-end server.
I currently have Mail and Entourage 2004 running side by side on my just upgraded Mac. I used the mail account configuration wizard with ease. Go to the the Mail Preferences and click on Accounts. You can use the '+' button to add an account. Supply your full name and email address to the wizard and click continue. In the Account Type selection, choose Exchange. Type a friendly description such as "Exchange - Your Name". To get things to work correctly, you may need to know on what backend server your mailbox resides. You will also need to know what your OWA server is named on the network. You will also need to know what server is your outgoing mail server. This will likely be the same as your OWA or backend server. You should be able to retrieve those items from your Entourage settings. In my configuration, I was able to put the name of my OWA server (ex. owa.company.com) in both the Incoming Mail Server and Outlook Web Access Server fields as well as the outgoing mail server.
I am not sure how the configuration will vary with Exchange 2007 or in an environment without an OWA server. There are also issues with Address Book Integration of the Global Address List in Leopard in situations where there are multiple domains in a single forest. In that regard, contacts won't automatically resolve as they do in Entourage in many cases.

Apple Mail and MS Exchange server?

In a strange twist of fate, our new university President is a Mac guy (yeah!), but he is obligating all of us to put email and calendar software into MS Exchange server. Sadly, it means I will need to migrate 4 GB of emails from Apple mail to Entourage.
Does anyone know of a solution that will allow me to continue using Apple Mail?
I also favor NOW Up to Date & Contact for calendar and contacts. Any ideas on connectivity between Exchange server?
Thanks.
Intel iMac Mac OS X (10.4.9)

Rats! I just heard from our IT department. The reason Apple Mail is not supported is that it requires IMAP to be turned on. They claim that "IMAP passes passwords and mail in clear text which is a big security problem. Exchange natively sends all of its info in an encrypted manner. "
Is there a way to get Apple Mail to use Exchange Server without IMAP in a way that will get these security freakish IT folks to be happy?

Demoting and Removing Exchange 2007 Server

Oh, I mistakenly saw 2003, and I thought you were removing Exchange 2003. My bad.
Run the uninstaller on the old system. It will take care of the rest. It will probably error out and give you reasons, clean up the reasons and run the uninstaller again. Once it's uninstalled properly, then you can power off the server and everything should be good. Don't forget your send connectors. I forgot that in my travels once.

At one of our locations we recently migrated all exchange mailboxes to a new Exchange 2007 on new OS platform, moving away from Server 2003. Everything to my knowledge has been migrated, users should be all connecting to new server, all connector headends have been updated, etc. As a test, I shutdown the old Exchange server (without uninstalling) but we ran into issues that day with Outlook constantly (every 5-10 minutes) asking for the user's password, slow loading of folder data, etc.; reboots/application restarts did not resolve. We turned the old Exchange server back on and all is now well. My theory is this is due to the schema still containing info about the old Exchange server. If I uninstall Exchange completely, thus removing it form schema, could I expect to have this issue resolved? Obviously I only get one chance on this, so...
This topic first appeared in the Spiceworks Community

Remove and reconnect Exchange 2007 from Domain

I have an Exchange 2007 server running on a Windows 2008 server. For some reason the server will not run group policies. It hangs for a very long time when logging in on "Applying Group Policy Printers Policy" And also won't shutdown hanging on
"Applying Group Policy". The only wany I can shut it down is to manually power off the server.
I also ran the Group Policy Results Wizard and get a timeout when I run it against the Exchange server. DNS is working fine. I have tested all of the other servers using the same DNS and they all work fine. The server in question has been having other problems
for a while now, but I have been able to resolve all the other problems except for this one. The server is old and will be replaced this year, but I have to make it work until I get a new server. Maybe 6 months or so.
I am thinking of removing the server from the domain and then joining the domain again. I'm not sure that will fix it, but I hope it will. The only thing I'm worried about is getting the Exchange database and server running again after I remove and rejoin
it to the domain. I have heard I can shutdown and disable all Exchange services, then remove the server from the domain and rejoin. But I have never done that and want to be sure it can be done without destroying connectivity to AD and the users. So, is this
possible?
Any help is appreciated.
Doug

You should try fixing the AD issues instead of removing the Exchange server from the domain. You should start by analyzing what was done to cause the issue in the first place and remedy that.
Here is a bit similar concern that has been discussed earlier and has been suggested some good steps to sort-out the issue :
http://community.spiceworks.com/topic/267400-removing-and-re-joining-an-e2k7-server-to-the-domain
Moreover, when need to recover mailbox items back into previous format, you may also give shot to this automated solution (http://www.exchangeserverrecovery.com/) that could be a good approach while dealing
in such crucial circumstance.

Using Mail and Windows Exchange Server 2003

HI I have just set up a server using windows server 2003 and I also installed exchange 2003 on it as well. I have a domain which forwards to my server so I can set up my own mail addresses on exchange which connects to outlook. My windows pc is connected to the domain and the email works fine, no probs. I would like my mac book (tiger) to connect to the exchange server as well for my wife to get emails using an email address I have set up for her. Myself and my wife are new to macs so its slow going at the moment but I am persistant. When setting up the mail using the exchange option it asks for the incoming and outgoing mail server which confuses me as exchange doesnt use these as far as I am aware. can anyone offer any hep at all as I would really like this sorting.
thanks for any help offered

Hi
Without any further details regarding how you have set up your exchange mail server as well as your private network its going to be difficult to help you. In any rate you are the one who has configured the exchange/windows server so I would imagine all of the information regarding the mail server you should know?
For example if you have enabled webmail on the exchange server then you should know that. If you have not enabled it then there is nothing you need put in the relevant field.
How well internal DNS queries resolve for your server name to its IP address will depend on how well you have configured internal DNS Services. Only you would know why you can use the IP address and not the name, or the name and not the IP address. Perhaps you should review this. Typically you would match the external MX Record with an internal one, that way DNS names can resolve internally as well as externally to their relevant IP addresses. This all depends on how you have configured Exchange mail server. For example you could be using the POP connector feature. Again this is something you should know as you are the one who has configured it.
also when going through the mail setup it wont connect to the
incoming mail sever using the dns info but it will to the outgoing
mail server using the same info.
This could mean that internal DNS Services are not set up and that outbound mail is actually using your ISP's mail server rather than your internal server.
I'm not sure where you are getting Port 993 from? The default ports for POP (inbound) and SMTP (outbound) are 110 for POP and 25 for SMTP. All that is required is a Port forwarding/firewall rule for those ports that point to the internal IP address of your mail server. Provided your domain's MX record is pointing to the fixed external IP address configured in your router at your location then mail should flow in and out. Again this all depends on how you have configured your domain and mail server to send and receive mail. Again only you would know that.
If you launch MS/DOS (PC) prompt or terminal (Mac) and telnet to the server's internal IP address for port 25 it should tell you if it is accepting mail. You can use the same thing for port 110. The command would look something like this:
telnet 192.168.1.1 25
You should see something like this:
Trying 192.168.1.1...
Connected to whateveryouhavecalledit.
Escape character is '^]'.
220 yourdomain ESMTP
If you configure Apple Mail for a POP account then it should work using the internal IP address of your mail server for both inbound and outbound mail, as long as the account configured on your mail serverr is configured for a POP mail account.
Most Mail Server's today will offer a mail service using IMAP accounts (this is in addition to the other methods offered) which can be accessed simply using a web browser. In my view this is preferable to POP accounts as (a) you don't need a separate mail application (b) no mail is ever stored locally, its all kept on the server (c) you don't even need your own pc/mac to access your mail. As long as you know 3 bits of information you can send/receive mail anywhere in the world just as long as you have access to any computer that has access to the internet.
Hope this helps, Tony

Yosemite Mail crashing with Exchange account

I'm running OS X Yosemite 10.10.1 on a 2014 Macbook Pro.
On startup Mail crashes immediately with the following error:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An EWS folder ID string didn't have a corresponding mailbox name'
I have three email accounts (Exchange, iCloud, Gmail) and have disabled each one in turn and Mail opens and works fine with the iCloud and Gmail accounts. So it's definitely a problem with Exchange. In the Mail accounts pane the 'Advanced' tab has a listing for Internal Server Path with 'EWS/Exchange.asmx' listed in the box, so I'm guessing it has something to do with that (given the EWS bit in the error message)?
I've moved the com.apple.mail folder to the desktop and re-opened Mail but that didn't help (I've moved the folder back to where it was).
I can access my Exchange mail from both iPhone and iPad, so the problem seems to be restricted to OS X Mail rather than a problem with a specific email (seems logical?).
Any help appreciated.
Cheers,
Grant.

Thanks. I had tried that already but it seems that the account was only 'deactivated' rather than deleted. Anyway, I tried again and chose the option to delete the account from all devices. I've now added a new Exchange account and all seems to be working.
Thanks again.
Cheers,
Grant.

Mail and old Exchange server

Our institution has not upgraded to the 2007 Exchange server, and Mail under Snow Leopard does not recognize it. Has anyone found a workaround for this?
Thanks

Setup Mail as an IMAP client.

Yosemite mail and authentication exchange 2007

Similar Messages

Maybe you are looking for