Maybe even a site-wite compile-time directive? Probably the most common
would be something like SPAM under the INBOX for the filtered messages.
Having it in SQL would be nice (allow users to configure it if they call
the SPAM dir something else in their own hierarchy), although I'm not
familiar enough with the innards of the code to know if that would work
How about if a mailbox called SPAM exists, put it there, otherwise just drop it in the INBOX?
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet: sniffter.com