-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Dovecot gurus,

I have a couple of questions for which I haven't found answers in the docs (which may be well more a limitation of my capabilities than anything else). Here they go:

• Is it OK to move mailboxes around from under Dovecot?

Case in point: I'm using procmail to pass incoming mail through bogofilter (the standard recipe mentioned in their manpage, which more or less funnels spam into a "spam" mailbox, unsure into an "unsure" and non-spam into "inbox"). From time to time I'd like to clear the spam and unsure mailboxes, using logrotate. Dovecot seems to cope with it. Am I tempting my luck?

• Is there a way to tell an external application when mail has been moved by a client?

Again: dovecot+bogofilter: from time to time a client checks incoming, unsure and sometimes spam and decides to move --say-- a mail from unsure to spam (deciding it's spam, after all) or similar. This is of course important for the training of bogofilter, so I'd like to trigger a backend action. I see basically two possibilities:

• create two more mailboxes, say "spam-indeed" and "ham-indeed". User is told to move mail into these. Ham-indeed gets re-funneled to inbox (or something like that). Manual and error prone.

• Use the mail_log plugin (seems more attractive). I still have (distro-provided) dovecot 0.99.14, but this would be a good reason to upgrade. (I still don't see where I get the source mailbox in the mail_log messages from, but that's details now).

You get the idea, I think. Anyway, I am interested in any ways to combine dovecot and bogofilter in the backend in a way that I can route user feedback to the filter without putting too much burden on the user.

Ideas?

Thanks

• -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFGtuS4Bcgs9XrR2kYRAkiXAJoDJYZC8DYIxFqCw+HEIn0CCNssQwCfaZjh z533XFMH36c4Lemv/+gSn9A= =s87z -----END PGP SIGNATURE-----