On Wed, 2009-03-04 at 15:36 +0000, Sujit Acharyya-Choudhury wrote: > Just to clarify the exim spamd config is as follows in the data section:
Looks sane enough. However, this is a SpamAssassin problem, not Exim. Exim is reporting to you that a specific SA connection timed out - which implies that the SA child handling the connection wedged in some way. Is SA setup to do a lot of DNS lookups or other online tests? Can you be absolutely sure that these aren't causing some scans to go slowly - eg. if a TCP session has to be opened to some external app or service, is that working? You might want to turn up the debug level in SA, or do some other type of connection tracking so you know exactly which message the child was processing when it timed out. We also see this, but I usually ignore it unless it's for every single message... Graeme -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
