You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Dirk Kuypers <dk...@comnets.rwth-aachen.de> on 2005/05/04 13:15:16 UTC
Debugging spamd/spamc interaction
Hi,
we want to migrate our old mailserver (Sun E450 with Solaris 2.7, sendmail and
SA 2.64) to a Linux rack-server with debian linux, qmail and SA 3.x on it.
Now the new box is up and running so far and I wanted to test it first with
spamd/spamc to compare the more or less vanilla SA 3 performance with our old
setup of 2.64 with lots of custom rule-sets (but which gets more and more
outdated and annoys me;-).
I started spamd from the command line:
in:~# /usr/sbin/spamd --create-prefs --max-children 5 --helper-home-dir -A
137.226.4.0/24 -D --pidfile=/var/run/spamd.pid
trying to connect to syslog/unix...
no error connecting to syslog/unix
logging enabled:
facility: mail
socket: unix
output: syslog
creating INET socket:
Listen: 128
LocalAddr: 127.0.0.1
LocalPort: 783
Proto: 6
ReuseAddr: 1
Type: 1
debug: SpamAssassin version 3.0.2
[...]
logmsg: server started on port 783/tcp (running version 3.0.2)
logmsg: server successfully spawned child process, pid 4886
logmsg: server successfully spawned child process, pid 4887
logmsg: server successfully spawned child process, pid 4888
logmsg: server successfully spawned child process, pid 4889
logmsg: server successfully spawned child process, pid 4890
server pid: 4884
So at least everything seems to be running. But when I try to connect from
another machine, I get the following errors:
dk@brucez:~/Documents> spamc -d gin -l < SPAM.vanilla
spamc: connect(AF_INET) to spamd at 137.226.4.160 failed, retrying (#1 of 3):
Connection refused
spamc: connect(AF_INET) to spamd at 137.226.4.160 failed, retrying (#2 of 3):
Connection refused
spamc: connect(AF_INET) to spamd at 137.226.4.160 failed, retrying (#3 of 3):
Connection refused
spamc: connection attempt to spamd aborted after 3 retries
But: I don't get an entry at the log files of the spamd host. I can't even
test it on gin itsself, the same result.
What can I do to debug this situation? Why is the spamd host not listening? Is
it because of qmail? I think it get's somehow started with qmail-scanner
normally, but I am not the one configuring the mail-server...
Thanks for any help
Dirk
--
Dipl.-Ing. Dirk Kuypers
Lehrstuhl fuer Kommunikationsnetze, RWTH Aachen
Kopernikusstr. 16, 52074 Aachen, W101
Tel: +49 241 879 3779, RWTH: +49 241 (80) 20547