Total Attachment Size Restrict - Exchange 2010

Hi Guys,
Am trying to create a Transport rule to restrict attachment size for a particular group members. (restriction to 1MB total attachment size)
The problem is that when a member of user tries to send email with four attachment(300KB x 4nos.) which exceeds 1MB he/she is still able to send emails.
When a users send single attachment of 1MB above, he/she gets the NDR which is what am expecting.
Reference:- http://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx
Attachment size limits These limits apply to the maximum allowed size of a
single attachment within a message. The message may contain many attachments that greatly increase the overall size of the message. However, an attachment size limit applies to the size of an individual attachment only.
How to restrict total/sum size of all attachment which exceeds 1MB?
- Charles

Hi,
Based on my knowledge, we can't limit total attachment size for a message directly. But As Ed said, we can use message size limit to limit the total size of a message as a workaround.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

DB size for exchange 2010

Hello,
How do I find out the database size in Exchange 2010 please?
Kind Regards,
Jerome

You can use powershell commandlet.
Get-MailboxDatabase -Status | FL ServerName, Name, DatabaseSize
Regards
SK

Entourage 2008 EWS Attachment limit on Exchange 2010

Hi Folks,
I'm having a problem allowing my Entourage users to attach files larger than 10MB. I've looked through all of the potential attachment limits on Transport config/Send connectors/Receive connectors/Users mailbox settings, but they all look okay to me.
[PS] C:\Windows\system32>get-mailbox user | fl max*
MaxSafeSenders    :
MaxBlockedSenders :
MaxSendSize       : 150 MB (157,286,400 bytes)
MaxReceiveSize    : 150 MB (157,286,400 bytes)
[PS] C:\Windows\system32>get-sendconnector | fl max*
MaxMessageSize : 150 MB (157,286,400 bytes)
MaxMessageSize : 150 MB (157,286,400 bytes)
[PS] C:\Windows\system32>get-receiveconnector | fl max*
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : unlimited
MaxInboundConnectionPercentagePerSource : 100
MaxHeaderSize                           : 64 KB (65,536 bytes)
MaxHopCount                             : 30
MaxLocalHopCount                        : 8
MaxLogonFailures                        : 3
MaxMessageSize                          : 150 MB (157,286,400 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 5000
MaxAcknowledgementDelay                 : 00:00:30
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize                           : 64 KB (65,536 bytes)
MaxHopCount                             : 30
MaxLocalHopCount                        : 8
MaxLogonFailures                        : 3
MaxMessageSize                          : 150 MB (157,286,400 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 200
MaxAcknowledgementDelay                 : 00:00:30
[PS] C:\Windows\system32>get-transportconfig | fl max*
MaxDumpsterSizePerDatabase : 100 MB (104,857,600 bytes)
MaxDumpsterTime            : 7.00:00:00
MaxReceiveSize             : 150 MB (157,286,400 bytes)
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize                : 150 MB (157,286,400 bytes)
I'm running Exchange 2010 (with Rollup3 installed), on Server 2008R2.
My clients are running Entourage 2008 EWS, patched up with the latest Office Mac updates.
Apart from their inability to send 10+MB attachments, everything else is fine.
Regards,

Shane
Toutges solution worked for us. Exchange Server 2010 (current patch level as of March 2015), Mac OS Outlook 2011 via EWS.
Key to the solution is this revision:
maxReceivedMessageSize value
to [example value]
51200000 underneath the heading <EWSMessageEncoderSoap11Element />. There are 6 places to make this change (bytes)
I have not seen this noted under the several MS Tech Net articles that pertain to the problem of sending large email attachments via Mac Outlook 2011 via EWS.

What is the Exchange 2010 maximum mailbox database size that is support by MS in a single DAG environment?

My Exchange setup:
Exchange 2010 Enterprise
2 mailbox servers
2 CAS, 2 HT
12 mailbox databases. The total of all databases combine is about 2TB. The largest mailbox databases are 530GB, 250GB, and 196GB. Are this over the supported recommendations?
bl

2TB, look at the second article but best practice 200GB or less
http://social.technet.microsoft.com/Forums/exchange/en-US/48431bab-4049-47db-9a84-359d5123d247/what-is-the-maximum-supported-database-size-in-exchange-2010-
http://social.technet.microsoft.com/Forums/exchange/en-US/f96892b3-8e2d-4eef-b64a-4cbc0097396d/ideal-size-for-exchange-mailbox-database

Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2

Hi,
We are planning cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2.
Requesting you to please help us out for below scenario.
Source Exchange 2010 SP2:- abc.com
2AD, 2CAS & 2 MBX servers
Database:- 4
Total Users :- 3500
Accepted Domains :- 8
Total Data:- 5TB +
Target Exchange 2010 SP2:- xyz.com
Resource allocated same as above.
Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.
With the guidelines mentioned in
http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-14203 we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into
OWA. It gives error “The Outlook Web App address
https://mail.abc.com/owa is out of date.”
Kindly let us know how to solve this issue.
Kindly let me know if you want any more information from our end.
Thanks in advance.
Thanks and Regards, Shashank Kudi

Hi Shashank,
Do you have certificates properly installed and configured in the target Exchange?
If not, Please configure certificate and import the certificate to the trusted root CA if you are using internal CA cert.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Export Mailbox from Exchange 2010 and Import to Exchange 2007

Hello,
I exported mailbox (1GB in size) from Exchange 2010 to *.pst file; I need to import it into
Exchange 2007 mailbox. Is it supported ?
The operation completed successfully (no errors) but no items were imported; is it due to unsupported backward compatibility or some other issue ?
Thank you,
Luca
Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

I also have the same issue. Exported mailboxes on Exchange 2010 SP3 latest updates using
New-MailboxExportRequest and then tried to import into mailbox on Exchange 2007 SP3 with latest updates. The 32-bit client machine used for the import has Outlook 2010 SP1 (SP2 and later updates causes a different error). I used Outlook 2010 because the E2K10
New-MailboxExportRequest documentation states that you have to use Outlook 2010 or later. The PST files created can be opened and imported via Outlook but not with the
Import-Mailbox cmdlet (with no error as stated in this thread). Other PSTs, not created from E2K10 export do import just fine. I also ran ScanPST.exe against the exported PST and then ran the import again and it worked, everything got imported. Interestingly
the test mailbox PST file I was using was 761 KB but after the ScanPST it was 1,257 KB - must be some difference in the PST format that the Import-Mailbox cmdlet can't deal with.
Does anyone have any other solutions or
workarounds to this. I've got over 900 mailboxes I need this for due to an
acquisition? Has anyone tried using Outlook 2013 on the machine used for doing
the Exchange 2007 imports or does Outlook 2013 also have the same issue as later versions of Outlook 2010 (Exchange Mailbox import failed with error code 2147221233)?

Exchange 2013 / Outlook 2010+ Attachment size limit

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 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 : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
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 : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 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 : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
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 : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl
1. If you send a message larger than 10MB from an external client to your org, does it bounce back because its over the limit?
2. Do you see the same problem sending internally with OWA?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 - Accepting Messages Above the Attachment Size Limit

Recently we implemented a new Exchange 2010 server in a site. This site is in another country with very poor WAN connectivity. Our standard attachment limit is 50MB (51200 kb) .
Since we have put this server in place I am seeing messages get stuck in the queue that are above the 50MB limit.
What I am confused about is how are they making it there, why is Exchange accepting them? I have checked all the connectors, they are all appear to be set correctly.
What I also notice is these messages sit in the queue and get error:
421 4.4.2 Connection dropped due to ConnectionReset
Any ideas?

Consider applying an enterprise limit by using Set-TransportConfig -MaxSendSize -MaxReceiveSize.
http://technet.microsoft.com/en-us/library/bb124151(v=exchg.150).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Outlook 2010 attachment size limit

We're using a sendmail server for our email and have been using Outlook 2003 for the client. I'm evaluating Outlook 2010 but we've hit a snag. Total attachments over ~20MB result in a "The attachment size exceeds the allowable limit".
This works fine under 2003.
How can I fix this?

Hi,
First, please let us know the email server you are using. Is it Exchange and what’s the version? Also, does this issue occur on all the client computers or only
one some of the computers?
As this issue might be related to some settings on the Exchange server side, you may also contact your network administrator to check the settings on the server side.
If there are no attachment limitation settings on the server side, we can troubleshoot the issue by the steps below:
Step 1: Disable background transfer of attachments to the Exchange server.
=============
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you
follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.
1. Run regedit on the outlook client computer that has the issue.
2. Locate the following registry key:
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook]
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableBGSave
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 1
Note: You will see the Policies key if policies are deployed in your environment. If so, add the registry key under the following registry key:
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook]
4. Restart Outlook and test the issue again. Is the issue resolved? If the problem persists, let’s continue.
Step 2: Start Outlook in online mode/safe mode.
=============
1. In Outlook, click File > Info > Account settings > Account settings.
2. Click your Exchange account, and click the
Change button, then More settings,
Advanced tab. Uncheck Use cached Exchange mode.
3. Exit Outlook . Click Start, point to All Programs, and then point to
Microsoft Office.
4. Press and hold the
CTRL key, and then click Microsoft Outlook.
Is the problem resolved? If not, let’s continue.
Step 3: Create a new Outlook profile.
=============
1.    Exit Outlook.
2.
Go to Start > Control Panel, click or double-click
Mail.
Mail appears in different Control Panel locations depending upon the version of the Microsoft Windows operating system, Control Panel view selected, and whether a
32- or 64-bit operating system or version of Outlook is installed.
The easiest way to locate
Mail is to open Control Panel in Windows, and then in the
Search box at the top of window, type Mail. In
Control Panel for Windows XP, type Mail in the
Address box.
Note
The Mail icon appears after Outlook starts for the first time.
The title bar of the Mail Setup dialog box contains the name of the current profile. To select a different existing profile, click Show Profiles, select the profile
name, and then click Properties.
3.
Click Show Profiles. Choose Prompt for a profile to be used.
4.
Click Add.
5.
Type a name for the profile, and then click OK.
6.
Start Outlook, and choose this new profile.
If this problem does not occur in the new Outlook profile, the old Outlook is corrupted. We can delete that and use a new Outlook profile.
Step 4: If it still not resolved, create a new Outlook profile on another PC that does not have this issue, then check to see if it persists. This can help us to narrow
down that if the issue is specific to the machines.
Please take your time to try the suggestions and let me know the results at your earliest convenience. If anything is unclear or if there is anything I can do for
you, please feel free to let me know.
Best Regards,
Sally Tang

