arghosrho
asked on
Exchange 2016 Size restrictions.
i have a working Exchange system and the owners want to use it for file sharing as well in a very simple way. they just want to be able to send really really large emails to each other and to a variety of their clients that actually has no issue receiving hundreds of megabytes in one email.
based on that I increased all the settings to the maximum 2407MB i walked through every web.config file that exchange has and modified it as well.
never the less when they send emails to external clients they get the following
Your message wasn't delivered to anyone because it's too large. The limit is 35 MB. Your message is 85 MB.
Your message is larger than the size limit for messages. Please make it smaller and try sending it again.
Requested gave this error:
SMTPSEND.OverAdvertisedSiz e; message size exceeds fixed maximum size
in the following lines you will see the Transport seetings.
[PS] C:\Windows\system32>Get-Tr ansportCon fig | ft MaxSendSize, MaxReceiveSize
MaxSendSize MaxReceiveSize
----------- --------------
1.999 GB (2,146,435,072 bytes) 1.999 GB (2,146,435,072 bytes)
[PS] C:\Windows\system32>Get-Se ndConnecto r | ft name, MaxMessageSize
Name MaxMessageSize
---- --------------
internet Unlimited
AddressBookPolicyRoutingEn abled : False
AnonymousSenderToRecipient RatePerHou r : 1800
ClearCategories : True
ConvertDisclaimerWrapperTo Eml : False
DSNConversionMode : PreserveDSNBody
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetecti onEnabled : True
ExternalDsnMaxMessageAttac hSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthor ity :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetecti onEnabled : True
InternalDsnMaxMessageAttac hSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthor ity :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationE nabled : False
LegacyArchiveJournalingEna bled : False
LegacyArchiveLiveJournalin gEnabled : False
RedirectUnprovisionedUserM essagesFor LegacyArch iveJournal ing : False
RedirectDLMessagesForLegac yArchiveJo urnaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : 1.999 GB (2,146,435,072 bytes)
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShad ow : 2
MaxRetriesForRemoteSiteSha dow : 4
MaxSendSize : 1.999 GB (2,146,435,072 bytes)
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailu re : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardIn terval : 2.00:00:00
ShadowMessagePreferenceSet ting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
[PS] C:\Windows\system32>Get-Tr ansportCon fig | ft name, MaxSendSize, MaxReceiveSize, ExternalDSNMaxMessageAttac hSize
Creating a new session for implicit remoting of "Get-TransportConfig" command...
Name MaxSendSize MaxReceiveSize ExternalDsnMaxMessageAttac hSize
---- ----------- -------------- -------------------------- -----
Transport Settings 1.999 GB (2,146,435,072 bytes) 1.999 GB (2,146,435,072 bytes) 1.999 GB (2,146,435,072 bytes)
as far as i can see all the sizes are far above this 35MB limit that the system keep complaining about.
can someone help me out ?
based on that I increased all the settings to the maximum 2407MB i walked through every web.config file that exchange has and modified it as well.
never the less when they send emails to external clients they get the following
Your message wasn't delivered to anyone because it's too large. The limit is 35 MB. Your message is 85 MB.
Your message is larger than the size limit for messages. Please make it smaller and try sending it again.
Requested gave this error:
SMTPSEND.OverAdvertisedSiz
in the following lines you will see the Transport seetings.
[PS] C:\Windows\system32>Get-Tr
MaxSendSize MaxReceiveSize
----------- --------------
1.999 GB (2,146,435,072 bytes) 1.999 GB (2,146,435,072 bytes)
[PS] C:\Windows\system32>Get-Se
Name MaxMessageSize
---- --------------
internet Unlimited
AddressBookPolicyRoutingEn
AnonymousSenderToRecipient
ClearCategories : True
ConvertDisclaimerWrapperTo
DSNConversionMode : PreserveDSNBody
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage
ExternalDsnLanguageDetecti
ExternalDsnMaxMessageAttac
ExternalDsnReportingAuthor
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage
InternalDsnLanguageDetecti
InternalDsnMaxMessageAttac
InternalDsnReportingAuthor
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationE
LegacyArchiveJournalingEna
LegacyArchiveLiveJournalin
RedirectUnprovisionedUserM
RedirectDLMessagesForLegac
MaxDumpsterSizePerDatabase
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : 1.999 GB (2,146,435,072 bytes)
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShad
MaxRetriesForRemoteSiteSha
MaxSendSize : 1.999 GB (2,146,435,072 bytes)
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailu
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardIn
ShadowMessagePreferenceSet
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled
HeaderPromotionModeSetting
Xexch50Enabled : True
[PS] C:\Windows\system32>Get-Tr
Creating a new session for implicit remoting of "Get-TransportConfig" command...
Name MaxSendSize MaxReceiveSize ExternalDsnMaxMessageAttac
---- ----------- -------------- --------------------------
Transport Settings 1.999 GB (2,146,435,072 bytes) 1.999 GB (2,146,435,072 bytes) 1.999 GB (2,146,435,072 bytes)
as far as i can see all the sizes are far above this 35MB limit that the system keep complaining about.
can someone help me out ?
Dont forget some ISP's set a physical limit on the email traffic that passes thru their routers and SMTP servers.
I attended a course in specialized TCP/IP protocols and transport. ISP engineers attended too. They explained that one users email with a huge attachment had the potential to create congestion in their own network and had set limits on what they would allow pass thru. Of the 20 odd students it created quite a bit of debate. Some felt the ISP's shouldn't do this, while others could see why they did.
You may just find that the messages wont reach some recipients for this reason alone.
I attended a course in specialized TCP/IP protocols and transport. ISP engineers attended too. They explained that one users email with a huge attachment had the potential to create congestion in their own network and had set limits on what they would allow pass thru. Of the 20 odd students it created quite a bit of debate. Some felt the ISP's shouldn't do this, while others could see why they did.
You may just find that the messages wont reach some recipients for this reason alone.
ASKER
the User mailboxes are all unlimited due to the idea that they need to upload and send gigantic files.
the refusal we are getting is indeed not internal. its when they try to send pictures to live/Hotmail
@tahir and all my limits are set to 2gb as you can see in the posted above code. so running those commands wouldn't cause difference i assume. would it?
the refusal we are getting is indeed not internal. its when they try to send pictures to live/Hotmail
@tahir and all my limits are set to 2gb as you can see in the posted above code. so running those commands wouldn't cause difference i assume. would it?
This is going to be a nightmare for you as an administrator of Exchange. What is the total number of mailboxes you have? This setup will balloon Mailboxes to sizes that are not recommend by MS.
Some things to consider:
Some things to consider:
- The larger the mailbox gets the system will be taxed and users will experience performance impacts.
- If you attempt to send this to an external person 99.99% chance the recipient's server will reject the email.
- If you send 2 GB attachment to five internal mailboxes you will have 10 GB worth of space used up. Just think about the growth over time. It will be a nightmare to handle.
- Exchange was never meant to be used as a file sharing system. You may want to look at other technologies like a SharePoint Server or Citrix ShareFile
I agree with a lot of the statements made. This is going to be a nightmare as you have no control over external ISP receive limits. You would be better off setting up a Moveit SFTP server and allowing them to move files via it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i agree with you Gentlemen. but no one will send such large files. this is just removing limitations. the biggest ever will be much lesser than 100MB
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
so. no one thinks the problem is in my exchange? it's more in the people receiving the message?
Yes.
may I know, are you using web mail to send email or outlook?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i guess ill do that, i did what i could to make it work. but i can't control the world for that matter
Note: provide figure in MB
Open in new window