Alan, > I've upgraded a box to fedora 5 today. There were no application upgrades > as the core 4 was running Postfix 2.2.10, Amavisd-new 2.4, Spamassassin > 3.1.1. Things look like they are OK, but the Postfix queue is backing up. > > May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) (!) ESMTP ABORTING: timed > out during waiting for input from client May 5 01:25:22 mx1 amavis[2152]: > (02152-03-2) TempDir::strip: /var/amavis/tmp/amavis-20060505T010059-02152 > May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) rmdir_recursively: > /var/amavis/tmp/amavis-20060505T010059-02152/parts, excl=1 > May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) TIMING [total 480018 ms] > lookup_sql: 10 (0%)0, SMTP pre-DATA-flush: 5 (0%)0, unlink-0-files: 480004
After 8 minutes of inactive session from Postfix ($smtpd_timeout), amavisd is disconnecting a session. This may even be normal, but is unusual: the Postfix parameter smtp_connection_cache_time_limit (or its lmtp counterpart) is normally set to 2 seconds, so Postfix should have disconnected first, much before 8 minutes. Postfix lmtp client used to be much more persistent - but all this assumes there are no messages to be processed, waiting in the queue. You may check the corresponding Postfix log entry, or even look at tcpdump of the session on loopback interface. Grep also for logged entries of id '(02152-03-2)' before the ESMTP ABORTING. Make sure the $max_servers (amavisd.conf) matches maxproc (master.cf) of the Postfix service feeding amavisd. This has nothing to do with Net::SMTP as Gary suspected, the Net::SMTP implements client side of the SMTP protocol, while the above happens on the server side (sub process_smtp_request). > I'm assuming that this is spamassassin timing out because when I run with > debug-sa it gets as far as these messages and stops: > > [3159] dbg: auto-whitelist: post auto-whitelist score: 2.906 > [3159] dbg: rules: running body-text per-line regexp tests; score so > far=2.906 [3159] dbg: uri: running uri tests; score so far=2.906 > [3159] dbg: rules: running raw-body-text per-line regexp tests; score so > far=2.906 [3159] dbg: rules: running full-text regexp tests; score so > far=2.906 [3159] dbg: check: is spam? score=2.906 required=5 > [3159] dbg: check: > tests=MISSING_SUBJECT,NO_REAL_NAME,NO_RECEIVED,NO_RELAYS,TO_CC_NONE [3159] > dbg: check: > subtests=__HAS_MSGID,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__NONEMPTY_BODY,__SA >NE_MSGID,__SARE_WHITELIST_FLAG,__SOBER_P_MSGID,__UNUSABLE_MSGID Perhaps, but this bears no direct relationship with your log above. Mark ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
