none
Maximum message size RRS feed

  • Question

  • I have an application that puts messages into Office 365 via the EWS "CreateItem" command.  What I am noticing is that very large messages (total size about 69 mb) are accepted by EWS but then disappear - they are not imported.  I think that previously, I would at least get a http 500+ error, but now the message is happily accepted, it just disappears.  If I manipulate the size of the message to go below that 69 mb threshold, it will work fine (the only difference is the size of the attachment).  So can you tell me what is the real maximum message size, can it be increased somehow, and is there a way that you can update EWS so that it returns an error if a message cannot be imported?

    (sorry if this is an answered question, but the search function on this forum is not working at the moment).

    Tuesday, July 17, 2018 8:33 PM

All replies

  • Best to set limit at 33-35% larger then the desired limit.  For more info read this https://support.lucid8.com/support/solutions/articles/6000171025-message-being-sent-exceeds-the-message-size-established-exchange-2007-2010-2013-2016-

    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    Tuesday, July 17, 2018 8:42 PM
  • I haven't tried using the Exchange Management Shell, but I'v set the message size restrictions for my test mailbox to be 153600 kb for both sent and received messages.  Makes no difference.  
    Tuesday, July 17, 2018 9:10 PM
  • Well a few things

    1. Follow that article

    2. Like the article says it can take time to make those stick unless you cycle 

    AFTER MAKING ADJUSTMENTS

    • Once you make changes for message size, even though the changes appear to be updated it may take up to 2hrs or more for changes to actually take effect

    • To make changes take effect immediately: Restart the Microsoft Exchange Information Store & Microsoft Exchange Transport service.


    NOTE: Be aware that restarting the Information Store service will dismount and remount all exchange databases on the server which will interrupt mail flow temporarily.


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    Tuesday, July 17, 2018 9:16 PM
  • What does the response you get look like ? CreateItem should return the ItemId ?

    Also are you setting the X-AnchorMailbox header ?

    Cheers
    Glen

    Tuesday, July 17, 2018 11:35 PM
  • Well actually it turns out that while there is no http error, the response XML does have the error "ErrorMimeContentInvalid" (in response to the message being too large).  This is different behavior than previously, where I would get http error 507.  And I was able to increase the message size limits in the O365 admin app, but as someone indicated, it does take a couple hours or more for the change to take effect.
    Wednesday, July 18, 2018 5:49 PM