Mail.app with Exchange 2010

Question

Level 1

8 points

Mail.app with Exchange 2010

I work in a large educational institution. Recently, we upgraded to our Exchange server from 2003 to 2010. The process has not been smooth.

In Exchange 2003, I was able to connect to the server, read my email, send email, etc. Since the "upgrade", I can not.

I've tried deleting the account and going to System Preferences | Mail, Contacts.... and recreating the account there. When I do so, the account can't be created because "The Exchange server "appropriate_server_name" is not responding."

The settings are correct if I go ahead and set up the account manually:

the appropriate server is listed as the Internal Server
The internal server path seems correct: EWS/Exchange.asmx
The internal port is 443 with SSL turned on.
External port is also EWS/Exchange.asmx

My iPhone and iPad connect without a problem. (I'm presuming that this is a different set up since I don't have to be on the network for iOS devices to work).

Any help with where I can have the IT people look would be greatly appreciated.

For example, is there a permission setting that needs to be checked on the server? (We seem to have had to fix some of these).

Thanks in advance.

Posted on Jan 24, 2012 4:44 PM

Reply

Answer 1

Csound1

Level 9

60,063 points

Jan 24, 2012 4:47 PM in response to Smhearty

EWS/Exchange is a 2003 pathway.

Ask the IT dept for the correct numbers, maybe even make them work for a living and do it for you, Mail is compatible with E2007 & E2010, (and yes, I do wonder how it worked with E2003, with which it is not supported)

Stop giving IT a pass, they exist to fix your problems.

Reply

Answer 2

Smhearty Author

Level 1

8 points

Jan 24, 2012 5:12 PM in response to Csound1

Thanks so much. Do you know what numbers I'm looking for? Am I looking for a specific pathway?

Autodiscovery doesn't work. This is why I believe that they have a permission setting wrong on the server.

Exchange 2003 didn't sync Calendar or Contacts. I was looking forward to Exchange 2010 for the additional functionality. However, this has been a huge step backward for me.

Thanks again for your quick and kind reply.

Reply

Answer 3

Csound1

Level 9

60,063 points

Jan 24, 2012 5:26 PM in response to Smhearty

Smhearty wrote:

Thanks so much. Do you know what numbers I'm looking for? Am I looking for a specific pathway?

Autodiscovery doesn't work. This is why I believe that they have a permission setting wrong on the server.

Exchange 2003 didn't sync Calendar or Contacts. I was looking forward to Exchange 2010 for the additional functionality. However, this has been a huge step backward for me.

Thanks again for your quick and kind reply.

You'll need your e-mail address, password, username (usually but not necessarily the part of your e-mail address preceding the @ sign) and mail server address, this, in the majority of cases will connect you, if it does not IT needs to hand over the missing info.

Reply

Answer 4

Asatoran

Level 4

2,532 points

Jan 24, 2012 5:34 PM in response to Smhearty

iPhone/iPad connect to Exchange using ActiveSync. Mail in OSX 10.6 and later use Exchange Web Services. (EWS) So iPhone/iPad connecting doesn't necessarily help troubleshooting OSX Mail.

Exchange 2003 did NOT have EWS. Were you using the same version of OSX & Mail to connect to the 2003 server? If so, then likely the old server was configured for IMAP access. (Or were you using some other app like Entourage?) To gain the same access for the new server, you'd need to enable IMAP on the new Exchange server. (POP3 could also be used, but probably not what you want.) If your OSX Mail connectivity to Exchange 2003 previously did NOT provide access to your Exchange calendar, then you almost certainly used IMAP (or POP3.)

To connecting Mail to Exchange 2007/2010, you point Mail to your Outlook Web App webpage. (a.k.a.: Outlook Web Access in Exchange 2003.) The same web page you should be able to access with a web browser. If you're using a single Exchange server (no Edge or hub transports, etc.) the OWA & EWS is enabled by default.

Reply

Answer 5

Csound1

Level 9

60,063 points

Jan 24, 2012 5:37 PM in response to Asatoran

Asatoran wrote:

iPhone/iPad connect to Exchange using ActiveSync. Mail in OSX 10.6 and later use Exchange Web Services. (EWS) So iPhone/iPad connecting doesn't necessarily help troubleshooting OSX Mail.

