Don't send copies, I'm subscribed.

On Tue, Apr 23, 2013 at 01:01:20PM +0200, Ludovic LEVET wrote:
> The transcription is on mail first mail :

This is no transcript. This is several smtpd sessions intermingled.

> Why nobody complain ? the response is in the session transcription :
> ...
> 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]

This is no smtp proxy. This is a smtp server receiving stuff from
localhost and it times out.

> During this time (define by smtpd_proxy_timeout=600s ), there is a
> lot of pending process from smtpd and perl dkim, this 2 process wait
> for end of communication, until postfix close the connection by time
> out.

Wrong side. This is the normal session timeout and have nothing to do
with a proxy.

> But, normaly postfix smtp must send a 'QUIT' command if the socket
> is not reuse (cache connexion process) but  the param
> 'smtp_connection_cache_on_demand=no' is not take care.

It doesn't even need to close the connection.

> The mail is transfered well, but the connexion is not terminate properly.

Show proof.

> So, like you said in 3.8 of RFC5321 confirm what i said :

Stop arguing with standards.

> Le 23/04/2013 12:12, Bastian Blank a écrit :
> >Please fix your MUA, it produces TOFU.

As you ignored be: PLONK and EOD.

Bastian

-- 
Most legends have their basis in facts.
                -- Kirk, "And The Children Shall Lead", stardate 5029.5

Reply via email to