Link to home
Start Free TrialLog in
Avatar of Daniel Bertolone
Daniel BertoloneFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Message size exceeds fixed maximum message size

I have an issue where an end user is trying to send an email into the domain but keeps getting a bounce back saying that message size exceeds fixed maximum message size.

The email is 17mb in size and i increased the allowed message limit via server config > hub transport > receive connectors > default to 19mb but still cannot receive the email.

Do i need to apply the limit anywhere else or is there another way of checking the allowed message size?
Avatar of d3ath5tar
d3ath5tar
Flag of United Kingdom of Great Britain and Northern Ireland image

Does the user or the mailstore they are in have a limit set as well?
Hope you are facing issue when receiving the email which are more in size(as you said 17 MB email). follow the discussion below, that talks a little about this same situation.

https://www.experts-exchange.com/questions/26846812/Microsoft-Exchange-2007-only-accepts-messages-under-8MB.html

If you are having issues in sending big emails, you need to look at the sending limit on transport configuration. refer the article mentioned below,

http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/exchange-2007-message-size-limits.html
http://exchangeshare.wordpress.com/2008/04/24/exchange-2007-where-to-set-message-mail-size-limit/

If the NDR is generated from the destination domain, you will have to contact them for the limit that they have set.


-Praveen
Avatar of Rob Williams
The message size limits have to be set in several locations. The following SBS 2008 specific article outlines where and how to do so:
How Do I Change Message Size Limits in Exchange 2007
http://blogs.technet.com/b/sbs/archive/2008/10/28/how-do-i-change-message-size-limits-in-exchange-2007.aspx
If using the POP3 Connector you should also view:
http://blogs.technet.com/b/sbs/archive/2009/07/01/sbs-2008-introducing-the-pop3-connector.aspx

Keep in mind not all servers on note to you may support messages of that size. 6GB seems to be the standard that works consistently though many sites are expanding to 10GB and much more. This is especially importnat when using the SBS POP connector and a hosting company.
Avatar of Daniel Bertolone

ASKER

Thanks rob.

I changed the settings as per one of the link's above and my limits are as follows:

Max send Size: 10MB
Max receive Size: 2000KB

Any reason why its showing kb instead of mb?
Even though I changed the limits i am still unable to receive the email. External user keeps getting the same bounce back.

Do I need to restart any of exchanges services for the limits to come into effect?
Are you using the POP3 connector? As I recall you were in another post. If so it may be out of your hands. The host may not accept messages of that size.
Hi rob

No this is a different site that gets its mail delivered straight to exchange
SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Rob

The global receive size is set to 20480 KB

Also all of the user’s mailbox limits are set to unlimited but i still cannot receive the email.

I was thinking the issue could lay on the sender’s server but the bounce back points to us.
Try sending a large attachment from a 3rd party site to confirm.

Keep in mind trying to work with attachments of this size is not practical because of common limits by most servers.
Just sent a 17mb email from 3rd party site & get exactly the same message that the recipient server rejected the message due to file size.

The limit must still be enforced somewhere
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Agreed. Did you reboot the server after the changes? Restarting the Exchange services should do the trick, but if not see if a reboot will cause it to "kick in".