Spam Assassin Issue

[e1kosau]

hi im watching this thread for a couple of days now. any news about this? im also getting spam bigtime and it gets rejected (some of it though) but your support told me that my rules cant be read by spamd because of the error

Code: Select all

Still running as root: user not specified with -u, not found, or set to root.  Fall back to nobody.



my question is where i can find that rule?

thanks.

don

[burhankhalid]

Does anyone have any idea what to do about this error in /var/log/maillog :

Code: Select all

Mar 18 10:05:05 avalon spamd[18033]: spamd starting
Mar 18 10:05:06 avalon spamd[18035]: server started on port 783/tcp (running version 3.0.4)
Mar 18 10:05:06 avalon spamd[18035]: server successfully spawned child process, pid 18038
Mar 18 10:05:06 avalon spamd[18035]: server successfully spawned child process, pid 18039
Mar 18 10:05:06 avalon spamd[18035]: server successfully spawned child process, pid 18040
Mar 18 10:05:06 avalon spamd[18035]: server successfully spawned child process, pid 18041
Mar 18 10:05:06 avalon spamd[18035]: server successfully spawned child process, pid 18042
Mar 18 10:05:13 avalon spamass-milter[5878]: SpamAssassin: mi_stop=1
Mar 18 10:05:13 avalon spamass-milter[5878]: spamass-milter 0.3.0 exiting
Mar 18 10:05:16 avalon spamass-milter[18082]: spamass-milter 0.3.0 starting
Mar 18 10:06:59 avalon sendmail[18093]: k2I76x7v018093: from=<foo@bar.com>, size=1118, class=0, nrcpts=1, msgid=<12170776.1142665516192.JavaMail.root@webmail.example.com>, proto=ESMTP, relay=root@localhost
Mar 18 10:06:59 avalon sendmail[18094]: k2I76xjO018094: Milter (spamassassin): error connecting to filter: Connection refused by /var/run/spamassassin/spamd.pid
Mar 18 10:06:59 avalon sendmail[18094]: k2I76xjO018094: Milter (spamassassin): to error state


I have verified that this is not a spamassassin configuration problem, because spamc can successfully check messages without errors. So has anyone got this setup going on FC4?

[ScalixSupport]

First thing to check is that the socket file defined by spamass-milter is the same socket file as the one defined in the Milter definition in sendmail.cf

Cheers

Dave

[ahathaway]

hi im watching this thread for a couple of days now. any news about this? im also getting spam bigtime and it gets rejected (some of it though) but your support told me that my rules cant be read by spamd because of the error

Code: Select all

Still running as root: user not specified with -u, not found, or set to root.  Fall back to nobody.



my question is where i can find that rule?

thanks.

don

Don,

One thing the KB article doesn't cover is who spamassassin runs as. The default setup will have spamassassin running as nobody. Anyone can freel free to correct me on this point, but this will prevent auto-learning for bayesian filtering and auto-whitelisting.

The usual solution is to configure spamassassin to run as another user, like spamd. Then all the relevant files can be placed in /home/spamd/.spamassassin (note: make sure you su to that user when you run sa-learn, to make sure that the right bayes databases get updated).

The options line in /etc/init.d/spamassassin (and/or /etc/sysconfig/spamassassin) should look like this:

Code: Select all

SPAMDOPTIONS="-x -d -c -m5 -H /home/spamd/.spamassassin -u spamd"

Also, as has been pointed out elsewhere in these forums, you'll want to change the spamass-milter script to permit it to alter headers (by removing the "-m" flag and adding a user):

Code: Select all

EXTRA_FLAGS="-r 15 -u spamd"

This seems to work well for me.

--Aaron

[garethm]

I've taken a slightly different tack here - I'm allowing it to carry on running as "nobody" but I've created a "spamassassin" directory under /var/opt/scalix (so it gets included in the backups), with directory writeable by "nobody", and I added:these lines to /etc/mail/spamassassin/local.cf:

Code: Select all

# Enable the Bayes system
use_bayes               1
bayes_path              /var/opt/scalix/spamassassin/

# Enable Bayes auto-learning
bayes_auto_learn              1


It's working really well.