Exchange 2003 did NOT have EWS. Were you using the same version of OSX & Mail to connect to the 2003 server? If so, then likely the old server was configured for IMAP access. (Or were you using some other app like Entourage?) To gain the same access for the new server, you'd need to enable IMAP on the new Exchange server. (POP3 could also be used, but probably not what you want.) If your OSX Mail connectivity to Exchange 2003 previously did NOT provide access to your Exchange calendar, then you almost certainly used IMAP (or POP3.)

To connecting Mail to Exchange 2007/2010, you point Mail to your Outlook Web App webpage. (a.k.a.: Outlook Web Access in Exchange 2003.) The same web page you should be able to access with a web browser. If you're using a single Exchange server (no Edge or hub transports, etc.) the OWA & EWS is enabled by default.

That's what I was thinking, and you are correct in that calendar and contacts will not be available using Imap.

Reply

Answer 6

Smhearty Author

Level 1

8 points

Feb 7, 2012 8:16 AM in response to Smhearty

So, I'm still not experiencing happiness. I'm connecting through EWS protocol. If I'm not on the network, everything works well. Once I'm inside the network, I have lots of issues.

Sending email (whether new or a reply), will frequently result in an error message. However, the email has actually sent already. This leads to me sending multiple copies.
Inside the network, I have to use port 80 for the internal server. Turning on SSL will result in errors in connecting.
I frequently receive messages "This message has no content". This seems sporatic. I can't ever get the body of that message. (It shows up fine on iOS and Outlook 2010.) Synchronizing doesn't bring in the body of the message. Frequently, the message window shows absolutely nothing. Sometimes it will show the From, Subject, Date, To, CC fields, sometimes it is completely blank.

I used AutoDiscover to do the original settings. AutoDiscover set up the correct internal server and external server. However, it also turned on SSL for both. The internal and external server path are ews/exchange.asmx.

Any help, ideas, etc. is greatly appreciated. This has been a great source of frustration. I was looking forward to Exchange 2010 and being able to sync everything. Instead, it has been greatly frustrating.

Cheers.

Reply

Answer 7

Smhearty Author

Level 1

8 points

Feb 7, 2012 9:27 AM in response to Smhearty

Looks like an authentication issue?

Our Exchange server is set up with these settings:

Server sideissue, please ask your exchange administrator to perform the following actions.

1, Open IIS Manager on yourExchange 2007/2010 Client Access Server

2, Select "Default WebSite" then "EWS"

3, Select"Authentication"

4, Right click on "BasicAuthentication"

5, Select "Enable"

Yet, I continually get the message below:

2/7/12 12:24:40.626 PM Mail: *** Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1257/MessageStores.subproj/EWSConnection.m:486

Received an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)" UserInfo=0x7f95e74b44e0 {EWSErrorMessage=The request failed schema validation., NSUnderlyingError=0x7f95e748e980 "The operation couldn’t be completed. (SOAPWebServicesErrorDomain error -1000.)"}, response: (null)

(

0 Message 0x00007fff91db60f7 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116

1 Message 0x00007fff91db628d -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185

2 Message 0x00007fff91ce481a -[EWSConnection sendMessage:forRequest:] + 643

3 Message 0x00007fff91cf5283 -[EWSGateway sendMessage:forRequest:] + 75

4 Message 0x00007fff91d059d0 -[EWSRequestOperation executeOperation] + 108

5 Message 0x00007fff91dd6b7f -[MonitoredOperation main] + 228

6 Foundation 0x00007fff923586d8 -[__NSOperationInternal start] + 705

7 Foundation 0x00007fff9236b936 ____NSOQSchedule_block_invoke_2 + 124

8 libdispatch.dylib 0x00007fff97eff8ba _dispatch_call_block_and_release + 18

9 libdispatch.dylib 0x00007fff97f00799 _dispatch_worker_thread2 + 255

10 libsystem_c.dylib 0x00007fff940bb3da _pthread_wqthread + 316

11 libsystem_c.dylib 0x00007fff940bcb85 start_wqthread + 13

)

Reply