On Fri, 2011-04-08 at 04:41:59 +0200, Amedeo Rinaldo wrote:

> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Apr 8 03:28:46 mx20 postfix/postscreen[16419]: CONNECT from
> [190.135.213.150]:18780
> Apr 8 03:28:55 mx20 postfix/postscreen[16419]: NOQUEUE: reject: RCPT
> from [190.135.213.150]:18780: 450 4.3.2 Service currently
> unavailable; from=<no-reply...@job.de>, to=<eb...@validdomain.com>,
> proto=ESMTP, helo=<anteldata.net.uy>
> Apr 8 03:28:55 mx20 postfix/postscreen[16419]: HANGUP after 1.6 from
> [190.135.213.150]:18780 in tests after SMTP handshake
> Apr 8 03:28:55 mx20 postfix/postscreen[16419]: PASS NEW
> [190.135.213.150]:18780
> Apr 8 03:28:55 mx20 postfix/postscreen[16419]: DISCONNECT
> [190.135.213.150]:18780
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 
> PASS NEW ?? ..infact a second later:

>From the POSTSCREEN_README:

 When a good client passes the deep protocol tests, postscreen(8) adds
 the client to the temporary whitelist but it cannot hand off the "live"
 connection to a Postfix SMTP server process in the middle of the
 session. Instead, postscreen(8) defers mail delivery attempts with a 4XX
 status, logs the helo/sender/recipient information, and waits for the
 client to disconnect.

 The next time the client connects it will be allowed to talk to a
 Postfix SMTP server process to deliver its mail.

> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Apr 8 03:29:37 mx20 postfix/postscreen[16419]: CONNECT from
> [190.135.213.150]:19436
> Apr 8 03:29:37 mx20 postfix/postscreen[16419]: PASS OLD
> [190.135.213.150]:19436
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 
> If the client didn't close properly the connection, is the intended
> behaviour to 'PASS NEW' that client ? Odd, i expected postscreen to
> repeat tests the next time the client connects.

In certain situations, some SMTP clients do not send QUIT; this is
logged as a HANGUP but not treated as a protocol test failure.  Do not
mistake logging of HANGUP to mean test failure.

-- 
Sahil Tandon <sa...@freebsd.org>

Reply via email to