You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Bjorn Jensen <bj...@info-connect.dk> on 2006/08/03 18:15:38 UTC
sa-update problems
I just ran sa-update for the first time today, and now I'm getting this
when starting up spamd:
Aug 3 18:05:30 mail3 spamd[590]: config: cannot opendir
/var/lib/spamassassin/3.001003: Permission denied
Aug 3 18:05:30 mail3 spamd[590]: config: cannot opendir
/var/lib/spamassassin/3.001003: Permission denied
Aug 3 18:05:32 mail3 spamd[590]: spamd: server started on port 783/tcp
(running version 3.1.3)
Aug 3 18:05:32 mail3 spamd[590]: spamd: server pid: 590
Aug 3 18:05:32 mail3 spamd[590]: spamd: server successfully spawned
child process, pid 592
Aug 3 18:05:32 mail3 spamd[590]: spamd: server successfully spawned
child process, pid 593
This seems to mean that no local rules are loaded and most spam goes
right through.
The directory /var/lib/spamassassin/3.001003 exists and there's another
directory in there with the new rules, just like the wiki says about
sa-update, and if I run spamassassin -D --lint it shows no problems, and
I'm also able to scan emails through that just fine, just not spamd
spamd is running like so:
root 624 0.4 1.5 52032 46960 ? Ss 18:06 0:01
/usr/bin/spamd -d -c --min-children=5 -m15 -i xxx.xxx.xxx.xxx -H -A
xxx.xxx.xxx.xxx -r /var/run/spamd.pid
root 626 3.3 1.6 56760 52260 ? S 18:06 0:13 spamd child
root 627 0.3 1.5 53816 48924 ? S 18:06 0:01 spamd child
root 663 0.0 1.5 52596 47452 ? S 18:09 0:00 spamd child
root 679 0.0 1.4 52032 45788 ? S 18:12 0:00 spamd child
The directories:
[root@mail3 spamassassin]# ll /var/lib/spamassassin
total 8
drwxr-xr-x 3 root root 4096 Aug 3 17:53 3.001003
[root@mail3 spamassassin]# ll /var/lib/spamassassin/3.001003
total 16
drwxr-xr-x 2 root root 4096 Aug 3 17:53 updates_spamassassin_org
-rw-r--r-- 1 root root 2151 Aug 3 17:53 updates_spamassassin_org.cf
[root@mail3 spamassassin]# ll
/var/lib/spamassassin/3.001003/updates_spamassassin_org
total 720
-rw-r--r-- 1 root root 5479 Aug 3 17:53 10_misc.cf
-rw-r--r-- 1 root root 8112 Aug 3 17:53 20_advance_fee.cf
-rw-r--r-- 1 root root 1602 Aug 3 17:53 20_anti_ratware.cf
-rw-r--r-- 1 root root 6690 Aug 3 17:53 20_body_tests.cf
-rw-r--r-- 1 root root 1534 Aug 3 17:53 20_compensate.cf
-rw-r--r-- 1 root root 14287 Aug 3 17:53 20_dnsbl_tests.cf
-rw-r--r-- 1 root root 15636 Aug 3 17:53 20_drugs.cf
-rw-r--r-- 1 root root 11380 Aug 3 17:53 20_fake_helo_tests.cf
-rw-r--r-- 1 root root 33153 Aug 3 17:53 20_head_tests.cf
-rw-r--r-- 1 root root 17501 Aug 3 17:53 20_html_tests.cf
-rw-r--r-- 1 root root 3305 Aug 3 17:53 20_meta_tests.cf
-rw-r--r-- 1 root root 2135 Aug 3 17:53 20_net_tests.cf
-rw-r--r-- 1 root root 15880 Aug 3 17:53 20_phrases.cf
-rw-r--r-- 1 root root 4711 Aug 3 17:53 20_porn.cf
-rw-r--r-- 1 root root 17038 Aug 3 17:53 20_ratware.cf
-rw-r--r-- 1 root root 9690 Aug 3 17:53 20_uri_tests.cf
-rw-r--r-- 1 root root 2228 Aug 3 17:53 23_bayes.cf
-rw-r--r-- 1 root root 420 Aug 3 17:53 25_accessdb.cf
-rw-r--r-- 1 root root 1342 Aug 3 17:53 25_antivirus.cf
-rw-r--r-- 1 root root 9114 Aug 3 17:53 25_body_tests_es.cf
-rw-r--r-- 1 root root 17673 Aug 3 17:53 25_body_tests_pl.cf
-rw-r--r-- 1 root root 190 Aug 3 17:53 25_dcc.cf
-rw-r--r-- 1 root root 1990 Aug 3 17:53 25_dkim.cf
-rw-r--r-- 1 root root 1944 Aug 3 17:53 25_domainkeys.cf
-rw-r--r-- 1 root root 2735 Aug 3 17:53 25_hashcash.cf
-rw-r--r-- 1 root root 189 Aug 3 17:53 25_pyzor.cf
-rw-r--r-- 1 root root 2201 Aug 3 17:53 25_razor2.cf
-rw-r--r-- 1 root root 8339 Aug 3 17:53 25_replace.cf
-rw-r--r-- 1 root root 2870 Aug 3 17:53 25_spf.cf
-rw-r--r-- 1 root root 352 Aug 3 17:53 25_textcat.cf
-rw-r--r-- 1 root root 7536 Aug 3 17:53 25_uribl.cf
-rw-r--r-- 1 root root 47385 Aug 3 17:53 30_text_de.cf
-rw-r--r-- 1 root root 34883 Aug 3 17:53 30_text_fr.cf
-rw-r--r-- 1 root root 1667 Aug 3 17:53 30_text_it.cf
-rw-r--r-- 1 root root 38211 Aug 3 17:53 30_text_nl.cf
-rw-r--r-- 1 root root 30281 Aug 3 17:53 30_text_pl.cf
-rw-r--r-- 1 root root 2883 Aug 3 17:53 30_text_pt_br.cf
-rw-r--r-- 1 root root 33700 Aug 3 17:53 50_scores.cf
-rw-r--r-- 1 root root 1113 Aug 3 17:53 60_awl.cf
-rw-r--r-- 1 root root 4903 Aug 3 17:53 60_whitelist.cf
-rw-r--r-- 1 root root 2367 Aug 3 17:53 60_whitelist_dkim.cf
-rw-r--r-- 1 root root 3480 Aug 3 17:53 60_whitelist_spf.cf
-rw-r--r-- 1 root root 1723 Aug 3 17:53 60_whitelist_subject.cf
-rw-r--r-- 1 root root 12968 Aug 3 17:53 80_additional.cf
-rw-r--r-- 1 root root 0 Aug 3 17:53 empty.pre
-rw-r--r-- 1 root root 36 Aug 3 17:53 MIRRORED.BY
[root@mail3 spamassassin]#
Regards,
Bjorn Jensen
Re: sa-update problems
Posted by Bjorn Jensen <bj...@info-connect.dk>.
Theo Van Dinter wrote:
> On Thu, Aug 03, 2006 at 06:15:38PM +0200, Bjorn Jensen wrote:
>
>> Aug 3 18:05:30 mail3 spamd[590]: config: cannot opendir
>> /var/lib/spamassassin/3.001003: Permission denied
>> Aug 3 18:05:30 mail3 spamd[590]: config: cannot opendir
>> /var/lib/spamassassin/3.001003: Permission denied
>>
>
>
>> The directory /var/lib/spamassassin/3.001003 exists and there's another
>> directory in there with the new rules, just like the wiki says about
>> sa-update, and if I run spamassassin -D --lint it shows no problems, and
>> I'm also able to scan emails through that just fine, just not spamd
>>
>
> Hrm, that's extremely odd. Is there something special about how you run
> spamd? chroot jail? limitations via something like selinux?
>
Thank god, you pointed me in the right direction.
The server is a fedora core 5 server where spamassassin has been
installed by yum/rpm and selinux was set to enforcing. It has now been
set to disabled, and it can now read the files.
Regards,
Bjorn Jensen
Re: sa-update problems
Posted by Theo Van Dinter <fe...@apache.org>.
On Thu, Aug 03, 2006 at 06:15:38PM +0200, Bjorn Jensen wrote:
> Aug 3 18:05:30 mail3 spamd[590]: config: cannot opendir
> /var/lib/spamassassin/3.001003: Permission denied
> Aug 3 18:05:30 mail3 spamd[590]: config: cannot opendir
> /var/lib/spamassassin/3.001003: Permission denied
> The directory /var/lib/spamassassin/3.001003 exists and there's another
> directory in there with the new rules, just like the wiki says about
> sa-update, and if I run spamassassin -D --lint it shows no problems, and
> I'm also able to scan emails through that just fine, just not spamd
Hrm, that's extremely odd. Is there something special about how you run
spamd? chroot jail? limitations via something like selinux?
Generally speaking, if the dirs can be accessed via any general user w/
spamassassin, there shouldn't be any problem using spamd.
> [root@mail3 spamassassin]# ll /var/lib/spamassassin
> total 8
> drwxr-xr-x 3 root root 4096 Aug 3 17:53 3.001003
> [root@mail3 spamassassin]# ll /var/lib/spamassassin/3.001003
> total 16
> drwxr-xr-x 2 root root 4096 Aug 3 17:53 updates_spamassassin_org
> -rw-r--r-- 1 root root 2151 Aug 3 17:53 updates_spamassassin_org.cf
Hrm. This looks fine to me.
--
Randomly Generated Tagline:
"... and don't we all love Pspice?" - Instructor Dean