Well, depending on your setup...
What we do is use an IMAP server, but the vast majority of our users are POP3. So, anybody who wants auto deletion or server side filtering gets some mojo applied to their account, so that tagged spam winds up in the IMAP trash folder. Everything in that folder gets deleted when it hits one week old.
Pros: They never see it if they don't want to, but it's easily accessable from webmail if they ever do want to see it. It doesn't pile up too much.
Cons: Some people get a *lot* of spam in a week. Still, spam tends to be relatively small.
May as well chip in with what we do, since everyone else has ;-) (Might help give people that are wondering what to do ideas as well...)
99% of our users use POP3 or webmail or both.
SA (spamc actually) runs globally through procmail, allowing us to provide fully independant preferences for each user.
The default settings unless otherwise changed by end users is SA is enabled, required_hits is 7, and SA only tags messages in the subject and headers as spam (report_safe 0 mode) but doesn't otherwise redirect or block messages.
The reasoning behind not enabling blocking of messages by default should be pretty clear to anyone who follows this list. By having scanning and subject tagging on by default it introduces people to the idea of spam filtering and gives them an idea of how accurate it is on THEIR mail without them losing any mail or having to do anything, initially.
A plugin in our Webmail app Squirrelmail gives each user access to their settings, including:
* SpamAssassin on/off (done at a procmail level - if its off, it really doesn't run SA for them at all)
* required_hits can be adjusted between 5 and 30 in a few specific steps (dropdown box)
* Quarantine Spam on/off - when on, anything flagged as spam goes to a "Spam" folder on the webmail. (Also accessible by IMAP, but they don't know that :)
* Messages in the Spam folder older than a certain number of days (default 15, adjustable from 2 to 30) are purged nightly by a cron job to prevent buildup of spam
* For adventurous types that get bucket loads of spam, there is an instant delete option (done at a procmail level) which will /dev/null messages above a second threshold - 15, 20, 25, 30, or disabled. Since the minimum for this is 15 they can't get into *too* much trouble ;-) This helps purge the really obvious spam immediately leaving only the less certain stuff for them to check in their Spam folder occasionally..
* Whitelist and blacklist boxes so users can add their own whitelists and blacklists....
We've been running like this for a couple of months now and so far feedback has been *very* positive. It gives just the right amount of control to end users, has sensible defaults, and is simple enough for those that just want to "turn it on" and not worry about some of the more advanced features. (All a neophyte has to do is enable the quarantine option)
Regards, Simon
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
