Timo Sirainen writes:> #expire = Trash 7 Spam 30Does the above mean one will be able to indicate multiple folders to expire? That is great! Any thoughts on having a per mailbox setting? For ISPs , one may want to give users the option to enable/disable the feature and perhaps give them a choice of dates.. ie Trash 7 days or 30 days. Spam 1 day or 7 days.
Timo Sirainen wrote:> # Expire plugin. Mails are expunged from mailboxes after being there the > # configurable time. The first expiration date for each mailbox is stored in > # a dictionary so it can be quickly determined which mailboxes contain > # expired mails. The actual expunging is done in a nightly cronjob, which > # you must set up: > # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool > #expire = Trash 7 Spam 30 > #expire_dict = db:/var/lib/dovecot/expire.dbFor users implementing the expire-tool as an email retention policy, it may be helpful to add path wildcarding and exclusion to handle users with folder heirarchies. e.g., To implement a 1-year retention policy on messages in all folders, excluding all messages in and in subfolders of 'Archived Email': expire = Trash 7 Spam 30 * 365 expire_exclude = Archived\ Email\\*
[repost] On Sun, 2006-10-08 at 11:27 -0400, Francisco Reyes wrote:> Timo Sirainen writes: > > > #expire = Trash 7 Spam 30 > > Does the above mean one will be able to indicate multiple folders to expire?Yep.> That is great! > Any thoughts on having a per mailbox setting?I guess you mean per user? Pretty much all imap/pop3/plugin settings in Dovecot can be user-specific if only they're returned properly from userdb. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20061013/fe4f5514/attachment.bin>