Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 110
  • Last Modified:

Weird behavior of message size limits in Exchange 2007

I've just seen what I think is some bizarre behavior in Exchange 2007 regarding message size limits.  I'm sending from one Exchange 2007 to another Exchange 2007 in different domains.  They are both Exchange 2007 SP3 with the latest rollup installed.  

The sending server has no message size limits.  The receiving server had a 50MB message size limit on the Internet receive connector.  I got a complaint from a user at the receiving end that someone had sent him a message with a 42MB attachment and it was rejected, so I began testing.

First I checked the message size limit on all the receive connectors and found one that had a 20MB limit.  I didn't think this connector should be affecting the Internet receive limits at all, but I changed it anyway.  I tried sending a 43MB attachment, and it was rejected.  Because they use an outside anti-spam/virus filtering service, I checked with them. They did not think their system was affecting this behavior. I had to change some log settings but finally found an SMTP log entry showing that the message was rejected at the receiving server because of the size limit.

Then, I tried resending it one more time and decided to check on the sending server.  In the message queue on the SENDING server, it showed the message size as 60MB. So, I changed the receiving server's limit to 75MB, and sure enough the message went through.

Now the weirdness is that in Outlook on both the sending and receiving end, the message size shows as 43MB.

Anyone have any ideas what this is about?
0
Hypercat (Deb)
Asked:
Hypercat (Deb)
  • 2
  • 2
2 Solutions
 
IvanSystem EngineerCommented:
Hi,

email with attachment can get you overhead, somewhere from 10-30%, or so. I'm not sure if there is some calculator, but there is overhead. Larger the attachment, larger overhead. I used to have limit of 10mb, but I told users that it is 8mb, so no1 would complain :)

Regards,
0
 
Hypercat (Deb)Author Commented:
I thought it might be something like that, but 17MB is a lot of overhead - closer to 50% than 30% - and obviously more than I was ever expecting to see.  Although some of our clients do deal with large attachments, we always try to discourage it.  I've never heard any statistics about it, though. Where did you get the 10-30% figure?
0
 
IvanSystem EngineerCommented:
Hi,

that is what I have came up with years of exchange administration. When you send email, you can go to EMC, Toolbox, Message Tracking and track some mail you have sent with attachment.

For instance.
I have just send email, with attachment of 10.320.754bytes (9.84MB)
When you look at message tracking, it's size is 14.126.169bytes
That is 36% larger email, because of attachment.

This was just tested on Exchange 2007, that I have. I have never send email larger then 10Mb, but I guess it can go higher then 30%, as just tested.

Regards.
0
 
VB ITSSpecialist ConsultantCommented:
The size changes due to MIME encoding that gets added onto the message by your server. The general consensus is that the size will grow by roughly 33%.

Email programs (such as Outlook) are aware of this encoding so they hide it.

Have a read of this link if you'd like some more information: http://searchexchange.techtarget.com/tip/Outbound-message-size-changes-due-to-format-conversions
0
 
Hypercat (Deb)Author Commented:
Thanks to you both for your comments.  I've been a system admin for years and simply never had occasion to check message size limits this closely before...live and learn!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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