RE: Spamassassin Letting a Lot of Spams Through - SpamAssassin

This is a discussion on RE: Spamassassin Letting a Lot of Spams Through - SpamAssassin ; Hi /usr/share/spamassassin - contains version release time rules, always used unless next dir exists. /var/lib/spamassassin/ / - contains 'sa-update'ed rules to bring release time rules upto date without needing a full version release /etc/mail/spamassassin - contains site wide rules and ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: RE: Spamassassin Letting a Lot of Spams Through

  1. RE: Spamassassin Letting a Lot of Spams Through

    Hi

    /usr/share/spamassassin - contains version release time rules, always used unless next dir exists.

    /var/lib/spamassassin// - contains 'sa-update'ed rules to bring release time rules upto date without needing a full version release

    /etc/mail/spamassassin - contains site wide rules and settings.

    ~/.spamassassin contains user specific rules.

    So copying rules from /usr/share/spamassassin to ~/.spamassassin will achieve nothing.

    Get the idea now?
    --
    martin

    -----Original Message-----
    From: aladdin
    Sent: Sunday, September 14, 2008 3:13 PM
    To: users@spamassassin.apache.org
    Subject: Re: Spamassassin Letting a Lot of Spams Through

    On Sunday 14 September 2008 10:06, aladdin wrote:
    > On Sunday 14 September 2008 05:07, you wrote:
    > > On Sun, 2008-09-14 at 01:05 -0400, aladdin wrote:
    > > > > So, evidently, it can't find my bayes database. So, since I want to
    > > > > use a system-wide database, where is it (/usr/share/spamassassin?,
    > > > > which has a lot of likely looking files in it), and how do I tell
    > > > > spamd to use it?

    > >
    > > By default it is in the .spamassassin directory of the user SA runs in.
    > >
    > > Using /usr/share/spamassin sounds like a bad idea to me: you're
    > > attempting to mix site-specific data with system files.
    > >
    > >
    > > Martin

    >
    > Hmmm! Oddly enough, that's where apt (the Debian package manager) put
    > them. So, I guess that leads to two more areas of questions:
    >
    > 1. Is there no precedent for stopping spam using system-wide files? I am
    > almost the sole user of this machine and would like to do this, if it's
    > possibe. Why would apt put them there otherwise?
    >
    > 2. If question one leads to user-specific files & directories, do I just
    > take the contents of /usr/share/spamassassin and copy it into
    > ~/.spamassassin? The contents of /usr/share/spamassassin are:
    > ################################################## #########
    > total 676
    > drwxr-xr-x 2 root root 4096 2008-09-07 19:24 ./
    > drwxr-xr-x 256 root root 12288 2008-09-07 19:24 ../
    > -rw-r--r-- 1 root root 5681 2007-02-15 00:28 10_misc.cf




    > -rw-r--r-- 1 root root 18944 2007-02-15 00:28 triplets.txt
    > -rw-r--r-- 1 root root 1843 2007-02-15 00:28 user_prefs.template
    > ################################################## ##################
    > Are these the files to be copied to ~/.spamassassin?


    As it turns out, I do have a ~/.spamassassin directory. It's current contents
    are:
    ################################################## ###############
    -rw------- 1 anw anw 1306624 2008-09-14 03:38 auto-whitelist
    -rw------- 1 anw anw 88190 2008-07-28 16:52 bayes_journal
    -rw------- 1 anw anw 684032 2008-07-28 16:52 bayes_seen
    -rw------- 1 anw anw 5283840 2008-07-28 16:52 bayes_toks
    -rw-r--r-- 1 anw anw 1487 2008-07-28 16:52 user_prefs
    ################################################## ###############

    Should I just copy the above into it and change the owner/group, and that's
    how spamassassin is supposed to work?

    --
    Thanks and regards,
    anw

    ************************************************** ********************
    Confidentiality : This e-mail and any attachments are intended for the
    addressee only and may be confidential. If they come to you in error
    you must take no action based on them, nor must you copy or show them
    to anyone. Please advise the sender by replying to this e-mail
    immediately and then delete the original from your computer.
    Opinion : Any opinions expressed in this e-mail are entirely those of
    the author and unless specifically stated to the contrary, are not
    necessarily those of the author's employer.
    Security Warning : Internet e-mail is not necessarily a secure
    communications medium and can be subject to data corruption. We advise
    that you consider this fact when e-mailing us.
    Viruses : We have taken steps to ensure that this e-mail and any
    attachments are free from known viruses but in keeping with good
    computing practice, you should ensure that they are virus free.

    Red Lion 49 Ltd T/A Solid State Logic
    Registered as a limited company in England and Wales
    (Company No:5362730)
    Registered Office: 25 Spring Hill Road, Begbroke, Oxford OX5 1RU,
    United Kingdom
    ************************************************** ********************


  2. Re: Spamassassin Letting a Lot of Spams Through

    Thanks, Martin, for the reply.

    Well, I guess I get the idea; what that doesn't explain now is why my spam
    scores (on what one would think is really obvious spam) are so low and why
    the log says it can't find the bayes database.

    On Sunday 14 September 2008 12:01, Martin.Hepworth wrote:
    > Hi
    >
    > /usr/share/spamassassin - contains version release time rules, always
    > used unless next dir exists.
    >
    > /var/lib/spamassassin// - contains 'sa-update'ed rules to bring
    > release time rules upto date without needing a full version release
    >
    > /etc/mail/spamassassin - contains site wide rules and settings.
    >
    > ~/.spamassassin contains user specific rules.
    >
    > So copying rules from /usr/share/spamassassin to ~/.spamassassin will
    > achieve nothing.
    >
    > Get the idea now?
    > --
    > martin
    >
    > -----Original Message-----
    > From: aladdin
    > Sent: Sunday, September 14, 2008 3:13 PM
    > To: users@spamassassin.apache.org
    > Subject: Re: Spamassassin Letting a Lot of Spams Through
    >
    > On Sunday 14 September 2008 10:06, aladdin wrote:
    > > On Sunday 14 September 2008 05:07, you wrote:
    > > > On Sun, 2008-09-14 at 01:05 -0400, aladdin wrote:
    > > > > > So, evidently, it can't find my bayes database. So, since I want
    > > > > > to use a system-wide database, where is it
    > > > > > (/usr/share/spamassassin?, which has a lot of likely looking files
    > > > > > in it), and how do I tell spamd to use it?
    > > >
    > > > By default it is in the .spamassassin directory of the user SA runs in.
    > > >
    > > > Using /usr/share/spamassin sounds like a bad idea to me: you're
    > > > attempting to mix site-specific data with system files.
    > > >
    > > >
    > > > Martin

    > >
    > > Hmmm! Oddly enough, that's where apt (the Debian package manager) put
    > > them. So, I guess that leads to two more areas of questions:
    > >
    > > 1. Is there no precedent for stopping spam using system-wide files? I am
    > > almost the sole user of this machine and would like to do this, if it's
    > > possibe. Why would apt put them there otherwise?
    > >
    > > 2. If question one leads to user-specific files & directories, do I just
    > > take the contents of /usr/share/spamassassin and copy it into
    > > ~/.spamassassin? The contents of /usr/share/spamassassin are:
    > > ################################################## #########
    > > total 676
    > > drwxr-xr-x 2 root root 4096 2008-09-07 19:24 ./
    > > drwxr-xr-x 256 root root 12288 2008-09-07 19:24 ../
    > > -rw-r--r-- 1 root root 5681 2007-02-15 00:28 10_misc.cf

    >
    >
    >
    > > -rw-r--r-- 1 root root 18944 2007-02-15 00:28 triplets.txt
    > > -rw-r--r-- 1 root root 1843 2007-02-15 00:28 user_prefs.template
    > > ################################################## ##################
    > > Are these the files to be copied to ~/.spamassassin?

    >
    > As it turns out, I do have a ~/.spamassassin directory. It's current
    > contents are:
    > ################################################## ###############
    > -rw------- 1 anw anw 1306624 2008-09-14 03:38 auto-whitelist
    > -rw------- 1 anw anw 88190 2008-07-28 16:52 bayes_journal
    > -rw------- 1 anw anw 684032 2008-07-28 16:52 bayes_seen
    > -rw------- 1 anw anw 5283840 2008-07-28 16:52 bayes_toks
    > -rw-r--r-- 1 anw anw 1487 2008-07-28 16:52 user_prefs
    > ################################################## ###############
    >
    > Should I just copy the above into it and change the owner/group, and that's
    > how spamassassin is supposed to work?


    --
    Thanks and regards,

    Allen Williams
    Office: +1.321.309.7931
    Mobile: +1.321.258.1272


  3. Re: Spamassassin Letting a Lot of Spams Through

    Aladdin:

    2008/9/14 aladdin :
    > Thanks, Martin, for the reply.
    >
    > Well, I guess I get the idea; what that doesn't explain now is why my spam
    > scores (on what one would think is really obvious spam) are so low and why
    > the log says it can't find the bayes database.


    Sounds like you should start by using the backports repo to get a
    newer version of SA. Then, you should check the permissions on the
    bayes_* files (trust me, you SHOULD consider putting the Bayes and AWL
    system in a SQL database, it's easier to mantain and faster). And
    then, you should start using sa-update to get the lastest set of
    rules.

    >
    > On Sunday 14 September 2008 12:01, Martin.Hepworth wrote:
    >> Hi
    >>
    >> /usr/share/spamassassin - contains version release time rules, always
    >> used unless next dir exists.
    >>
    >> /var/lib/spamassassin// - contains 'sa-update'ed rules to bring
    >> release time rules upto date without needing a full version release
    >>
    >> /etc/mail/spamassassin - contains site wide rules and settings.
    >>
    >> ~/.spamassassin contains user specific rules.
    >>
    >> So copying rules from /usr/share/spamassassin to ~/.spamassassin will
    >> achieve nothing.
    >>
    >> Get the idea now?
    >> --
    >> martin
    >>
    >> -----Original Message-----
    >> From: aladdin
    >> Sent: Sunday, September 14, 2008 3:13 PM
    >> To: users@spamassassin.apache.org
    >> Subject: Re: Spamassassin Letting a Lot of Spams Through
    >>
    >> On Sunday 14 September 2008 10:06, aladdin wrote:
    >> > On Sunday 14 September 2008 05:07, you wrote:
    >> > > On Sun, 2008-09-14 at 01:05 -0400, aladdin wrote:
    >> > > > > So, evidently, it can't find my bayes database. So, since I want
    >> > > > > to use a system-wide database, where is it
    >> > > > > (/usr/share/spamassassin?, which has a lot of likely looking files
    >> > > > > in it), and how do I tell spamd to use it?
    >> > >
    >> > > By default it is in the .spamassassin directory of the user SA runs in.
    >> > >
    >> > > Using /usr/share/spamassin sounds like a bad idea to me: you're
    >> > > attempting to mix site-specific data with system files.
    >> > >
    >> > >
    >> > > Martin
    >> >
    >> > Hmmm! Oddly enough, that's where apt (the Debian package manager) put
    >> > them. So, I guess that leads to two more areas of questions:
    >> >
    >> > 1. Is there no precedent for stopping spam using system-wide files? I am
    >> > almost the sole user of this machine and would like to do this, if it's
    >> > possibe. Why would apt put them there otherwise?
    >> >
    >> > 2. If question one leads to user-specific files & directories, do I just
    >> > take the contents of /usr/share/spamassassin and copy it into
    >> > ~/.spamassassin? The contents of /usr/share/spamassassin are:
    >> > ################################################## #########
    >> > total 676
    >> > drwxr-xr-x 2 root root 4096 2008-09-07 19:24 ./
    >> > drwxr-xr-x 256 root root 12288 2008-09-07 19:24 ../
    >> > -rw-r--r-- 1 root root 5681 2007-02-15 00:28 10_misc.cf

    >>
    >>
    >>
    >> > -rw-r--r-- 1 root root 18944 2007-02-15 00:28 triplets.txt
    >> > -rw-r--r-- 1 root root 1843 2007-02-15 00:28 user_prefs.template
    >> > ################################################## ##################
    >> > Are these the files to be copied to ~/.spamassassin?

    >>
    >> As it turns out, I do have a ~/.spamassassin directory. It's current
    >> contents are:
    >> ################################################## ###############
    >> -rw------- 1 anw anw 1306624 2008-09-14 03:38 auto-whitelist
    >> -rw------- 1 anw anw 88190 2008-07-28 16:52 bayes_journal
    >> -rw------- 1 anw anw 684032 2008-07-28 16:52 bayes_seen
    >> -rw------- 1 anw anw 5283840 2008-07-28 16:52 bayes_toks
    >> -rw-r--r-- 1 anw anw 1487 2008-07-28 16:52 user_prefs
    >> ################################################## ###############
    >>
    >> Should I just copy the above into it and change the owner/group, and that's
    >> how spamassassin is supposed to work?

    >
    > --
    > Thanks and regards,
    >
    > Allen Williams
    > Office: +1.321.309.7931
    > Mobile: +1.321.258.1272
    >


    Regards,


    Luis
    --
    _____________________________________

    GNU/GPL: "May The Source Be With You...

    Linux Registered User #448382.
    _____________________________________


  4. Re: Spamassassin Letting a Lot of Spams Through

    On 14/09/2008 1:56 PM, Luis Hernán Otegui wrote:
    > Aladdin:
    >
    > 2008/9/14 aladdin :
    >> Thanks, Martin, for the reply.
    >>
    >> Well, I guess I get the idea; what that doesn't explain now is why my spam
    >> scores (on what one would think is really obvious spam) are so low and why
    >> the log says it can't find the bayes database.

    >
    > Sounds like you should start by using the backports repo to get a
    > newer version of SA. Then, you should check the permissions on the
    > bayes_* files (trust me, you SHOULD consider putting the Bayes and AWL
    > system in a SQL database, it's easier to mantain and faster). And
    > then, you should start using sa-update to get the lastest set of
    > rules.


    Yes, if you wish to use system wide bayes you should refer to the
    following in the Mail::SpamAssassin::Conf POD:

    > bayes_path /path/filename (default: ~/.spamassassin/bayes)
    > This is the directory and filename for Bayes databases. Several databases will be created, with this
    > as the base directory and filename, with "_toks", "_seen", etc. appended to the base. The default
    > setting results in files called "~/.spamassassin/bayes_seen", "~/.spamassassin/bayes_toks", etc.
    >
    > By default, each user has their own in their "~/.spamassassin" directory with mode 0700/0600. For
    > system-wide SpamAssassin use, you may want to reduce disk space usage by sharing this across all
    > users. However, Bayes appears to be more effective with individual user databases.
    >
    > bayes_file_mode (default: 0700)
    > The file mode bits used for the Bayesian filtering database files.
    >
    > Make sure you specify this using the 'x' mode bits set, as it may also be used to create directories.
    > However, if a file is created, the resulting file will not have any execute bits set (the umask is set
    > to 111).


    That is, you need to set the path and a proper file mode for system wide
    access. Also make sure the file system rights are appropriate for
    system wide access by all users too.

    Additionally, SQL is the recommended storage method for bayes.

    Daryl


  5. Re: Spamassassin Letting a Lot of Spams Through

    I'll admit I'm struggling a bit. Lo, those many hours ago when I started this
    I admitted to being a newbie here. I'm not adverse to putting everything in
    mysql, and I've seen the docs on how to do it; I'd just like to get a
    successful vanilla install first. As I said earlier, I'm (almost) the only
    user of this machine, and I'm really trying to test spamassassin here before
    I try to put it on a production mail server.

    After I followed someone's advice and uncommented the flock statement in
    local.cf, I am now getting this in the mail.warn log file:

    Sep 14 15:54:44 anw-dev spamd[21774]: bayes: locker: safe_lock: cannot create
    lockfile /etc/spamassassin/bayes.mutex: Permission denied

    This seems odd, since the contents/perms of /etc/spamassassin are:

    drwxr-xr-x 2 root root 4096 2008-09-14 15:44 ./
    drwxr-xr-x 125 root root 12288 2008-09-13 17:09 ../
    -rw-rw-r-- 1 root root 0 2008-09-14 15:44 bayes.mutex
    -rw-rw-r-- 1 root root 948 2007-02-15 00:28 init.pre
    -rw-rw-r-- 1 root root 1232 2008-09-14 13:32 local.cf
    -rw-rw-r-- 1 root root 1200 2008-09-12 12:29 local.cf~
    -rw-rw-r-- 1 root root 2178 2008-09-13 20:29 v310.pre
    -rw-rw-r-- 1 root root 2179 2007-02-15 00:28 v310.pre~
    -rw-rw-r-- 1 root root 806 2007-02-15 00:28 v312.pre

    and spamd runs as root (I know this is probably not the best idea, but, like I
    say, I'm just trying to get it to work). When I first saw this message, I
    did a "touch bayes.mutex" to get it there in the first place, but didn't
    really think that would make a difference; it didn't. I mean, I'm not sucha
    newbie that I don't understand Linux permissions (famous last words, of
    course;-), so I really don't understand this.

    Here is my latest local.cf, and it doesn't seem to me following the
    bayes_path. My bayes_toks & bayes_seen type files are still in
    ~/.spamassassin and not showing up anywhere else (but I'm sure that is some
    misunderstanding on my part, unless I really do have a permissions problem
    in /etc/spamassassin):

    ######## local.cf ##########################
    rewrite_header Subject *****SPAM*****
    lock_method flock
    required_score 5.0
    use_bayes 1
    bayes_auto_learn 1
    bayes_path /etc/spamassassin/bayes
    ########## end local.cf ######################

    and then, following someone else's advice and trying to do an sa-update, I got
    this:

    anw-dev:/var/log# sa-update
    Can't locate Net/DNS.pm in @INC (@INC
    contains: /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl)
    at /usr/bin/sa-update line 91.
    BEGIN failed--compilation aborted at /usr/bin/sa-update line 91.

    Just adding insult to injury, I guess.

    On Sunday 14 September 2008 14:00, Daryl C. W. O'Shea wrote:
    > On 14/09/2008 1:56 PM, Luis Hernán Otegui wrote:
    > > Aladdin:# This is the right place to customize your installation of

    SpamAssassin.
    > >
    > > 2008/9/14 aladdin :
    > >> Thanks, Martin, for the reply.
    > >>
    > >> Well, I guess I get the idea; what that doesn't explain now is why my
    > >> spam scores (on what one would think is really obvious spam) are so low
    > >> and why the log says it can't find the bayes database.

    > >
    > > Sounds like you should start by using the backports repo to get a
    > > newer version of SA. Then, you should check the permissions on the
    > > bayes_* files (trust me, you SHOULD consider putting the Bayes and AWL
    > > system in a SQL database, it's easier to mantain and faster). And
    > > then, you should start using sa-update to get the lastest set of
    > > rules.

    >
    > Yes, if you wish to use system wide bayes you should refer to the
    >
    > following in the Mail::SpamAssassin::Conf POD:
    > > bayes_path /path/filename (default: ~/.spamassassin/bayes)
    > > This is the directory and filename for Bayes databases.
    > > Several databases will be created, with this as the base directory and
    > > filename, with "_toks", "_seen", etc. appended to the base. The default
    > > setting results in files called "~/.spamassassin/bayes_seen",
    > > "~/.spamassassin/bayes_toks", etc.
    > >
    > > By default, each user has their own in their "~/.spamassassin"
    > > directory with mode 0700/0600. For system-wide SpamAssassin use, you may
    > > want to reduce disk space usage by sharing this across all users.
    > > However, Bayes appears to be more effective with individual user
    > > databases.
    > >
    > > bayes_file_mode (default: 0700)
    > > The file mode bits used for the Bayesian filtering database
    > > files.
    > >
    > > Make sure you specify this using the 'x' mode bits set, as it
    > > may also be used to create directories. However, if a file is created,
    > > the resulting file will not have any execute bits set (the umask is set
    > > to 111).

    >
    > That is, you need to set the path and a proper file mode for system wide
    > access. Also make sure the file system rights are appropriate for
    > system wide access by all users too.
    >
    > Additionally, SQL is the recommended storage method for bayes.
    >
    > Daryl


    --
    Thanks and regards,

    Allen Williams
    Office: +1.321.309.7931
    Mobile: +1.321.258.1272


  6. Re: Spamassassin Letting a Lot of Spams Through

    On 14/09/2008 4:47 PM, aladdin wrote:
    > and spamd runs as root (I know this is probably not the best idea, but, like I
    > say, I'm just trying to get it to work).


    The spamd child process will drop privs to whatever user it is scanning
    mail for, or nobody if scanning mail for root. Thus requiring root
    privs to write to your bayes files is not going to work.

    Place the bayes files in a directory that you can "safely" give rw
    rights to all users that you're scanning mail for. This isn't going to
    be /etc/spamassassin (it could be a subdir of that though, if you want).

    Also make sure you set the bayes_file_mode to 770 or 777 (depending on
    how you configure rights for your bayes files).

    > and then, following someone else's advice and trying to do an sa-update, I got
    > this:
    >
    > anw-dev:/var/log# sa-update
    > Can't locate Net/DNS.pm in @INC (@INC
    > contains: /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl)
    > at /usr/bin/sa-update line 91.
    > BEGIN failed--compilation aborted at /usr/bin/sa-update line 91.


    That there is your biggest issue. You don't have Net:NS installed (or
    at least Perl can't locate it) so SpamAssassin cannot do network tests.
    Install Net:NS. Perhaps you should review the INSTALL file to make
    sure there's nothing else you're missing that you should install.

    Daryl


  7. Re: Spamassassin Letting a Lot of Spams Through

    OK, thanks so much, Daryl!

    I have now set up /home/spamassassin, with the directory and all files chmod'd
    777 and bayes_file_mode set to 777, and installed, on my Debian system the
    libnet-dns-perl package that should give me the Net:NS stuff; lo and
    behold, sa-update ran with no errors, so I'm on a roll here! Now to let it
    run for a while and see what happens.

    One (hopefully;-) last question: what are all the files
    in /usr/share/spamassassin, and can I leave them there, or do I need to move
    them to my new /home/spamassassin directory? I posted them earlier, but
    since they've been snipped from here, I'll repeat part of them; they are, for
    example:

    -rw-r--r-- 1 root root 5681 2007-02-15 00:28 10_misc.cf
    -rw-r--r-- 1 root root 8327 2007-02-15 00:28 20_advance_fee.cf
    -rw-r--r-- 1 root root 1791 2007-02-15 00:28 20_anti_ratware.cf
    -rw-r--r-- 1 root root 7077 2007-02-15 00:28 20_body_tests.cf
    -rw-r--r-- 1 root root 1749 2007-02-15 00:28 20_compensate.cf
    -rw-r--r-- 1 root root 14505 2007-02-15 00:28 20_dnsbl_tests.cf
    -rw-r--r-- 1 root root 15854 2007-02-15 00:28 20_drugs.cf
    -rw-r--r-- 1 root root 11672 2007-02-15 00:28 20_fake_helo_tests.cf
    -rw-r--r-- 1 root root 33045 2007-02-15 00:28 20_head_tests.cf
    -rw-r--r-- 1 root root 17485 2007-02-15 00:28 20_html_tests.cf
    -rw-r--r-- 1 root root 3532 2007-02-15 00:28 20_meta_tests.cf
    -rw-r--r-- 1 root root 2350 2007-02-15 00:28 20_net_tests.cf
    -rw-r--r-- 1 root root 16172 2007-02-15 00:28 20_phrases.cf
    -rw-r--r-- 1 root root 5003 2007-02-15 00:28 20_porn.cf
    -rw-r--r-- 1 root root 17065 2007-02-15 00:28 20_ratware.cf
    -rw-r--r-- 1 root root 9901 2007-02-15 00:28 20_uri_tests.cf
    -rw-r--r-- 1 root root 2520 2007-02-15 00:28 23_bayes.cf
    -rw-r--r-- 1 root root 420 2007-02-15 00:28 25_accessdb.cf
    -rw-r--r-- 1 root root 1534 2007-02-15 00:28 25_antivirus.cf
    -rw-r--r-- 1 root root 9306 2007-02-15 00:28 25_body_tests_es.cf
    -rw-r--r-- 1 root root 17865 2007-02-15 00:28 25_body_tests_pl.cf
    -rw-r--r-- 1 root root 190 2007-02-15 00:28 25_dcc.cf
    -rw-r--r-- 1 root root 2182 2007-02-15 00:28 25_dkim.cf
    -rw-r--r-- 1 root root 2136 2007-02-15 00:28 25_domainkeys.cf
    -rw-r--r-- 1 root root 2927 2007-02-15 00:28 25_hashcash.cf
    -rw-r--r-- 1 root root 189 2007-02-15 00:28 25_pyzor.cf
    -rw-r--r-- 1 root root 2201 2007-02-15 00:28 25_razor2.cf


    Do I need to do anything special (put something like a path or anything) in a
    config file to activate them?

    On Sunday 14 September 2008 17:02, Daryl C. W. O'Shea wrote:
    > On 14/09/2008 4:47 PM, aladdin wrote:
    > > and spamd runs as root (I know this is probably not the best idea, but,
    > > like I say, I'm just trying to get it to work).

    >
    > The spamd child process will drop privs to whatever user it is scanning
    > mail for, or nobody if scanning mail for root. Thus requiring root
    > privs to write to your bayes files is not going to work.
    >
    > Place the bayes files in a directory that you can "safely" give rw
    > rights to all users that you're scanning mail for. This isn't going to
    > be /etc/spamassassin (it could be a subdir of that though, if you want).
    >
    > Also make sure you set the bayes_file_mode to 770 or 777 (depending on
    > how you configure rights for your bayes files).
    >
    > > and then, following someone else's advice and trying to do an sa-update,
    > > I got this:
    > >
    > > anw-dev:/var/log# sa-update
    > > Can't locate Net/DNS.pm in @INC (@INC
    > > contains: /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.8
    > > /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/lib/perl/5.8
    > > /usr/share/perl/5.8 /usr/local/lib/site_perl) at /usr/bin/sa-update line
    > > 91.
    > > BEGIN failed--compilation aborted at /usr/bin/sa-update line 91.

    >
    > That there is your biggest issue. You don't have Net:NS installed (or
    > at least Perl can't locate it) so SpamAssassin cannot do network tests.
    > Install Net:NS. Perhaps you should review the INSTALL file to make
    > sure there's nothing else you're missing that you should install.
    >
    > Daryl


    --
    Thanks and regards,

    Allen Williams
    Office: +1.321.309.7931
    Mobile: +1.321.258.1272


  8. Re: Spamassassin Letting a Lot of Spams Through

    On 14/09/2008 5:41 PM, aladdin wrote:
    > One (hopefully;-) last question: what are all the files
    > in /usr/share/spamassassin, and can I leave them there, or do I need to move
    > them to my new /home/spamassassin directory?


    Do not move them, do not delete them. They are the default rules that
    come with SpamAssassin. SpamAssassin expects to find them there.

    Daryl


+ Reply to Thread