SBS2011 (Exchange 2010 SP2) - limiting cache size doesn't appear to work

Hi All,
Hoping for some clarification here, or extra input at least. I know there are other posts about this topic such as
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/5acb6e29-13b3-4e70-95d9-1a62fc9304ac but these have been
incorrectly marked as answer in my opinion.
To recap the issue. The Exchange 2010 store.exe process uses a lot of memory. So much in fact it has a negative performance impact on the server (sluggish access to the desktop etc). You can argue about this all day - it's by design
and shouldn't be messed with etc but the bottom line is that it does use too much memory and it does need tweaked. I know this because if you simply restart the Information Store process (or reboot the server) it frees up the memory and the performance
returns (until its cache is fully rebuilt that is). I have verified this on 4 different fresh builds of SBS2011 over the last 6 months. (all on servers with 16GB RAM)
I have scoured the internet for information on limiting how much memory exchange uses to cache the information store and most articles point back to the same two articles (http://eightwone.com/2011/04/06/limiting-exchange-2010-sp1-database-cache/
and
http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache) that deal with exchange 2010 and exchange 2010 SP1, notably not exchange 2010 SP2. Ergo most articles are out of date since exchange 2010 SP2 has been released since these articles
were posted.
When testing with our own in house SBS2011 server (with exchange 2010 SP2) I have found that specifying the min, max and cache sizes in ADSIEDIT has varying results that are not in line with the results documented in the articles I mentioned above.
I suspect the behaviour of these settings has changed with the release of exchange 2010 SP2 (as it did between the initial release and SP1).
Specifically here's what I have found using ADSIEDIT;
If you set the msExchESEParamCacheSize to a value - it doesn't have any effect.
If you set the msExchESEParamCacheSizeMax to a value - it doesn't have any effect.
If you set the msExchESEParamCacheSizeMin to a value - it always locks the store.exe process to using exactly this value.
I have also tested using combinations of these settings with the result that the size and max size values are always ignored (and the store.exe process uses the maximum available amount of memory - thus causing the performance degradation) but as soon as
you specify the min value it locks it to this value and it doesn't change.
As a temporary solution on our in-house SBS2011 I have set the min value to 4GB and it appears to be running fine (only 15 mailboxes though).
Anyone got some input on this ? thank you for your time.

