Re: spam.el: automatically resplitting ham in a spam group?

[Josh Huber <huber+news@alum.wpi.edu>]

Kai Grossjohann <kai@emptydomain.de> writes:

> Yes.  I just tell spam.el to move spams to INBOX.makespam and hams
> to INBOX.makeham, and then the server-side config does the rest.

Sounds nice!

> Incoming mail is passed through Bogofilter before invoking
> cyrdeliver.  (I should be using LMTP but haven't figured that out,
> yet.)

I was thinking of using the exiscan extensions inside exim to tag
messages with a header, and then users could create a sieve rule to
filter based on that header.  I guess that's about the same as you're
doing.

> There are cron jobs which connect to the imap server using an
> administrative account (it's a Perl script using Mail::IMAPClient).
> The cron jobs train Bogofilter on user.jrl.makespam and
> user.jrl.makeham.  The spam is then deleted, and the ham moved back
> into the user's inbox.  (I have a separate database for each user.)

This sounds like a nice solution.  Based on the bogofilter score, do
you sometimes reject messages?  I was thinking it would be nice if
this were tied into the Exim data acl so I could reject messages early
on, but I guess that's not a requirement.

> I could show the script if you like, but it's really ugly.

Could you send it to me privately, just so I can get a good idea of
how this is done?  I promise I won't tell anyone how ugly it is :)

-- 
Josh Huber