Ok, problem solved. Spamassassin was taking 36 seconds on average to
process this message. The only way I could decrease this time is to
turn off remote checking (checking other databases). So, problem
solved. Thanks for the help.
Jeremy
On May 28, 2004, at 2:11 PM, Jeremy Fried wrote:
Yup I have the same setup. qmail+spamassassin+clamav and I think
you're definitely right about the problem. Although adding an MX
configuration to my domain name doesn't seem to be helping. Maybe I
need to wait a little bit for it to take effect. Would there be any
other way to fix this problem? Assuming it's the timeout that's the
problem.
Jeremy
On May 28, 2004, at 12:14 PM, Bill McCormick wrote:
jfried wrote:
I'm trying to use fetchmail to download my e-mail via pop3 (SSL
connection), but I keep running into the same error. I get this
socket error for different e-mails at random times. The only thing
that I found in common in all the e-mails is their size. They're
all spam too. The most recent is 1430 octets
[snip]
2004: poll completed
fetchmail: Query status=2 (SOCKET)
fetchmail: normal termination, status 2
Same problem here:
RH 9 2.4.20-6smp, fetchmail release 6.2.5+NLS
delivering to local qmail+spamassassisn+clamav
To me, the problem appears to be that on occassion SA takes a long
time to scan a message and then when fetchmail tries to continue the
connection has timed out. The problem was much worse (the machines
tcp/ip stack seemed to die) until I made the following changes:
1. upgraded my version of ddclient
2. added an MX configuration to ddclient.conf
I'm not sure really how any of this fits together. I'm just happy my
network connection keeps working now.
Cheers,
Bill
_______________________________________________
Fetchmail-friends mailing list
Fetchmail-friends(_at_)lists(_dot_)ccil(_dot_)org
http://lists.ccil.org/cgi-bin/mailman/listinfo/fetchmail-friends