Xueron Nee, > I have just got a problem about a message with multi recipients. > > the message has 18 recipients, and amavisd-new forwards it to my dspam > using pipeline. But the first recipient got a negative SMTP response to > data-dot, and which caused the message be delivered again and again. > > But when I test it manually, pipeline was not used any more:( But just > connection reuse. So I cannot reappear the problem.
>Aug 31 14:57:07 pe6850b amavis[2587]: (02587-14) smtp resp to RCPT (pip) > (<[email protected]>): 250 2.1.5 OK >Aug 31 14:57:07 pe6850b amavis[2587]: (02587-14) smtp resp to DATA: > 354 Enter mail, end with "." on a line by itself >Aug 31 14:57:07 pe6850b amavis[2587]: (02587-14) smtp cmd> QUIT >Aug 31 15:04:53 pe6850b amavis[2587]: (02587-14) (!)rw_loop: leaving rw loop, > no progress, last event (select) 465.938 s ago >Aug 31 15:04:53 pe6850b amavis[2587]: (02587-14) smtp resp to data-dot > (<[email protected]>): >Aug 31 15:04:53 pe6850b amavis[2587]: (02587-14) Negative SMTP response > to data-dot (<[email protected]>): >Aug 31 15:12:39 pe6850b amavis[2587]: (02587-14) (!)rw_loop: leaving rw loop, > no progress, last event (select) 465.937 s ago >Aug 31 15:12:39 pe6850b amavis[2587]: (02587-14) smtp resp to data-dot > (<[email protected]>): >Aug 31 15:12:39 pe6850b amavis[2587]: (02587-14) Negative SMTP response > to data-dot (<[email protected]>): >Aug 31 15:13:55 pe6850b amavis[2587]: (02587-14) smtp resp to data-dot > (<[email protected]>): 250 2.6.0 <[email protected]> Message accepted > for delivery The problem here is that DSPAM lmtp server takes 17 minutes to start responding after receiving a message. Meanwhile amavisd times out (twice), waiting for response. Which is why the end result is a temporary failure. (there is a subsequent problem that LMTP protocol gets out of step, letting timeout responses to data-end inappropriately advance on the list of per-recipient responses, which I'll need to address, but is not affecting your case) You could try increasing $child_timeout (in amavisd.conf) and $smtp_data_done_timeout (default 600 s) in sub mail_via_smtp_single, although this will then get you in trouble on the input side with MTA. I'd say 17 minutes is way too long, and you should investigate why DSPAM is taking so long. I very much doubt this has anything to do with pipelining, more likely with the message contents itself. Mark ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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/
