does qmail-scanner disable the system using spamd??

Zenith · Unread post by **Zenith** » Fri Jan 07, 2005 8:38 am

After installing qmail-scanner i discovered lots of errors in my maillog (located at /usr/local/psa/var/log/maillog) like this one.

Code: Select all

Jan  6 06:44:58 p12345678 spamc[17128]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jan  6 06:44:59 p12345678 spamc[17128]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused
Jan  6 06:45:00 p12345678 spamc[17128]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused
Jan  6 06:45:01 p12345678 spamc[17128]: connection attempt to spamd aborted after 3 retries
Jan  6 06:45:01 p12345678 qmail: 1104993901.349468 new msg 29399280
Jan  6 06:45:01 p12345678 qmail: 1104993901.349694 info msg 29399280: bytes 4778 from <auto-shipping@amazon.co.uk> qp 17146 uid 2520
Jan  6 06:45:01 p12345678 qmail: 1104993901.353850 starting delivery 265: msg 29399280 to local 4-USERNAME@DOMAINNAME.com
Jan  6 06:45:01 p12345678 qmail: 1104993901.354035 status: local 1/10 remote 0/20
Jan  6 06:45:01 p12345678 qmail-scanner[17123]: Clear:RC:0(207.171.180.180):SA:0(?/?): 3.093331 4365 auto-shipping@amazon.co.uk USERNAME@DOMAINNAME.com Your_Amazo
n.co.uk_order_has_dispatched_(#202-0220104-5928665) <j066RDBb000666.200501060627@dc-mail-3102.iad3.amazon.com> 1104993898.17125-0.p12345678.pureserver.info:3693
 orig-p12345678.pureserver.info110499389868017123:4365
Jan  6 06:45:01 p12345678 spamd[9965]: got connection over /tmp/spamd_full.sock
Jan  6 06:45:01 p12345678 spamd[17153]: Using default config for USERNAME@DOMAINNAME.com: /var/qmail/mailnames/DOMAINNAME.com/USERNAME/user_prefs
Jan  6 06:45:01 p12345678 spamd[17153]: processing message <j066RDBb000666.200501060627@dc-mail-3102.iad3.amazon.com> for USERNAME@DOMAINNAME.com:110.

What I'd like to know is does the qmail-scanner disable access to the spamd when accessed via spamc or directly? Does anyone else have this problem?

PS) I could dig out other different error messges if it would help.

Unread post by **scott** » Fri Jan 07, 2005 9:36 am

no, that message means spamd isnt running. spamc is just a client, used to communicate with spamd

Zenith · Unread post by **Zenith** » Fri Jan 07, 2005 10:02 am

Yes i know it looks like that but spamd was running at the time, which was what made it so strange.

I restarted the psa-spamassassin, spamassassin services & even rebooted but still got the same or similar errors.

The other error thing I kept seeing was:

Jan 6 21:24:20 p12345678 spamd[779]: info: setuid to root succeeded
Jan 6 21:24:21 p12345678 spamd[779]: Still running as root: user not specified with -u, not found, or set to root. Fall back to nobody.
Jan 6 21:24:21 p12345678 spamd[779]: processing message <00m94g5gf2f73f9b@users.sourceforge.net> for root:99.
Jan 6 21:24:21 p12345678 spamd[779]: cannot write to /root/.spamassassin/bayes_journal, Bayes db update ignored
Jan 6 21:24:21 p12345678 spamd[779]: bayes expire_old_tokens: lock: 779 cannot create tmp lockfile /root/.spamassassin/bayes.lock.p12345678.pureserver.info.779
for /root/.spamassassin/bayes.lock: Permission denied
Jan 6 21:24:25 p12345678 spamd[779]: clean message (-1.5/6.0) for root:99 in 4.6 seconds, 394 bytes.
Jan 6 21:24:25 p12345678 spamd[380]: connection from localhost.localdomain [127.0.0.1] at port 35890
Jan 6 21:24:25 p12345678 spamd[788]: info: setuid to root succeeded
Jan 6 21:24:25 p12345678 spamd[788]: Still running as root: user not specified with -u, not found, or set to root. Fall back to nobody.
Jan 6 21:24:25 p12345678 spamd[788]: processing message <00m94g5gf2f73f9b@users.sourceforge.net> for root:99.
Jan 6 21:24:26 p12345678 spamd[788]: cannot write to /root/.spamassassin/bayes_journal, Bayes db update ignored
Jan 6 21:24:26 p12345678 spamd[788]: bayes expire_old_tokens: lock: 788 cannot create tmp lockfile /root/.spamassassin/bayes.lock.p12345678.pureserver.info.788
for /root/.spamassassin/bayes.lock: Permission denied

also i am thinking that this following bit of my mail log means that an unknown user has been mailed and the system defaults back to root to process it.....

Jan 6 21:30:31 p12345678 spamd[380]: connection from localhost.localdomain [127.0.0.1] at port 35939
Jan 6 21:30:31 p12345678 spamd[1694]: handle_user: unable to find user 'postmaster@p12345678.pureserver.info'!
Jan 6 21:30:31 p12345678 spamd[1694]: Still running as root: user not specified with -u, not found, or set to root. Fall back to nobody.
Jan 6 21:30:31 p12345678 spamd[1694]: checking message (unknown) for postmaster@p12345678.pureserver.info:99.
Jan 6 21:30:40 p12345678 spamd[1694]: clean message (2.0/6.0) for postmaster@p12345678.pureserver.info:99 in 8.7 seconds, 2703 bytes.
Jan 6 21:30:40 p12345678 qmail-scanner[1687]: Clear:RC:1(127.0.0.1):SA:0(2.0/6.0): 12.37421 2681 #@[] postmaster@p12345678.pureserver.info <> <1105047027880168
7@p12345678.pureserver.info> 1105047027.1689-0.p12345678.pureserver.info:2463 orig-p12345678.pureserver.info11050470276801687:2681

Unread post by **scott** » Fri Jan 07, 2005 10:11 am

THe cannot find user error is harmless, that means its trying to look up that users settings in mysql and they dont exist. The bayes error means that spamd is permissions related. It should be trying to read that from /var/qmail/.spamassassin instead of ~root. Sounds like a configuration error in the sysconfig/spamassassin file. Make sure it has -H /var/qmail on the end.