Hi Wietse,
I'm agree with you, after sending END-OF-MESSAGE, the Postfix
smtpd_proxy_CLIENT closes the SMTP connection
to the before-queue content filter without sending QUIT command and wait
for a 221 reply.
But Postfix smtpd complain to be compatible with ESMTP protocol
(http://www.postfix.org/SMTPD_PROXY_README.html), and specify in Postfix
Before-Queue Content Filter 'How Postfix talks to the before-queue
content filter' that QUIT command is used.
It this true on postfix 2.6.x but not on upper version.
So, DKIMproxy work like it will be, it repeat the same dialog in IN
(port 10025) to OUT (port 10026) and add only status in header. So, if
it don't received QUIT command in IN, it don't send it in OUT.
Then the problem is well in Postfix smtpd_proxy_CLIENT (was ok on 2.6.x
version).
So, i think and i said that ESMTP protocol will be fully respected by
Postfix smtpd_proxy_CLIENT.
Modifying dkimproxy will be only a workaround for this problem, but it
will not be serious implemantation in respect of RFC.
Are you agree with me ?
Ludovic.
Le 23/04/2013 14:22, Wietse Venema a écrit :
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.
Apparently the content filter is waiting for QUIT *after* the
connection is closed. Please file a bug report for the content
filter.
Wietse
