Marc G. Fournier
scrappy at hub.org
Mon Apr 25 16:03:02 EDT 2005
I don't know ... just scan'd through the patch, and am not quite sure how
it interacts with the various external spam checkers ...
For instance, spamcheck.py allows you to talk to a 'remote spamd' daemon,
which can run on a different machines (we run >200 VPSs, but they all
share one central spamd, and associated bayes databases) ... is what Igor
doing just meant to filter based on existing headers, as generated by
Spamassassin (or equiv), or will it actually process the mail message to
generate its own headers?
With spamcheck, the processing is down at the LMTP stage, before sieve,
but after postfix itself has decided who to deliver it to, so you are
assured of "per user filters", vs system wide ... if sieve is just looking
at existing headers (which I don't know if that *is* what it is doing),
then that doesn't remove the issue :(
procmail is considered the 'preferred' solution for doing per user, but,
IMHO, that is just one more thing to break down :(
On Mon, 25 Apr 2005, Derrick Brashear wrote:
> On Apr 25, 2005, at 3:20 PM, Marc G. Fournier wrote:
>> IMHO, the biggest thing missing from sieve is the ability to easily use
>> anti-spam software like Spamassassin ...
> Well, spamtest and virustest extensions are coming from Igor Brezac when he
> has time to finish them, if that will help.
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org Yahoo!: yscrappy ICQ: 7615664
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
More information about the Info-cyrus