I concur with Erin. I'm seeing the same behaviour across all SBS2011 boxes, whether running SP1, SP2 or SP3.
If a minimum value is set, the store cache size barely rises above the minumum. I have one server with 32GB RAM. Store.exe was using 20GB of RAM, plus all the other Exchange services which total 4GB+. That left virtually no free RAM and trying to do
anything else on the server was sluggish at best.
All the advise is that setting a maximum alone has no effect and a minimum must be set too. But when set, the store cache size barely rises above the minimum. I have set a 4GB minimum and 16GB max, but 5 days later it's still using only slightly more than
4GB and there's 8GB free. Now the server as a whole is responsive, but doing anything with Exchange is sluggish.
Just saying leave Exchange to manage itself is not an answer. The clue is in the name - Small Business Server. It's not Exchange Only Server - there are other tasks an SBS must handle so leaving Exchange to run rampant is not an option. Besides, there are
allegedly means to manage the Exchange cache size - they just don't apparently work!
I'm guessing nobody has an answer to this so the only solution is to effectively fix the cache size to a sensible value by setting min and max to the same value.
Adam@Regis IT

Problem with Exchange 2010, Q10 and attachment

Q10 & Exchange 2010; unable to download and forward attachment
Hi all,
i have a problem with Q10 phone, sync with Exchange 2010 with activesync (not BES) all seem ok but unable to download attach.
When press "download" didnt start. Unable also to forward same message but i think is a chainde problem.
Same message from desktop (outlook) or OWA is ok and attach downloadable.
This is the only Q10 present in company for test so i cannot compare to others BB.
All other users connected to the exchaneg server have iphone & ipad no issue result. Email service seem ok also for desktop.
Firmware was updateted about 10 day ago.
Any idea for me?
Thanks

