Jeremy Fried wrote:
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.
Try running named.