• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 74
  • Last Modified:

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):

Yet, I am still getting bounces for things that are only 15MB:

Delivery to the following recipient failed permanently:


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?
1 Solution
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


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

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.
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.
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

DrDamnitAuthor Commented:
It's not the ISP either.
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:


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.
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?
DrDamnitAuthor Commented:
Turns out, this was a bug or configuration problem in Exchange itself. The most recent roll-up (December) fixed it.
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.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now