Hi marcottt,
Could you provide more detail please so I can better assist?
Do you have this issue with all attachment types? If not, what type of attachment are you having this issue with and what size is the attachment?
What happens when you try to forward the message? Is any error received?
Does removing and re-adding the email account make any difference?
I look forward to your response.
-FS
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)!

Exchange 2010 - Cannot receive/send large attachements - Did all the configurations needed

Hello All,
I am using Exchange 2010 Standard Server - SP1. I am having difficulty send\receiving large attachments. I went through all the KB documents and solutions, but to still no avail. Can anyone let me know if I am missing anything else.
Below is what I have done already:
Thank you in advance!
1. Organization Configuration
Organization Configuration | Hub Transport | Global Settings tab | Transport Settings |
2. Server Configuration
Server Configuration | Hub Transport | select a HT server | Receive Connectors -> select a connector | Properties |
3. Send Connector Configuration
Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties |
4. Recipients Configuration
Recipients Configuration | Mailbox | select mailbox | properties | Mail Flow Settings | Message Size Restrictions|
5. Recipients Group Configuration
Recipients Configuration |Distribution Group | select Group | properties | Mail Flow Settings | Message Size Restrictions
6. Global Setting --- Please use adsiedit to connect Configuration container:
Configuration container | Services | Microsoft Exchange |YourOrgName| Global Settings | Message Delivery | Properties，check the below values：
a. delivContentLength
b. SubmissionContentLength
c. msExchRecipLimit
7. Transport Rules -- Organization Configuration | Hub Transport | Transport Rules

Hello All,
I am using Exchange 2010 Standard Server - SP1. I am having difficulty send\receiving large attachments. I went through all the KB documents and solutions, but to still no avail. Can anyone let me know if I am missing anything else.
The error I get is "552 5.3.4 Message size exceeds fixed maximum message size"
Below is what I have done already:
Thank you in advance!
1. Organization Configuration
Organization Configuration | Hub Transport | Global Settings tab | Transport Settings |
2. Server Configuration
Server Configuration | Hub Transport | select a HT server | Receive Connectors -> select a connector | Properties |
3. Send Connector Configuration
Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties |
4. Recipients Configuration
Recipients Configuration | Mailbox | select mailbox | properties | Mail Flow Settings | Message Size Restrictions|
5. Recipients Group Configuration
Recipients Configuration |Distribution Group | select Group | properties | Mail Flow Settings | Message Size Restrictions
6. Global Setting --- Please use adsiedit to connect Configuration container:
Configuration container | Services | Microsoft Exchange |YourOrgName| Global Settings | Message Delivery | Properties，check the below values：
a. delivContentLength
b. SubmissionContentLength
c. msExchRecipLimit
7. Transport Rules -- Organization Configuration | Hub Transport | Transport Rules

