[Mailman-Users] mm2.0.X to 2.1.1 upgrade, spamassassin

[Jon Carnes]

SpamAssassin is integrated at the MTA level (or at the local delivery
level).  In any case there is no need, and in fact there should not be
any hooks for SpamAssassin built into Mailman.

You can pass any incoming mail through SpamAssassin before delivering it
to your internal network, or if you only have only one mail server then
you can front-end each list with a procmail script which passes the
incoming mail through Spam Assassin before passing it on to Mailman.

If you need help with that, look in the archives or drop a note back to
the list.

Jon Carnes

On Tue, 2003-02-25 at 12:52, Dave Stern - Former Rocket Scientist wrote:
> Regarding the problems I had where the tracedump was complaining of
> authentication/cookies, I was able to resolve the problem by unprotecting
> things some (chmod g+w  in $PREFIX/logs, $PREFIX/archives/private)
> and then re-running check_perms. Interesting that check_perms ran
> successfully previously....
> 
> Looking at the options now, I'm not sure I'll upgrade. I do like the
> privacy-->sender-filter option: Action to take for postings from non-members
>                                    for which no explicit action is defined.
> 
> (previously, I used a cron to wipe mail sent to lists held for moderator and
> add mailfilters for moderators to not see notifications of held messages.
> 
> But I'm disappointed that there aren't any obvious/simple hooks to have this
> play with spamassassin. Or has anyone else successfully done this?
> 
> 
>  =-=-=-=-=-=-=-=-=-=-=-=-  generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=-=-=
>  David Stern                                            University of Maryland
>                 Institute for Advanced Computer Studies