I've started noticing messages like these in my logs and the logs on
mx1.FreeBSD.org in recent months:
Oct 13 00:58:21 rincewind postfix/postscreen[76460]: COMMAND PIPELINING
from [46.101.147.153]:59818 after BDAT: DKIM-Sig
nature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=masozm.com;\r\n\t s=mail; h=Content-
Oct 13 17:12:51 rincewind postfix/postscreen[60205]: COMMAND PIPELINING
from [198.180.150.2]:37464 after BDAT: Received: from
h1fa3.n1.ips.mtn.co.ug ([41.210.159.163] helo=[192.168.8.100])\r\n\tby
mail.rg.net with
Oct 13 17:12:59 rincewind postfix/postscreen[60205]: COMMAND PIPELINING
from [198.180.150.2]:33740 after BDAT: Received: from
h1fa3.n1.ips.mtn.co.ug ([41.210.159.163] helo=[192.168.8.100])\r\n\tby
mail.rg.net with
The senders are running recent Exim versions.
There was a discussion on this list about a year ago which resulted in a
patch against Postfix 3.4-20180903.
Did this issue accidentally get unfixed or is this a new interop issue
with Exim? I'm running 3.4.7. What can I do to debug this better?
I've turned postscreen_pipelining_enable off on mx1.FreeBSD.org for the
time being because it was getting a lot of legitimate email deferred
(and timed out).
Philip
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
