Dan Carp
asked on
Exchange 2013 Message Size Limits
I've been attempting to increase our Exchange 2013 message size limit (for received messages, not for sent) from 10 MB to 15MB. My transport config is as follows:
Receive connectors are as follow:
When I run the following command, all users come back with unlimited receive sizes:
Lastly, I rebooted our Exchange server to ensure all services had restarted. When I send a message with attachments slightly over 10MB, I still find the following error in our logs:
I've scoured the internet, but can't seem to find what I am missing. Could somebody help me find what I expect is the obvious answer beneath my nose? Thanks!
[PS] C:\Windows\system32>get-transportconfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 15 MB (15,728,640 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 15 MB (15,728,640 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : 15 MB (15,728,640 bytes)
MaxRecipientEnvelopeLimit : 5000
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : 10 MB (10,485,760 bytes)
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : False
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : TrueReceive connectors are as follow:
[PS] C:\Windows\system32>get-receiveconnector | ft name, maxmessagesize
Name MaxMessageSize
---- --------------
Default SERVER 15 MB (15,728,640 bytes)
Client Proxy SERVER 15 MB (15,728,640 bytes)
Default Frontend SERVER 15 MB (15,728,640 bytes)
Outbound Proxy Frontend SERVER 36 MB (37,748,736 bytes)
Client Frontend SERVER 15 MB (15,728,640 bytes)
Copiers SERVER 35 MB (36,700,160 bytes)
Special1 SERVER 15 MB (15,728,640 bytes)
Special2 SERVER 15 MB (15,728,640 bytes)When I run the following command, all users come back with unlimited receive sizes:
[PS] C:\Windows\system32>get-mailbox | ft Name, MaxReceiveSizeLastly, I rebooted our Exchange server to ensure all services had restarted. When I send a message with attachments slightly over 10MB, I still find the following error in our logs:
PSComputerName RunspaceId PSShowComputerName Timestamp ClientIp ClientHostname ServerIp ServerHostname SourceContext ConnectorId Source EventId InternalMessageId MessageId Recipients RecipientStatus TotalBytes RecipientCount RelatedRecipientAddress Reference MessageSubject Sender ReturnPath Directionality TenantId OriginalClientIp MessageInfo MessageLatency MessageLatencyType EventData
-------------- ---------- ------------------ --------- -------- -------------- -------- -------------- ------------- ----------- ------ ------- ----------------- --------- ---------- --------------- ---------- -------------- ----------------------- --------- -------------- ------ ---------- -------------- -------- ---------------- ----------- -------------- ------------------ ---------
servr.org.com 7e921223-0471-4626-88a1-fc664207ee81 False 5/24/2015 10:06:27 AM 192.168.xxxx servr.org.com 192.168.xxxx servr 08D2644194F1E7A0;2015-05-24T14:06:18.404Z;0 servr\Default servr SMTP RECEIVE 39479339384834 <CAHHHUP6rkwZx5q4uaYFjHrWcEk=toHJsCSjFNyHxsinMZa+WDA@mail.gmail.com> {user1@orgxyz123.com} {} 11345312 1 Fwd: 7.9 MB user22@gmail.com user11111111111111@gmail.com Incoming 209.85.192.182 0cA: None {[FirstForestHop, servr.org.com], [ProxiedClientIPAddress, 209.85.192.182], [ProxiedClientHostname, mail-pd0-f182.google.com], [ProxyHop1, servr.org.com(192.168.xxxx)], [DeliveryPriority, Normal], [OriginalFromAddress, user11111111111111@gmail.com], [AccountForest, org.com], [PurportedSender, user11111111111111@gmail.com]}
servr.org.com 7e921223-0471-4626-88a1-fc664207ee81 False 5/24/2015 10:06:28 AM servr ROUTING FAIL 39479339384834 <CAHHHUP6rkwZx5q4uaYFjHrWcEk=toHJsCSjFNyHxsinMZa+WDA@mail.gmail.com> {user1@orgxyz123.com} {[{LRT=};{LED=550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization};{FQDN=};{IP=}]} 11345312 1 {<59db0612-666b-4378-a477-2d7dfd2b3331@servr.org.com>} Fwd: 7.9 MB user22@gmail.com user11111111111111@gmail.com Incoming None {[DeliveryPriority, Normal], [OriginalFromAddress, user11111111111111@gmail.com], [AccountForest, org.com]} I've scoured the internet, but can't seem to find what I am missing. Could somebody help me find what I expect is the obvious answer beneath my nose? Thanks!
Also what are you using for your smart host? I would check if you have any restrictions there as well.
Does this issue happen when you send internally?
As Peter stated, it is most likely the send connector. I would just also check your smart host or edge server.
Will.
Does this issue happen when you send internally?
As Peter stated, it is most likely the send connector. I would just also check your smart host or edge server.
Will.
ASKER
Peter - send connector max is 10MB (confirmed via your command). I don't desire to change the max send size, but could if this has an impact on receive size. Are they tied together and expected to be changed at the same time?
Will - to be honest, smart host is a new term to me. Is this my ISP? We don't have a separate edge server - running a single Exchange server for our environment.
FYI, in case it makes any difference, the reason why I'm looking to do this is because I've recently implemented inbound message size restrictions via Google Apps. The advantage of doing so is that recipients now receive the content of a message with "ATTACHMENT STRIPPED" prepended to the subject (rather than the too large message simply being blackholed). We still want 10 MB limits for both incoming and outgoing messages, but incoming limits are handled via Google Apps and outgoing remain handled by Exchange. If I try to send over 10MB internally, the send restriction still applies (a warning message stating "The file you're attaching is bigger than the server allows. Try putting the file in a shared location and sending a link instead."). To confirm, the message is definitely getting through Google Apps successfully and hitting our Exchange server in tact and with a message size under the 15 MB Exchange defined limit.
Will - to be honest, smart host is a new term to me. Is this my ISP? We don't have a separate edge server - running a single Exchange server for our environment.
FYI, in case it makes any difference, the reason why I'm looking to do this is because I've recently implemented inbound message size restrictions via Google Apps. The advantage of doing so is that recipients now receive the content of a message with "ATTACHMENT STRIPPED" prepended to the subject (rather than the too large message simply being blackholed). We still want 10 MB limits for both incoming and outgoing messages, but incoming limits are handled via Google Apps and outgoing remain handled by Exchange. If I try to send over 10MB internally, the send restriction still applies (a warning message stating "The file you're attaching is bigger than the server allows. Try putting the file in a shared location and sending a link instead."). To confirm, the message is definitely getting through Google Apps successfully and hitting our Exchange server in tact and with a message size under the 15 MB Exchange defined limit.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for clarifying, Will. Google Apps is the filtering service (smart host?) we are utilizing. I can trace the message through their logs and confirm that it is being delivered successfully (and in tact) to our Exchange server. For some reason, it seems that the Exchange server is still flagging the message as too large even though based on the tracking log the message is showing as 11345312 bytes (10.8 MB).
Did you restart the Hub Transport service after making the change, it may not apply the change until that is done?
ASKER
Thanks Peter - always a good question. I did restart that one and a couple other recommended services. Since the issue persisted, I then even rebooted the server during off hours to make certain nothing on that front was missed. Tested again and still the same problem.
Strange, must have mussed a setting somewhere. Check the Global settings again.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the recommendations... here's the latest output, noting that nothing has been adjusted since my last server reboot. Note also that I'm only trying to adjust receive limits, not send limits, so I have omitted most send related commands.
[PS] C:\Windows\system32>Get-TransportConfig | ft MaxSendSize, MaxReceiveSize
MaxSendSize MaxReceiveSize
----------- --------------
10 MB (10,485,760 bytes) 15 MB (15,728,640 bytes)
[PS] C:\Windows\system32>Get-ReceiveConnector | ft name, MaxMessageSize
Name MaxMessageSize
---- --------------
Default SERVER 15 MB (15,728,640 bytes)
Client Proxy SERVER 15 MB (15,728,640 bytes)
Default Frontend SERVER 15 MB (15,728,640 bytes)
Outbound Proxy Frontend SERVER 36 MB (37,748,736 bytes)
Client Frontend SERVER 15 MB (15,728,640 bytes)
Copiers SERVER 35 MB (36,700,160 bytes)
Special1 SERVER 15 MB (15,728,640 bytes)
Special2 SERVER 15 MB (15,728,640 bytes)
[PS] C:\Windows\system32>Get-mailbox | ft Name, MaxSendSize, MaxReceiveSize
Name MaxSendSize MaxReceiveSize
---- ----------- --------------
USER 01 Unlimited Unlimited
USER 02 Unlimited Unlimited
USER 03 Unlimited Unlimited
USER 04 Unlimited Unlimited
USER 05 Unlimited Unlimited
USER 06 Unlimited Unlimited
USER 07 Unlimited Unlimited
USER 08 Unlimited Unlimited
USER 09 Unlimited Unlimited
USER 10 Unlimited Unlimited
USER 11 Unlimited Unlimited
USER 12 Unlimited Unlimited
USER 13 Unlimited Unlimited
USER 14 Unlimited Unlimited
USER 15 Unlimited Unlimited
USER 16 Unlimited Unlimited
USER 17 Unlimited Unlimited
USER 18 Unlimited Unlimited
USER 19 Unlimited Unlimited
USER 20 Unlimited Unlimited
USER 21 Unlimited Unlimited
USER 22 Unlimited Unlimited
USER 23 Unlimited Unlimited
USER 24 Unlimited Unlimited
USER 25 Unlimited Unlimited
USER 26 Unlimited Unlimited
USER 27 Unlimited Unlimited
USER 28 Unlimited Unlimited
USER 29 Unlimited Unlimited
USER 30 Unlimited Unlimited
USER 31 Unlimited Unlimited
USER 32 Unlimited Unlimited
USER 33 Unlimited Unlimited
USER 34 Unlimited Unlimited
USER 35 Unlimited Unlimited
USER 36 Unlimited Unlimited
USER 37 Unlimited Unlimited
USER 38 Unlimited Unlimited
USER 39 Unlimited Unlimited
USER 40 Unlimited Unlimited
USER 41 Unlimited Unlimited
USER 42 Unlimited Unlimited
USER 43 Unlimited Unlimited
USER 44 Unlimited Unlimited
USER 45 Unlimited Unlimited
USER 46 Unlimited Unlimited
USER 47 Unlimited Unlimited
USER 48 Unlimited Unlimited
USER 49 Unlimited Unlimited
USER 50 Unlimited Unlimited
USER 51 Unlimited Unlimited
USER 52 Unlimited Unlimited
USER 53 Unlimited Unlimited
USER 54 Unlimited Unlimited
USER 55 Unlimited Unlimited
USER 56 Unlimited Unlimited
USER 57 Unlimited Unlimited
USER 58 Unlimited Unlimited
USER 59 Unlimited Unlimited
USER 60 Unlimited Unlimited
USER 61 Unlimited Unlimited
USER 62 Unlimited Unlimited
[PS] C:\Windows\system32>ASKER
I've reconfirmed that everything relevant from this article has been addressed:
https://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
The only item I haven't touched is client-specific message size limits, but I don't think that should affect us since incoming messages are being rejected at the server level. Any other thoughts?
https://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
[PS] C:\Windows\system32>get-transportconfig | fl maxreceivesize
MaxReceiveSize : 15 MB (15,728,640 bytes)
[PS] C:\Windows\system32>get-transportrule
[PS] C:\Windows\system32>get-receiveconnector | fl maxheadersize, maxmessagesize
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 15 MB (15,728,640 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 15 MB (15,728,640 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 15 MB (15,728,640 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 36 MB (37,748,736 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 15 MB (15,728,640 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 35 MB (36,700,160 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 15 MB (15,728,640 bytes)
MaxHeaderSize : 128 KB (131,072 bytes)
MaxMessageSize : 15 MB (15,728,640 bytes)
[PS] C:\Windows\system32>get-adsitelink
Name ADCost ExchangeCost Sites
---- ------ ------------ -----
DEFAULTIPSITELINK 100 {domain.com/Configuration/Site...
[PS] C:\Windows\system32>get-adsitelink | fl maxmessagesize
MaxMessageSize : Unlimited
[PS] C:\Windows\system32>get-deliveryagentconnector
Name AddressSpaces DeliveryProtocol Enabled
---- ------------- ---------------- -------
Text Messaging Deliver... {MOBILE:*;1} MOBILE True
[PS] C:\Windows\system32>get-deliveryagentconnector | fl maxmessagesize
MaxMessageSize : Unlimited
[PS] C:\Windows\system32>get-foreignconnector
[PS] C:\Windows\system32>get-transportservice
Name MessageTrackingLogEnabled
---- -------------------------
SERVER True
[PS] C:\Windows\system32>get-transportservice | fl pickupdirectorymaxheadersize
PickupDirectoryMaxHeaderSize : 64 KB (65,536 bytes)
[PS] C:\Windows\system32>The only item I haven't touched is client-specific message size limits, but I don't think that should affect us since incoming messages are being rejected at the server level. Any other thoughts?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Peter - I didn't expect that those settings would impact retrieving messages through Outlook, but I just went through and modified all values to 20MB maximums and left as is those that were set to 64MB. Additionally, I upped the max receive limits for the org and all receive connectors to 20MB to ensure that there was more than sufficient headroom. To further confirm, I'm testing with an email from an external Gmail account with slightly under 8MB of attachments (which Exchange interprets as 11345243 bytes / 10.8 MB per log message below).
I rebooted the Exchange server to ensure all necessary services had restarted, then tested again. Still no luck.
{[{LRT=};{LED=550 5.2.3 RESOLVER.RST.SendSizeLimit
I rebooted the Exchange server to ensure all necessary services had restarted, then tested again. Still no luck.
{[{LRT=};{LED=550 5.2.3 RESOLVER.RST.SendSizeLimit
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No solution found.
Get-SendConnector | fl *max*