EAS Attachment size stuck at 10MB after move from 2010

We have just moved from 2010 to 2013CU3 exchange (2012 server) and all size restrictions but EAS works as expected.
OWA, outlook, Macs they all manage to both send and receive 100MB+ emails, but EAS looks to be stuck at 7MB (10).
In 2010 EAS clients had no problem with 100MB+ emails.
I've changed the values in web.conf, set the Header Request Filter value, set the values in transport config, set the values
in send and receive connectors and set the limits directly on the mailboxes.
Any EAS decive can download big attachments (100MB+) but none can send any over 7MB (10).
Trying to send 12MBs of pictures on a iPad (iOS7) results in an immediate popup telling me "cannot send, your mailbox is full".
Trying the same amount of pictures on a android phone results in the mail being stuck in outbox forever.
The same problem occurs both in my production setup, and my 2 test labs.
No warning or errors in the eventlog.
Production setup:
3 AD Servers, 2 witnes servers.
3 Exchange 2013CU3 on 2012 Server, all exch servers have all roles installed.
2 Sites connected with a 1Gbit VPN connection.
1 DAG with 3 DBs, 600GBs of mail in each DB.
I've managed exchange servers since the 2003 version and this is the first time I've not been able to make EAS work, what am I missing?

When email is sent using the ActiveSync handheld device the message size is justified with the value located in the file %ExchangeInstallPath%ClientAccess\Sync\web.config
Default Email message size in Activesync:
<add key=”MaxDocumentDataSize” value=”10240000″> (value in bytes) Approx 9.7 MB
maxRequestLength=”10240″ (value in kilobytes ) = Approx 10 MB
Ref: http://rajisubramanian.wordpress.com/2014/01/26/exchange-server-2013-message-size-configuration-detail/
http://technet.microsoft.com/en-us/library/hh529949%28v=exchg.150%29.aspx
Exchange Queries

How to Restrict Max Recipient for Inbound in Exchange 2010

Hi,
I want to restrict my inbound mails which is having more than 10 recipients (it may be TO,CC & BCC) in my Exchange 2010.
I set the limit to 10 in the following area.
1.Mailbox
2.Organization
3.Connector (for Receive connectors only)
4.Transport server
But still external users send a mail to more than 10 of our users.
Accepted domain is configured as an internal relay domain.

Hi,
Based on my knowledge, we can't restrict the inbound recipients number in Exchange server. What we can do is restrict the outbound recipients number. For an example, if you set the value of RecipientLimits to 10 for user1, then user1 can't send an message
with more than 10 recipients, but the setting can't have an effect on receiving messages. Your understanding will be appreciated.
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Outlook multi-day (not 'all day') meeting requests showing up as 1 day off on iphone attached Activesync Exchange 2010 accounts

Exchange 2010 SP2 Server
iPhone iOS 5.01 (4/4s) using ActiveSync
Outlook 2007 clients
When multi-day (not 'all day') meeting requests or appointments are being sent to email accounts which have an iPhone attached to the Exchange account via ActiveSync, the iPhone accepts the meeting request but then moves the event one day later than what it was originally scheduled and posts it to Outlook - also 1 day later than it is supposed to be.
For example: A meeting request comes into my that is schedule for 9AM-4PM M-W but when I accept it on my iphone it gets posted to my calendar as an ALL DAY event but T-Thu
We upgraded to Exchange SP2 because some of the threads were alluding that SP2 would fix it - it didn't. I know the fix is to rip out the event to separate calendar events but this will not work for reqeusts coming from outside. And this is too tedious. If anything, it is a serious bug.
Anybody seen this before?
Thanks,
Monty.

