It was also be nice to make external calls like you can with
procmail (pipe in from dbmail, do something, pipe out to dbmail
again).
Piping things in and out for specific aliases (which can include
domain
aliases, btw) is already possible, although you might have to jump
through
some weird aliasing hoops.
This kind of goes back to the gotcha's and hoops reference about spam
filters in general.
Something I've been working on as a simplification of spam filtering
has been to turn the spam filter into a web service that you contact
via http/https. It's a bayesian spam filter with user-specific
information in it. But the point in it's operation is to take an
email in, post it, get a response that is your header (X-Spam...)
that the client puts on the message, and the client then puts the
message back into circulation. In my current case, it's a
content_filter for postfix but I suppose it could be accessed by any
means you can come up with (LMTP, unit socket, piping...). I've
tried to remove as many of the hoops by pushing a lot of the "setup"
into a web service that no one needs to really think about.
I'm not saying this is the spam filter to use -- but it's similar to
a number of other projects but maybe simpler.
Perhaps the interface would be something of a POST/RESPONSE where the
response can either give you a status or a specific header string
response.
I'm a little reluctant to say dbmail should do spam filtering -- but
is this something that would be practical to do?
(Not really sure if I'm going anywhere with this thread...)
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
