Exchange overestimating message size limits?
Our exchange is running on 2007 sp2, and I have an issue where sending a message (with one sentence in the body and a 7.6 MB pdf attachment) from an external provider- gmail, hotmail, and yahoo- results in the following bounce:
----- Transcript of session follows -----
... while talking to [internal exchange IP]:
>>> MAIL From:<username@hotmail.com> SIZE=10588597
<<< 552 5.3.4 Message size exceeds fixed maximum message size
554 5.0.0 Service unavailable
This happens from all 3 providers, yet the same attachment (windows filesystem size shows it as 7.6 MB) sent from one mailbox server to another, passing through the same hub/transport server, is successful. Is this a problem with all 3 external senders
overestimating the message size (which seems doubtful) or exchange overestimating the message size? Is there any way to fix this in exchange?
July 8th, 2010 1:16am
Hi,
This article may be helpful for you.
http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/exchange-2007-message-size-limits.html
Seems to me a transport level setting not allowing the so long msg.
Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM)
www.HostingController.com
Free Windows Admin Tool Kit Click here and download it now
July 8th, 2010 1:45am
There is always some growth in the size of the email for encoding, and this growth can vary depending on many factors including the type of attachment, the message format being used, and the contents of the attachment. Growth of a third is not unusual depending
the encoding method used.
If you are getting the same size reported, then it has to be something about that attachment that is causing the growth. If you were to send a similar sized Word document then I would expect it would come through correctly.
Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/
July 8th, 2010 2:10am
Hi sara,
Agree with Sembee, the attachement size would grow larger than the intial size, depend on different encoded. And the email message which incoming from the ineternet pass through different size limits is also different from the
internal transfer.
If so, I would configure the connector/ORG limits more larger to meet the user's need, yet, it is not good too large.
Regards!
Gavin
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2010 11:40am
Hello all,
I have tried changing the settings for the global/org recieve to 15 MB, and for the send connector and the recieve connector, no settings on the mailboxes- and still messages of less than 10 MB are being bounced- current message is:
Delivery has failed to these recipients or
distribution lists:
myaddress@myschool.edu
This message exceeds the maximum message size allowed.
Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller -- by removing attachments, for example -- and try sending it again, or provide the following diagnostic text to your system administrator.
Sent by
Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: mydomain.net
myaddress@myschool.edu
#550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender ##
Original message headers:
eceived: from maile.myschool.edu (192.168.111.132) by email.myschool.edu
(172.25.1.175) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 14 Jul
2010 11:17:26 -0600
Received: from web111714.mail.gq1.yahoo.com (web111714.mail.gq1.yahoo.com
[67.195.23.112]) by maile.myschool.edu (8.13.1/8.13.1) with SMTP id
o6EHH7Vt022755 for <myaddress@myschool.edu>; Wed, 14 Jul 2010 11:17:07 -0600
Received: (qmail 66489 invoked by uid 60001); 14 Jul 2010 17:17:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1279127823; bh=nqTIWyy8xwO+lRffBqZycTOKPcb1ZfQXqgk9gFQ/1mQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=h1CQ/epggBfWaxLq8KgXHJeUXky8Oked6/q38frsAm9Z8mgyRPSLnF4JhDXUirbud5TTwKFjZw5EY87GMQPercjExFb/U5oGY5FU70iDXyT6X/niPnG/d02GoYN/NHrGPV0Kg+ZTE6ORgVYxtpikLY+K8t8LYu1bBCX09aYmsUQ=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type;
b=XSHiNoJrlJZR2JjZXI3NlKLLEc/1XKzILjErSTT7X6HJAhEhYoXogjC5PNp8lijF56Po4tVd0S7x3ZE9XwVZ1aoWNCaRPLNjNgS/R8xkj1DH8Sy7bI+ewWuPjpMo+uWwB6Rn+Va1RtS5oz8tRdg1zq4upRnAy4FpHoRwbMCYkHE=;
Message-ID: <231537.64984.qm@web111714.mail.gq1.yahoo.com>
X-YMail-OSG: zJjGiVIVM1nBYobdTRF.hd2FtwKdPfwfZkE1cpJOl41_sfJ
OZFAFYcN4X8pK20inrPJF66580u.p36CteoYQRhshEeVaEaKTk7AD.jVlsL5
Eq2FELlNWx4nLX_SzJR8.uxVLHeW0TcCj3pzTjkIXm34ymDDbouONFKwPjLg
vTLEJakb6.p6BwqJvDHfHdqPvKeHoqxvdIDF27Z8zkgKeCKIbF3ersJg0G1S
6F0gFePpuzvA6mjkccZ8Tl9vvr1qI3JHpxMPkCCzwofsw1f6DHUNn6Kc9DD8
7t71jA4Addqdc3WFwWMbK4kkz3cMDKvhTFB8n
Received: from [207.93.211.50] by web111714.mail.gq1.yahoo.com via HTTP; Wed,
14 Jul 2010 10:17:02 PDT
X-Mailer: YahooMailClassic/11.2.4 YahooMailWebService/0.8.104.276605
Date: Wed, 14 Jul 2010 10:17:01 -0700
From: s porter <yahootest@yahoo.com>
Subject: test after 15 MB
To: <myaddress@myschool.edu>
CC: <rechizen@myschool.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1173852712-1279127822=:64984"
X-Spam-Score: undef - yahootest@yahoo.com is whitelisted.
X-CanIt-Geo: ip=67.195.23.112; country=US; region=CA; city=Sunnyvale; postalcode=94089; latitude=37.4249; longitude=-122.0074; metrocode=807; areacode=408;
http://maps.google.com/maps?q=37.4249,-122.0074&z=6
X-CanItPRO-Stream: myaddress (inherits from 30_Block_Vote,default)
X-Canit-Stats-ID: 10855237 - 3fa502e8675d
X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.168.111.132
Return-Path: yahootest@yahoo.com
Content-Length: 10398
July 14th, 2010 8:26pm
Hi Sara,
Please analyze the tracking log to cnfirm the issue?
Regards!
Gavin
Free Windows Admin Tool Kit Click here and download it now
July 17th, 2010 6:53am
Check out this article on each of the various areas where limits can be applied.
http://exchangepedia.com/2007/09/exchange-server-2007-setting-message-size-limits.html
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
July 24th, 2010 9:36pm
Hi Gavin,
The exchange log shows the same error- 550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender
I tried attachments of a large .pdf and a different message with several large .jpg files. Both failed with the same 5.2.3. I'm bouncing the servers tonight and if it still fails I'll probably have to call MS. I'll try and post
the solution either way.
Scott- that's a great guide, but I think I've already covered the possible areas that apply to our org. I did change the send limit for the hub/transport server to 15 MB a few days ago in case that is the "sender" the error is referring to (cuz
it would be too helpful to actually specify WHICH sender... ). It hasn't worked so far, but perhaps it will after a reboot.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2010 11:02pm
Does Exchange accept mesages directly from the internet?
Do a simple test. Telnet to the Hub transport on port 25 and issue an EHLO command and see what is listed for SIZE.
It's important that you do this from a server that is allowed access to the Hub Transport internet receive connector so the maximum allowed mesage size is shown for the messages sent from the internet.
July 24th, 2010 11:27pm
Hi Andy,
I did the telnet from one of the mailbox servers to the hub transport, and the ehlo simply gave this:
250-SIZE
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH NTLM
250-8BITMIME
250-BINARYMIME
250 CHUNKING
So I don't really know what that means.
But-
The solution, for me, and for those who might be following this was:
changing the settings for the global/org recieve to 15 MB (15360 KB) AND changing the global/org SEND limit to 15 MB (this was the part that did not really make sense to me, but I guess even if you say your hub/transpot can send 15 MB, it can't unless
the org allows it). Also changed the limit for the send connector and the recieve connector to 15 MB, no settings on the mailboxes.
After this, had to reboot the hub/transport and mailbox servers.
I can now recieve a message with a 7.6 MB pdf from external mail sources like yahoo, etc.
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2010 11:01pm
Hi Sara,
If you didnt see the SIZE value listed, ( and based on the other verbs listed there), it means you didnt connect to the receive connector used for messages from the internet.
July 26th, 2010 11:31pm
On Mon, 26 Jul 2010 20:31:16 +0000, AndyD_ wrote:
>If you didnt see the SIZE value listed, ( and based on the other verbs listed there), it means you didnt connect to the receive connector used for messages from the internet.
.. . . or maybe the Receive Connector uses "Externally secured" on the
"Permissions" tab.
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2010 2:34am