friiz, > > PID 08733: A 0:02:08 =========:=========:=========:=====>
The indication above shows a stall during receiving of message by amavisd, between accepting a connection and start of processing... ... while the log below shows a stall during sending a message from amavisd back to Postfix. > > a tried with amavisd-2.3.3 - perl 5.8.0 > > and 2.4.2 perl 5.8.8 The log below seems to be from 2.3.3. (btw, 5.8.0 is to be avoided, use newer versions) > after running amavisd debug it stops while trying to send mail to > postfix smtpd > Jan 18 16:57:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) response to RCPT TO for <[EMAIL PROTECTED]>: "250 Ok" > Jan 18 16:57:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) prolong_timer after fwd-rcpt-to: remaining time 480 s > Jan 18 16:57:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) response to DATA: "354 End data with <CR><LF>.<CR><LF>" > Jan 18 16:57:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) write_header: 0, Amavis::Out=HASH(0xa5131c8) > Jan 18 16:57:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) prolong_timer after fwd-data: remaining time 480 s > > mail flow breaks here and waits until a timeout > Jan 18 17:02:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) prolong_timer after fwd-data-end: remaining time = 181 s Which comes exactly 5 minutes later. > Jan 18 17:02:33 fqdn.host.name /usr/local/sbin/amavisd[19175]: > (19175-01) response to data end: "421 Error: timeout > exceeded" Postfix aborted the session on timeout, because it did not receive or process the full message and the final dot in time. > Jan 18 16:57:33 linux postfix/smtpd[19310]: rec_put: type N len 19 data > X-Spam-Sco > Jan 18 16:57:33 linux postfix/smtpd[19310]: rec_put: type N len 18 data > X-Spam-Lev > Jan 18 16:57:33 linux postfix/smtpd[19310]: rec_put: type N len 0 data > > and there is no other sign of smtpd[19310] until timeout Do you have any header or body checks enabled in Postfix? Could be a deep recursion in regexp evaluation in Postfix filters. If this is not the case, you should capture a tcpdump on the SMTP session and see what really happens on the wire, e.g.: tcpdump -n -s 0 -i lo -w 0.log 'host 127.0.0.1 and tcp port 10025' then examine the log with wireshark or tcpdump -r. Mark ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
