[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9295
  • Last Modified:

Outlook 2011 for MAC with Exchange 2010 HTTP Error -18500 when sending email

We recently installed Outlook 2011 for MAC after we moved a users mailbox to our new Exchange 2010 SP1 server.  Outlook is able to connect to exchange and download all emails, calendar, etc... however when you send an email you receive the following message:

HTTP error. The server cannot fulfill the request.

Mail could not be sent.  The message has been moved to your Drafts folder.

Account name: "Exchange"
Error code: -18500

I can see that the email has been moved to the drafts folder.  OWA works on the MAC, Outlook 2010 on PC also work with no issues.  I can even see the email moved into the drafts folder in OWA.

I have searched everywhere and most people seem to have this issue with large attachments but it happens for every email that I send.  I have done the fixes for the large attachments hoping that would fix it but no luck so far.

Any assistance anyone could give would be greatly appreciated!
  • 2
  • 2
  • 2
1 Solution
Have you enabled the Exchange Web Services (EWS) protocol? This is needed.

Use this link to analyze it. If it's not enabled or there is a mistake with it, it will show you.
SeptAdminAuthor Commented:
Yes EWS is enabled.  I ran the test from the link you sent and everything worked fine.  It did not report any errors for EWS connectivity.  For the test you have to use an account with an empty inbox, so i created a new user to do the testing with.  

To make sure that it wasn't a user problem I created a new account in Outlook 2011 for my test user.  It also received the same error when trying to send an email.
The fix with the attachement size did you do it like this?

By default, the web.config file is located in the EWS Virtual directory Microsoft\Exchange Server\ClientAccess\exchweb\EWS will have the following entry, by default, the max request size is approximately 13MB


<httpRuntime maxRequestLength="13280" />



Change the item <httpRuntime maxRequestLength="13280" /> to <httpRuntime maxRequestLength="X" /> where X is the desired value in KBs. for example, X will be approximately 50000 (50MB).

Probably yes.

Take a look at this, this can resolve your problem

As a general rule: If Outlook Anywhere works, Outlook 2011 for Mac will also work.

As to Outlook Anywhere working:
• Autodiscover from the Internet
• Download of the Offline Address Book
• Free / Busy time
• Out-off-Office

You can test Outlook Anywhere here:
Remote Connectivity Analyzer Version History

It is a lot easier to test and troubleshoot Outlook Anywhere than issues with Outlook 2011, which throws you out in the UNIX world.

The URLs you access with Outlook Anywhere must also be accessible from your internal network.

Perhaps you should take a look at the answers in this thread. Here you’ll also find a link to the University of Texas, which has good instructions on how to configure Outlook 2011 manually. But in the long run, make sure that Autodiscover is in place for your Mac client.

Details on getting to work an Exchange 2010 SP1 account in Outlook 2011 for Mac
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

SeptAdminAuthor Commented:
Thanks Xaelian! I was able to determine that the problem was a misconfiguration with Autodiscover.  Once i corrected it emails started sending.
This is a issue with product which the "BUG" team is aware of. The product team is closely working towards resolution. The resolution will come with next build. Till then enjoy using OWA for over-sized attachment. No matter wherever you search , post or go unfortunately this is it :(
FYI :  http://community.office365.com/en-us/forums/153/t/209414.aspx ---  "All users who are on Version 15.0 Build (837.10) on the O365 Server will experience this issue".  No luck till next build

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now