I think jgedeon's referring to main/ZimbraServer/src/java/com/zimbra/cs/mailbox/Mailbox.java:
Quote:
int globalTimeout = (int) (acct.getTimeInterval(Provisioning.A_zimbraMailMes sageLifetime, 0) / 1000);
// sanity-check the really dangerous value... if (globalTimeout > 0 && globalTimeout < Constants.SECONDS_PER_MONTH) {
// this min is also used by POP3 EXPIRE command. update Pop3Handler.MIN_EPXIRE_DAYS if it changes. ZimbraLog.purge.warn("global message timeout < 1 month; defaulting to 31 days"); globalTimeout = Constants.SECONDS_PER_MONTH;
}
|
Since zimbraMailMessageLifetime affects items in
any folder we hard-coded a minimum; just too many support tickets on 'all my mail is missing'...
(If your getting that much email every 7 days, are you just using it for status checks? If so it may be time to consider a monitoring/stats package instead.)
However you can still do things like:
-Cron a periodic zmmailbox emptyFolder command (which is recursive by default, and yes you can run it on Inbox from CLI/SOAP, we just prevent it on system folders in ZWC).
-Move to trash with a filter (if your not already sorting for other reasons).
Gnyce's correct, we currently purge by date received (not by how long it's been in trash) however you can change this in the upcoming 5.0.17 by setting zimbraMailPurgeUseChangeDateForTrash TRUE (
19702)
Mailbox Purge - Zimbra :: Wiki