Solved

Allow big attachments to be received in Exchange 2010

Posted on 2014-09-24
9
65 Views
Last Modified: 2015-02-09
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?
0
Comment
Question by:DrDamnit
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 

Expert Comment

by:Roberto Oviedo
ID: 40342249
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
 
LVL 10

Expert Comment

by:Marshal Hubs
ID: 40343197
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
 
LVL 32

Author Comment

by:DrDamnit
ID: 40440515
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
ClickHouse in a General Analytical Workload

We have mentioned ClickHouse in some recent posts, where it showed excellent results.

In this article on Experts Exchange, we’ll look at how ClickHouse performs in a general analytical workload using the star schema benchmark test.

 
LVL 32

Author Comment

by:DrDamnit
ID: 40440518
It's not the ISP either.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 40442142
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
 
LVL 16

Expert Comment

by:Rajitha Chimmani
ID: 40442785
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
 
LVL 20

Expert Comment

by:Svet Paperov
ID: 40442853
Are you able to send big messages internally – for an Exchange to an Exchange account?

What is the anti-spam / anti-virus solution?
0
 
LVL 32

Accepted Solution

by:
DrDamnit earned 0 total points
ID: 40598013
Turns out, this was a bug or configuration problem in Exchange itself. The most recent roll-up (December) fixed it.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

631 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question