Allow big attachments to be received in Exchange 2010

Client wants to receive large attachments because customers are trying to send huge things that they shouldn't, and it's easier to receive them than try to train the sender in good internet practices.

I compromised and said I'll allow up to 40MB attachments be received. This has been working for a long time.

Last week (sometime) it started rejecting everything over 10MB.

Everywhere I look, I see that 40MB was setup properly.

For Example:

[PS] C:\Windows\system32>get-transportconfig | fl maxreceivesize, maxsendsize


MaxReceiveSize : 40 MB (41,943,040 bytes)
MaxSendSize    : 40 MB (41,943,040 bytes)

Open in new window


and for the user in question:
[PS] C:\Windows\system32>get-mailbox  john | fl maxReceiveSize,MaxSendSize


MaxReceiveSize : 100 MB (104,857,600 bytes)
MaxSendSize    : 100 MB (104,857,600 bytes)

Open in new window


Even the best practices analyzer recognizes that it should be 40MB (and complains... as it should):

9-24-2014-12-51-36-PM.png
Yet, I am still getting bounces for things that are only 15MB:

Delivery to the following recipient failed permanently:

     john@theclient.com

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain theclient.com by office.theclient.com. [123.456.78.9].

The error that the other server returned was:
552 5.3.4 Message size exceeds fixed maximum message size

Open in new window


Where else should I be looking?
LVL 32
DrDamnitAsked:
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.

Roberto OviedoMicrosoft Infrastructure ConsultantCommented:
Hi good morning

The email you receive in a Edge or some antispam device, if you pass by some antispam check to verify that the configuration is not blocking the email.

You can also check the receive connector with this command

Get-ReceiveConnector  | fl

or

Get-ReceiveConnector | where {$_.PermissionGroups -like "*Anonymous*"} | fl


Greetings.
0
Marshal HubsEmail ConsultantCommented:
Anything in between Exchange Server and the outside world like a spam filter or firewall or any device between Exchange and the Internet could have a different limit set on it that could be the reason of your problem. This also includes your ISP. Also, check your WG SMTP-Proxy settings. Go into the proxy configuration editor and check the settings.
0
DrDamnitAuthor Commented:
Finally had the ability to swing back around to this.

The spam filter is not blocking it. The bounce messages specifically say that the exchange box is doing it.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

DrDamnitAuthor Commented:
It's not the ISP either.
0
Alan HardistyCo-OwnerCommented:
Hi Michael, did you check the Receive Connector as suggested above as there will be restrictions set on there too?

A useful guide for reference:

http://exchangepedia.com/2007/09/exchange-server-2007-setting-message-size-limits.html

Alan
0
Rajitha ChimmaniCommented:
You must contact the recipient domain if you are sending emails externally. Possible they have different limits set. If theclient.com domain is not your domain then the delivery failure says the server at that domain rejected the message.
0
Svet PaperovIT ManagerCommented:
Are you able to send big messages internally – for an Exchange to an Exchange account?

What is the anti-spam / anti-virus solution?
0
DrDamnitAuthor Commented:
Turns out, this was a bug or configuration problem in Exchange itself. The most recent roll-up (December) fixed it.
0

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
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
Exchange

From novice to tech pro — start learning today.