FAQ
I have been attempting, unsuccessfully, to configure SpamAssassin to
work with my Mailman installation using the "Add
"Global_Pipeline.inster(1,'SpamAssassin')" method (from FAQ 4.23). I
am hoping that someone who has been successful at implementing this
will be able to help me out.

I have been working through the instrucitons available at http://
www.jamesh.id.au/articles/mailman-spamassassin/ and have been able to
create the user acount and directory, but when I attempt to pass the
arguments to spamd to get it to run in a locked down mode using the
instructions (spamd -d -u spamassassin -x -a -P --virtual-config-dir=/
var/lib/spamassassin/%u.prefs) I get the following:

warn: Unknown option: a
Usage:
spamd [options]

with a list of options that do not include an option "a" for crating
automatic whitelists. Not sure that's a big deal so I removed the -a
option and repeated the command, and that seemed to work OK.

i moved on to the next step (not using RPM's) which was:

chkconfig --level 345 spamassassin on

and I get the following:

error reading information on service spamassassin: No such file or
directory

Anybody have any ideas why this isn't working, or recommendations for
what else I can check?

Thanks,

J.R.

J.R. Constance
jrc at rodricon.com

Search Discussions

  • Stephen J. Turnbull at Oct 1, 2007 at 10:29 pm
    J.R. Constance writes:
    I have been working through the instrucitons available at http://
    www.jamesh.id.au/articles/mailman-spamassassin/
    I believe these instructions are pretty old, and SpamAssassin has
    evolved significantly since then.
    I get the following: >
    warn: Unknown option: a
    Usage:
    spamd [options]
    Confirmation of the "golden oldie" status of the instructions. You
    really should read the man page and other documentation for spamd,
    spamassassin, and spamc.
    i moved on to the next step (not using RPM's) which was: >
    chkconfig --level 345 spamassassin on
    AFAIK chkconfig is Red Hat/RPM-specific. If you didn't install
    SpamAssassin from RPMs, this isn't going to work.
    error reading information on service spamassassin: No such file or
    directory
    Consistent with the above guess.

    Note that it's not a certainty that anybody here is a SpamAssassin
    expert with experience on your platform. While eventually you need to
    work with Mailman, at this stage I strongly recommend you ask about
    installing and testing SpamAssassin on platform and SpamAssassin
    channels, too.
    Anybody have any ideas why this isn't working, or recommendations for
    what else I can check?
    First, a caution. If you're serious about "locked-down" mode (eg,
    having your lists spammed or your server turned into a spammer zombie
    could cost your job), maybe you should hire an expert. It's not
    something that can be achieved by following recipes you find on the
    web. If you're willing to accept something more-or-less secure and
    you're on a Red Hat system, then I would recommend installing both
    SpamAssassin and Mailman from RPMs, and going on from there.

    If/when you run into trouble, specify the vendor and version of your
    OS, the versions of the Mailman and SpamAssassin packages, and
    reproduce both commands and the informational and error messages that
    they produce verbatim.

    If you're not on Red Hat, we'll need the system details as above.
  • Brad Knowles at Oct 1, 2007 at 10:31 pm

    On 10/1/07, J.R. Constance wrote:

    I have been attempting, unsuccessfully, to configure SpamAssassin to
    work with my Mailman installation using the "Add
    "Global_Pipeline.inster(1,'SpamAssassin')" method (from FAQ 4.23). I
    am hoping that someone who has been successful at implementing this
    will be able to help me out.
    That's not really the recommended way to perform anti-spam filtering
    on your system. All anti-spam/anti-virus filtering really should be
    integrated into your MTA and done before you tell the other end "250
    Okay" at the end of the SMTP dialog.

    Otherwise you're accepting spam and taking the serious risk that
    you'll generate a backscatter bounce to a forged address.

    See FAQ 6.12 for one take on this type of solution. And don't ignore
    FAQ 4.64, either.

    --
    Brad Knowles <brad at shub-internet.org>
    LinkedIn Profile: <http://tinyurl.com/y8kpxu>

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedOct 1, '07 at 7:50p
activeOct 1, '07 at 10:31p
posts3
users3
websitelist.org

People

Translate

site design / logo © 2022 Grokbase