Ralf Hildebrandt:
> Today a fellow postmaster (using Exim) called me, they were having problems
> sending
> mail to charite.de. In my log I found:
>
> Sep 3 00:31:18 mail-cbf postfix/postscreen[34943]: CONNECT from
> [31.7.179.105]:38256 to [193.175.73.208]:25
> Sep 3 00:31:24 mail-cbf postfix/tlsproxy[39995]: CONNECT from
> [31.7.179.105]:38256
> Sep 3 00:31:24 mail-cbf postfix/tlsproxy[39995]: Anonymous TLS connection
> established from [31.7.179.105]:38256: TLSv1.2 with cipher
> ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
> Sep 3 00:31:24 mail-cbf postfix/postscreen[34943]: NOQUEUE: reject: RCPT
> from [31.7.179.105]:38256: 450 4.3.2 Service currently unavailable;
> from=<[email protected]>, to=<[email protected]>, proto=ESMTP,
> helo=<smtpgw03.nextwerk.de>
> Sep 3 00:31:24 mail-cbf postfix/postscreen[34943]: COMMAND PIPELINING from
> [31.7.179.105]:38256 after BDAT: Received: from [213.182.136.75]
> (helo=NWH-EX13.nwcloud.loc)\r\n\tby smtpgw03.nextwerk.de with esmtpsa (
>
> After I disabled chunking, mail would flow again.
> Is this an Exim issue or a flaw in the newly introduced BDAT feature?
The client is at fault. Postscreen DOES NOT announce PIPELNING support.
Wietse
