Hello,
[EMAIL PROTECTED] wrote:
Hi,
netstat -lnp | grep spamd
Does not find spamd.
instead netstat -lnp shows the process running on port 783:
tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN 24813/perl
and gives it the name perl since:
ps aux
spamd 24813 0.0 3.8 21676 19904 ? S 15:26 0:00 /usr/bin/perl -T -w /usr/bin/spamd -d -D
I can also telnet into spamd.
Does the failure have anything to do with the ... 24813/perl where perl should be spamd? I wonder.
I think it's not a problem as your spamd listens for localhost/783. What about your spamd logs? Have you checked your firewall (if any) as it looks like your firewall is blocking spamc's connection to localhost/783. You can also try --socketpath directive of spamd with -U option of spamc to enable UNIX domain socket communication instead of TCP socket communication.
Thanks for the help. I wonder when the spam gods will give me a break.
Regards, Phillip Lucs
Hello,
[EMAIL PROTECTED] wrote:
Hi to the group,
Spamassassin is not checking my emails yet. One of the tests that is failing is the following.
cd /usr/local/src/Mail-SpamAssassin-2.63
make test
Which results in the following log file messages.
tail /var/log/mail.err
May 5 23:04:20 emu spamc[24520]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused May 5 23:04:21 emu spamc[24520]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused May 5 23:04:22 emu spamc[24520]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused May 5 23:04:23 emu spamc[24520]: connection attempt to spamd aborted after 3 retries
What about checking:
netstat -lnp | grep spamd
it should listen on tcp/783
if it's there then spamd is listening for connections and spamc is unable to connect. Check you firewall rules. Maybe you are blocking the connections?
I have googled and found that this refers to a case when spamd is not running, however spamd is running.
ps afx
24813 ? S 0:00 /usr/bin/perl -T -w /usr/bin/spamd -x -u spamd -H /home/spamd -d -D
More googling of the error revealed that reinstalling spamassassin from CPAN may be required.
perl -MCPAN -e 'install Mail::SpamAssassin'
This revealed that my build was up to date. When I restarted spamassassin I still had the same problem.
I am really stuck and need help.
My only though at this stage is that spamassassin is not working since I have not connected the spamassassin box to the internet.
Regards, Phillip Lucs
Best Regards,
-- George Chelidze
Best Regards,
-- George Chelidze
