Exchange 2010 Archive Database - Attachment Sizes

Greetings.  We recently set up personal archiving on our Exchange 2010 on-premises server. Mail over a certain age is moved automatically to the user's archive folder in an archive database.

Around the same time, I lowered the maximum send/receive message size from 30MB to 10MB.

One of the members of my test group informed me today that archiving is working perfectly, except that messages with large attachments are not being moved.

Are these two related ?  Is there a connection between the server moving messages automatically and the send/receive size on the Send Connector and Transport ? Interesting.

Thanks much.
-Stephen
lapavoniAsked:
Who is Participating?
 
Adam BrownConnect With a Mentor Sr Solutions ArchitectCommented:
When you drop the Send/Receive max it actually applies a maximum to the size of email that is stored anywhere on the server in the back end, so emails that break the new policy cannot be recreated in any mailbox including the archive, though they will remain where they are with no issues. This is kind of a hidden gotcha for Exchange that you never realize until something like this happens.
0
 
lapavoniAuthor Commented:
Thanks, acbrown.  That's a very good explanation.  That really seems to defeat the purpose of removing large chunks of mail from the user's main mailbox while preventing huge messages from accumulating again. Hmmm.
0
 
lapavoniAuthor Commented:
Excellent.  Not good news for me, but exact answer to the question I asked.
0
 
lapavoniAuthor Commented:
I'm wondering if I can run a script to change the max/send receive every night before maintenance is done, then change it back in the morning ... sneaky :-)
0
 
Adam BrownSr Solutions ArchitectCommented:
yeah.
set-mailboxdatabase <database name> -prohibitsendquota 30MB -prohibitsendreceivequota 30MB 

Open in new window


set as a scheduled task before the exchange maintenance is scheduled should work. Then another with 10MB instead of 30MB to run right after. You'll just have to make sure the exchange management snap-in gets added prior to that line.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.