in reply to Routing SPAM emails to a junk folder

Some tough design decisions here!

Just let me tell you how I did it: my spam-detector labels all "spam"-mail with "[SPAM]" in the subject line and adds a new X-header "SPAM". Users can then use their own mail readers to catalogue, delete, or do whatever ... with their mail.

Seems to work OK

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Replies are listed 'Best First'.
For server-side cleanup
by darkphorm (Beadle) on Jul 20, 2004 at 18:33 UTC
    That's fine for the clients - but the problem is more that SPAM is currently accouting for upwards to 25% of the used space in homedirs on the mailserver. Also, the clients can have to download hundreds of spammy messages in a day, bogging the internet connection and delaying the emails they want. Thus, I want to drop it into an IMAP spam folder (which can be accessed in the webmail) and segregate the spammy messages. If somebody is on vacation, their spam will be cleared after a week rather than building up.
      Just a wild thought: give every user two e-mail addresses: the real one is "user@my.email.server" and the one for the spam is "spam.user@my.email.server".

      If you make the spam-box only available through webmail, your users do not have to download through all the spam-messages and you can easily delete these message after a reasonable expiry-period.

      CountZero

      "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law