Solved

Exchange 2010 Archive Database - Attachment Sizes

Posted on 2014-03-05
5
300 Views
Last Modified: 2014-03-05
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
0
Comment
Question by:lapavoni
  • 3
  • 2
5 Comments
 
LVL 39

Accepted Solution

by:
Adam Brown earned 500 total points
ID: 39908010
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
 

Author Comment

by:lapavoni
ID: 39908028
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
 

Author Closing Comment

by:lapavoni
ID: 39908029
Excellent.  Not good news for me, but exact answer to the question I asked.
0
 

Author Comment

by:lapavoni
ID: 39908032
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
 
LVL 39

Expert Comment

by:Adam Brown
ID: 39908196
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

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
how to add IIS SMTP to handle application/Scanner relays into office 365.

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question