[Mailman-Users] Tieing Mailman to Spamassassin

Rob Brandt bronto at csd-bes.net
Thu Mar 4 19:24:56 CET 2004

I've continued working on this and made changes as I thought carefully about
what is actually going on here.

Assuming that the email is being routed to mailman before the maildrop filter is
processed, I had the idea of piping the email to mailman *throuogh* the
maildrop filter, instead of with the alias.  That way, the maildrop filter can
pass it to spamassassin first using xfilter, then pipe it to mailman.

It doesn't work.  When I send a message to the list, postfix bounces it back
with the following message:

"<re-techtalk at re-techtalk.com>: Command died with status 2:
    "/usr/local/bin/maildrop". Command output: Failed to create default user
    preference file /var/spool/postfix/virtual/.spamassassin/user_prefs Group
    mismatch error.  Mailman expected the mail wrapper script to be executed as
    group "mailman", but the system's mail server executed the mail script as
    group "csdbes".  Try tweaking the mail server to run the script as group
    "mailman", or re-run configure,  providing the command line option

I understand what it's saying here, but I don't understand why.  I recognize
it's saying that the mailman process must be as the mailman group, but I don't
see why the pipe works from postfix alias (the non-virtual kind) but not piping
from maildrop.  Is there an argument to use that will set
"run as group mailman" for piping the message to mailman?


Quoting Rob Brandt <bronto at csd-bes.net>:

> I have a new mailing list that will likely attract spammers.  I need to tie
> this
> in to my spamassassin installation and am not quite sure how to go about
> doing
> it.  Here's my situation:
> My mail server configuration is postfix-courier-imap with mysql
> authentication.
> I use virtual domains in postfix, and to enable spam filtering I have
> maildrop
> installed and use a maildrop filter to pass email to spamassassin for
> analysis.
>  This allows me to do spam control on a per-domain basis.  If I want spam
> control on a particular domain, I set the postfix transport to "maildrop"; if
> not I set it to "local".  It works well, but have never used it for mailing
> lists.
> I was hoping that I would be able to use the same method with this new
> mailman
> list.  The domain is in fact dedicated to the mailing list, and no other
> email
> will be routed through it.  To try it, I assigned the transport for that
> domain
> to "maildrop" and created mail filter files for each of the mailman aliases.
> In the filter file for the actual mailing list, I put in the command to pass
> the mail through to spamassassin.  It doesn't seem to work.  The email gets
> processed through the list as if it hadn't been processed through
> spamassassin.
>  I'm guess that this is exactly the case; that since the mailman aliases are
> not real email accounts, the mailfilter files aren't even being looked at.
> Am I wrong?  Or is there a better way to do this?
> Thanks
> Rob
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users at python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

More information about the Mailman-Users mailing list