Trying to set up a policy that will archive e-mail older than 365 days on the server. It wasn’t obvious in the instructions what triggered the archive process. Finally realized it is the “-a” option for the “compact” command. This was set up in program document and scheduled to run Sat, Wed at 4:00 a.m. I also found I had to manually archive a couple of documents for the archive database to be created.<\/p>\n
Spent a lot of time on a policy document, but in the end, I don’t think that is being used at all because it is not being pushed into the client database. (Using a custom template.) So it is the client archive settings that enable the compact -a command to work on a given database.<\/p>\n
The “mail” in this line means only look into the mail directory. The -b means to<\/p>\n
Load compact mail -a -b<\/p><\/blockquote>\n
Link.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Trying to set up a policy that will archive e-mail older than 365 days on the server. It wasn’t obvious in the instructions what triggered the archive process. Finally realized it is the “-a” option for the “compact” command. This … Continue reading