Am 2013-04-23 14:22, schrieb Wietse Venema:
> Apr 22 14:20:08 dedi postfix/smtpd[2974]: smtp_get: timeout
> Apr 22 14:20:08 dedi postfix/smtpd[2974]: >
> dedi.ludosoft.org[127.0.0.1]: 421 4.4.2 dedi.ludosoft.org Error:
> timeout exceeded
> Apr 22 14:20:08 dedi postfix/smtpd[2974]: match_hostname:
> dedi.ludosoft.org ~? 127.0.0.0/8
> Apr 22 14:20:08 dedi postfix/smtpd[2974]: match_hostaddr: 127.0.0.1
> ~? 127.0.0.0/8
> Apr 22 14:20:08 dedi postfix/smtpd[2974]: timeout after
> END-OF-MESSAGE from dedi.ludosoft.org[127.0.0.1]
> Apr 22 14:20:08 dedi postfix/smtpd[2974]: disconnect from
> dedi.ludosoft.org[127.0.0.1]

After sending END-OF-MESSAGE, the Postfix smtpd_proxy_CLIENT closes
the SMTP connection to the before-queue content filter.

And this is exactly the problem: smtpd_proxy_CLIENT closes the connection without sending the QUIT command first, which is in violation of RFC 5321, section "4.1.1.10. QUIT (QUIT)"

We see the same behavior here with pre-queue amavisd:

Apr 23 22:01:21 lxmhs57 amavis[32118]: (32118-01) ESMTP> 554 5.7.0 Reject, id=32118-01 - spam Apr 23 22:01:21 lxmhs57 postfix-mwnin/smtpd[32156]: < [127.0.0.1]:10001: 554 5.7.0 Reject, id=32118-01 - spam Apr 23 22:01:21 lxmhs57 postfix-mwnin/smtpd[32156]: > unknown [95.58.34.47]: 554 5.7.0 Reject, id=32118-01 - spam Apr 23 22:01:21 lxmhs57 postfix-mwnin/smtpd[32156]: proxy-reject: END-OF-MESSAGE: 554 5.7.0 Reject, id=32118-01 - spam; from=<SPAMMER> to=<CUSTOMER> proto=ESMTP helo=<bla>
Apr 23 22:01:21 lxmhs57 amavis[32118]: (32118-01) smtp readline: EOF
Apr 23 22:01:21 lxmhs57 amavis[32118]: (32118-01) SMTP session over, timer stopped Apr 23 22:01:21 lxmhs57 amavis[32118]: (32118-01) ESMTP: notice: client broke the connection without a QUIT ()


Apparently the content filter is waiting for QUIT *after* the
connection is closed. Please file a bug report for the content
filter.

        Wietse

Wietse, this was a bug report for Postfix! Filing a bug report for the content filter because it does not check for a dropped connection is another story.

Michael

Reply via email to