Exchange Server Forums

MaxReceiveSize is not applied

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Management >> MaxReceiveSize is not applied

Page: [1]

Message

<< Older Topic Newer Topic >>

MaxReceiveSize is not applied - 24.Jan.2012 5:24:16 AM

Tonio

Posts: 2
Joined: 24.Jan.2012
Status: offline

Hi guys,

We have 2 mailbox servers, 2 HUB/CAS servers and 2 Edge servers in DMZ.
On all servers OS is Win2008 SE sp2 and Exchange 2007 sp3 ur5.
The problem is: Edge servers don't block incoming messages bigger than 20MB (in spite of the settings).

On HUBs:

[PS] C:\Windows\system32>Get-TransportConfig | fl

ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : PreserveDSNBody
GenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
InternalSMTPServers : {list of my internalSMTP servers}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
MaxDumpsterSizePerStorageGroup : 62MB
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : 20MB
MaxRecipientEnvelopeLimit : 5000
MaxSendSize : 20MB
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
WritingBrandingInDSNEnabled : True
Xexch50Enabled : True

Get-ReceiveConnector and Get-SendConnector on both HUBs and Edges show MaxMessageSize : 20MB

Synchronization test doesn't show any issues.

However, on both Edges get-transportconfig returns:

ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
GenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
InternalSMTPServers : {list of my internalSMTP servers}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
MaxDumpsterSizePerStorageGroup : 18MB
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : unlimited
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize : 20MB
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
WritingBrandingInDSNEnabled : True
Xexch50Enabled : True

MS says that the MaxDumpsterSizePerStorageGroup, MaxDumpsterTime, MaxReceiveSize and MaxRecipientEnvelopeLimit properties are not used by Edge Transport servers, but it's not really working as designed cause my Edges don't reject the messages bigger than 20 MB (actually they are trying to receive them, but smtp session is being closed on timeout. Errors in smtp protocol log - 421 4.4.1 Connection timed out)

I tried to remove the subscription, restart Transport service on HUBs, export/import new subscription file to HUBs and pushing the synchronization, but still MaxReceiveSize is unlimited on both Edges.

Any ideas how to set MaxReceiveSize = 20MB on Edge servers and how to force the servers to use this settings?

Post #: 1

Featured Links*

RE: MaxReceiveSize is not applied - 24.Jan.2012 5:03:59 PM

John Weber

Posts: 1208
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline

I will take a guess at Set-TransportServer or Set-TransportConfig

Use the Set-TransportServer cmdlet to set the transport configuration options for computers running Microsoft Exchange Server 2010 that have the Hub Transport server role or Edge Transport server role installed.

Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Microsoft Exchange Server 2010 organization

Take a look at this here, very helpful...I have used it numerous times and it still valid for 2010.
http://tsoorad.blogspot.com/2008/05/e2k7-message-size-limits.html

_____________________________

John Weber [Lync MVP] http://tsoorad.blogspot.com

(in reply to Tonio)

Post #: 2

RE: MaxReceiveSize is not applied - 25.Jan.2012 8:02:48 AM

Tonio

Posts: 2
Joined: 24.Jan.2012
Status: offline

John, of course I checked that article. Set-TrasnportServer has nothing in common with Maxmessagesize. The results of Get-TransportConfig I posted previously. Settings are obviously different and I have no clue why they are not being synchronized.

Test-synchronization on Hub returns this:

[PS] C:\Windows\system32>Test-EdgeSynchronization

Name : Edge01
LeaseHolder : Hub01
LeaseType : Option
ConnectionResult : Succeeded
FailureDetail :
LeaseExpiry : 25/01/2012 14:48:15
LastSynchronized : 25/01/2012 13:48:15
CredentialStatus : Synchronized
TransportServerStatus : Synchronized
TransportConfigStatus : Synchronized
AcceptedDomainStatus : Synchronized
SendConnectorStatus : Synchronized
MessageClassificationStatus : Synchronized
RecipientStatus : Synchronized
CredentialRecords : Number of credentials 6

Name : Edge02
LeaseHolder : SHub01
LeaseType : Option
ConnectionResult : Succeeded
FailureDetail :
LeaseExpiry : 25/01/2012 14:48:16
LastSynchronized : 25/01/2012 13:48:16
CredentialStatus : Synchronized
TransportServerStatus : Synchronized
TransportConfigStatus : Synchronized
AcceptedDomainStatus : Synchronized
SendConnectorStatus : Synchronized
MessageClassificationStatus : Synchronized
RecipientStatus : Synchronized
CredentialRecords : Number of credentials 6

(in reply to John Weber)

Post #: 3