I am experiencing a similar problem with a client of mine who is using Microsoft's Cloud-based Exchange server, Office 365. I suspect the Office 365 server is an Exchange 2010 server, similar to your environment. Check out my tests below which I think define when the day shifting happens.
I see that you applied SP2 to your Exchange 2010 environment, but have you also applied Update Rollup 1? See this article: http://support.microsoft.com/kb/2563324. It would be interesting to know whether that rollup resolves your problem.
I have done some pretty extensive testing and have posted in the Office 365 Support Forum (http://community.office365.com/en-us/f/146/p/53396/192332.aspx#192332) Here is a summary of my testing.
I am having the exact same problem described by Jim Edmonds and jkwmail (http://community.office365.com/en-us/f/176/p/19921/93304.aspx#93304) with one of my clients who is not very happy about this or our inability to resolve the problem. Here is what I am experiencing:
When an appointment in Office 365 spans multiple days, the appointment gets converted to an All Day Event and moved forward one day on an iPhone ActiveSync client.
I have completed the following troubleshooting:
1 - Using my GMail Account and my work email account on MS Exchange 2007 SP 2 Server I created separate single day appointments in the morning from each account spanning two hours and invited my client who is using MS Outlook 2010 and Office 365.
    Result: The appointments show the correct date and time on my Outlook, MS Exchange 2007 SP 2 OWA, and iPhone as well as my client's Outlook, Office 365 webmail, and iPhone.
2 - Using my GMail Account and my work email account on MS Exchange 2007 SP 2 Server I created separate single day appointments in the afternoon from each account spanning two hours and invited my client who is using MS Outlook 2010 and Office 365.
    Result: The appointments show the correct date and time on my Outlook, MS Exchange 2007 SP 2 OWA, and iPhone as well as my client's Outlook, Office 365 webmail, and iPhone.
3 - Using my GMail Account and my work email account on MS Exchange 2007 SP 2 Server I created separate multi-day appointments from Friday at 5 PM to Monday at 8 AM from each account and invited my client who is using MS Outlook 2010 and Office 365.
    Result: The appointments show the correct date and time on my Outlook, MS Exchange 2007 SP 2 OWA, and iPhone as well as my client's Outlook and Office 365 webmail. However, on my client's iPhone, the time on the appointments had changed to an all day event and the start date was shifted one day forward, Saturday, and the end date was Monday unless the appointment end time was after the appointment start time in which case it created an All Day Event on Tuesday as well. For Example: If the appointment was from 8 AM Friday Morning to 8 AM Monday Morning, the iPhone would show an All Day Event on Saturday, Sunday, and Monday. If the appointment was from 8 AM Friday Morning to 8:30 AM Monday Morning, the iPhone would show an All Day Event on Saturday, Sunday, Monday, and Tuesday. If the appointment was from 8 AM Friday Morning to 7:30 AM Monday Morning, the iPhone would show an All Day Event on Saturday, Sunday, and Monday. This was also true for appointments starting on Friday at 5 PM and ending on Monday at 5 PM, starting on Friday at 5 PM and ending on Monday at 5:30 PM, and starting on Friday at 5 PM and ending on Monday at 4:30 PM as in the above AM examples.
*** Again I would like to note that on my iPhone which is connected to my company's MS Exchange 2007 SP 2 server, the multi-day appointment shows up correctly with correct start and end times and is not converted to an All Day Event. ***
It would seem this is a problem with ActiveSync on Office 365 and iOS devices. What is particularly frustrating is that this exact problem is identified in KB 2563324 (http://support.microsoft.com/kb/2563324) Issue 1.6 - "An appointment is longer than 24 hours is changed to a multi-day All Day Event" which states: "To resolve this issue, install Update Rollup 1 for Exchange Server 2010 Service Pack 2 (SP2)." Since this is a cloud based service, we do not have the ability to either see what the current version of the Exchange service we are connected to is or update the service with this patch level.
4 - I performed the above three tests with my client creating the events in MS Outlook 2010 and inviting my work account on the MS Exchange 2007 SP 2 Server and got the exact same results.
5 - My client's iPhone is running iOS 4.3 and my iPhone is running iOS 5.1.0. In order to test this without going through the update process on my client's iPhone, I set up his Office 365 account on my iPhone and performed the tests in numbers 1-4 from above, viewing the results on my iPhone, and got the exact same results.
6 - Today, I tried this with a different Office 365 account, performed the multi-day test in number 3 from above and got the exact same results.
7 - Today I also upgraded my iPhone to iOS 5.1.1, performed the multi-day test in number 3 from above and got the exact same results.
8 - I have confirmed that all time zones are set correctly. I have checked the iPhone, OWA, Office 365 Webmail, etc.
I believe the problem in my case is with the Office 365 environment and not the iOS device. However, trying to get support from these large companies seems to be very difficult?
Does anyone from Apple know if this is an iOS bug or a problem with Exchange 2010/Office 365?
Thanks...
Jp

Total Attachment Size Restrict - Exchange 2010

Similar Messages

Maybe you are looking for