Link to home
Start Free TrialLog in
Avatar of lapavoni
lapavoniFlag for United States of America

asked on

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
ASKER CERTIFIED SOLUTION
Avatar of Adam Brown
Adam Brown
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of lapavoni

ASKER

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.
Excellent.  Not good news for me, but exact answer to the question I asked.
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 :-)
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.