Receive Exchange Attachment size

Would appreciate any advice on properly modifying the receive attachment sizes on our exchange 2010 server. I have modified the settings everywhere i can find however the rejection still occurs at the default 10MB limit.

I have Modified:  Set-TransportConfig -MaxReceiveSize 15MB  in the Shell

Modified message size restrictions in the individual setting for individual user  50000
Modified the Receive Connectors under Hub Transport 50000

Is there one i am perhaps i am missing?

The only thing i have not done is actually reboot the exchange server (no good time to do this)

Any help appreciated.. Thanks everyone!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nick RhodeIT DirectorCommented:
Great article on all the spots to check:

Might have missed the transport settings:

Organization Configuration > Hub Transport > Global settings
ssumerlinAuthor Commented:
Thank you very much... that is a perfect article!  I checked everything and i had missed the Organization hub transport. it is now also set.  

Still getting the bounce @ 10 Mb's however.  "This message wasn't delivered to anyone because it's too large. The limit is 10 MB. This message is 18 MB"

However when entering "Get-TransportConfig | Fl max*size" in the power shell  i get the correct response on the setting:  MaxReceiveSize : 20 MB's  

is this perhaps down to a reboot or is there a service that could be restarted?
Nick RhodeIT DirectorCommented:
Yes, a simple restart of the server would to.  If you are currently live and are unable to do so you could try restarting the exchange information store (for mailbox restirctions) and transport (for connectors).  I am trying to think of what else.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Don't bother restarting the server.
here is the complete list of all the places that need changing.  The first group gets the current sizes, the second will change the size limitations *EVERYWHERE* they need changing in order to make it work.

Get-SendConnector | fl MaxMessageSize 
Get-ReceiveConnector | fl MaxMessageSize
Get-TransportConfig | fl ExternalDsnMaxMessageAttachSize
Get-TransportConfig | fl InternalDsnMaxMessageAttachSize 
Get-TransportConfig | fl MaxSendSize
Get-TransportConfig | fl MaxReceiveSize

Get-SendConnector | Set-SendConnector –MaxMessageSize 20MB
Get-ReceiveConnector | Set-ReceiveConnector –MaxMessageSize 20MB
Set-TransportConfig -ExternalDsnMaxMessageAttachSize 20MB
Set-TransportConfig -InternalDsnMaxMessageAttachSize 20MB
Set-TransportConfig -MaxSendSize 20MB
Set-TransportConfig -MaxReceiveSize 20MB

Open in new window

ssumerlinAuthor Commented:
Thanks jrhelgeson!  I appreciate it very much.

I made the changes but i skipped the send connectors as we do not want to open those up.

it is interesting that when sending a test i do not a bounce but i do not receive the emails either?  Using Gmail..  perhaps they will not send anything over 10?
Nick RhodeIT DirectorCommented:
Gmail I believe sends up to 25.  Could also be the ISP does not allow it.
ssumerlinAuthor Commented:
Update .. doing more test today.  I have sent several however and not receiving a bounce but the email is not being delivered.

When looking at the Barracuda Spam filter the test (18MB's) email shows up there and indicates "delivered".  But the email is not showing up in the recipients outlook.
Nick RhodeIT DirectorCommented:
See if you can open up EMC and do a message tracking.  Exchange would have thrown an NDR (if turned on).  Check the junk folder if applicable.
ssumerlinAuthor Commented:
Update ....  i am again receiving a bounce message.  possibility a reboot is in order?

This is the Spam & Virus Firewall at

I'm sorry to inform you that the message below could not be delivered.
When delivery was attempted, the following error was returned.

<>: host[] said: 552 5.3.4
    Message size exceeds fixed maximum message size (in reply to MAIL FROM

Final-Recipient: rfc822;
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Spam-&-Virus-Firewall; host[]
    said: 552 5.3.4 Message size exceeds fixed maximum message size (in reply
    to MAIL FROM command)

---------- Forwarded message ----------
From: SSum <>
To: "Sumerlin, Stan" <>
Date: Fri, 4 Oct 2013 14:46:06 -0400
Subject: 16203k
If you are sending a 16mb message, expect that it will inflate to 2x the size once it gets mime BASE64 encoded.

Therefore, set your send/receive to 40mb to guarantee you'll get an 18 mb message.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ssumerlinAuthor Commented:
Thanks !   I will make that change
ssumerlinAuthor Commented:
jrhelgeson - It appears doubling it to 40 MB's did the trick!  I had no idea 2x the size would be necessary.

I appreciate everyone's help!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.