5.3.4 Message size exceeds fixed maximum message size


I searched thru other posted questions and I find similar postings, but none of the noted resolutions worked for me.

I am trying to send a 17 MB attachment to my external address. But when I send it I get a '5.3.4 Message size exceeds fixed maximum message size'

The Global Settings and the Send Connector of the Hub Transport are set at 30720 kb. There are no size limitation on the invididual mailboxes

Any ideas on what I overlooked?
bnrtechAsked:
Who is Participating?
 
endital1097Commented:
yes, the receive connectors have a 10MB limit

get-receiveconnector | set-receiveconnector -MaxMessageSize 30MB
0
 
beachgeeks1Commented:
I actually had the same problem on a 2K8 server last week.  Even though I didn't have limitations on the individual boxes, it would not allow the email to pass through to its destination.  After much searching the work around that I did was place an individual limit on the individual box and poof.  The email went through with no problem.  I had to do this for every user on the network.  Not a true fix, but a great work around.
0
 
smartsidCommented:
The error is definitelyu related to MEssage size restrictions. Please check Message size limits at below locations.
1. Global Settings for Exchange Organization.  Run "Get-transportconfig" in EMS and look for MaxSendSize
2. Check the limits on send connector. Run "Get-sendconnector | List" in EMS and look for MAxMessageSize
3. Check for any Message limits set on HT Servers. Run "Get-Transportserver | List " in EMS.
4. Look for any Message size restrictions set on User Mailbox. Run "Get-mailbox -identity affected_user_smtp"  in EMS.
 
Please post the output so we can help u further.
 
0
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.

 
endital1097Commented:
who is the reporting server in the NDR
if it is the destination server, then the have the limitation
outlook typically prevents you from attempting a message that exceeds the limit
0
 
bnrtechAuthor Commented:
endital1097 - the NDR is happening on the sender side. However, I have access to both the send and destination server. So if you would like me to check setting on the destination server just let me know.

smartsid - I was able to get 3 of the 4 items you requested. For the one item (Get-Transportserver | List) I was unable to locate the exact line item you wanted me to get a screenshot. Can you please clarify?

Also for 'Get-mailbox -identity affected_user_smtp' I could not get the syntax correct, but I believe the screenshot I am providing for 'user mailbox' will do the trick, right?

GetSendConnector.JPG
GetTransportConfig.JPG
usermaiilbox.JPG
0
 
bnrtechAuthor Commented:
beachgeeks1 - thanks for the tip. I am going to hold off on this suggestion and hoping a more global solution comes up (that may help both of us :)
0
 
endital1097Commented:
an easy way to test your internal settings is to send a coworker a 17mb file
if the message is delivered internally the issue is either on the external recipient's end or you ir internet send connector
0
 
bnrtechAuthor Commented:
endital1097

Good idea. I sent an email to an internal address and it has not bounced back (been about 20 minutes now).

I don't think it is the external recipient because I am sending test messages to another E2007 server that I manage. So then maybe, as you suggested, it is the internet send connector.

Where would I go to check the settings of the internet send connector?
0
 
endital1097Commented:
use the following to review the connector settings that apply
get-sendconnector | fl name,max*
0
 
bnrtechAuthor Commented:
endital1097,

Got it. I ran the command you noted on both the sending and recieving server. Screen shots from both servers
SendServerGetSendConnectorMax.JPG
RecieveServerGetSendConnectorMax.JPG
0
 
endital1097Commented:
run the same on all receive connector (both environments)
get-receiveconnector | fl name,max*

should probably also run
get-transportconfig | fl max*
0
 
bnrtechAuthor Commented:
0
 
bnrtechAuthor Commented:

That did the trick. Thanks for the support.

Interesting that none of the settings that I could tweak via the GUI management console could make this happen. Maybe I missed one?

Anyhow, it is fixed. Thanks again
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.