On Sunday, December 15, 2002, at 09:43 PM, G. Wayne Kidd wrote:
1) Give the user or the spam-reviewer a mechanism for adding the sender to the whitelist.Probably a web based configuration file editor is a good idea. I posted a meager PHP-based
editor to the list a couple days ago.
2) If the mail is not originally seen by the user, give the reviewer (also not a linux user) automated mechanism for removing the SPAM tags from the mail and forwardingSimply removing the subject rewrite and the body rewrite in the SA configuration will leave only a report in the message headers, which users probably won't notice.
the mail to the intended user.
3). Give the user a mechanism to get mail that slipped past SA into the blacklist.Deliver spam mail to an IMAP folder in the user's home directory, then set up a Web Mail interface.
Perhaps Mark Cushman's AeroMail (http://the.cushman.net/projects/aeromail/) for a quick and dirty
solution.
Could we concievably do this by forwarding the mail to some pseudo-user that accomplishes the goals set out above.You've got authentication problems there. A user could conceivably edit another user's blacklist/whitelist using this mechanism.
Patrick
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
