Weird behavior of message size limits in Exchange 2007

Posted on 2015-01-16
Medium Priority
Last Modified: 2015-01-19
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?
Question by:Hypercat (Deb)
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
  • 2
  • 2
LVL 17

Assisted Solution

Ivan earned 1000 total points
ID: 40554440

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

LVL 38

Author Comment

by:Hypercat (Deb)
ID: 40554494
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?
LVL 17

Expert Comment

ID: 40554524

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.

LVL 24

Accepted Solution

VB ITS earned 1000 total points
ID: 40555088
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
LVL 38

Author Closing Comment

by:Hypercat (Deb)
ID: 40557837
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!

Featured Post

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

Question has a verified solution.

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

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

764 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