I've got after-220 tests turned off
postconf | grep postscreen | egrep -i "bare|non_smtp|pipelining"
postscreen_bare_newline_action = ignore
postscreen_bare_newline_enable = no
postscreen_bare_newline_ttl = 30d
postscreen_non_smtp_command_action = drop
postscreen_non_smtp_command_enable = no
postscreen_non_smtp_command_ttl = 30d
postscreen_pipelining_action = enforce
postscreen_pipelining_enable = no
postscreen_pipelining_ttl = 30d
My intention is to NOT suffer mail delays due to these tests.
In my logs I've seen a very few
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: CONNECT from
[106.184.3.122]:42098 to [192.0.2.12]:25
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: PREGREET 156 after 0
from [106.184.3.122]:42098:
\000\234\000\001\032+<M\000\001\000\000\001\000\000\000\000\000\000\001\000\000\000\001\000\000\n(\0
Apr 19 02:11:09 mail01 postfix/dnsblog[1723]: addr 106.184.3.122 listed
by domain zen.spamhaus.org as 127.0.0.4
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: DNSBL rank 6 for
[106.184.3.122]:42098
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: BARE NEWLINE from
[106.184.3.122]:42098 after
\000\234\000\001\032+<M\000\001\000\000\001\000\000\000\000\000\000\001\000\000\000\001\000\000
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: COMMAND PIPELINING
from [106.184.3.122]:42098 after :
(\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: HANGUP after 0.12 from
[106.184.3.122]:42098 in tests after SMTP handshake
Apr 19 02:11:09 mail01 postfix/postscreen[1717]: DISCONNECT
[106.184.3.122]:42098
which LOOKS to me like both bare_newline test is exec'd.
Reading
http://www.postfix.org/POSTSCREEN_README.html#barelf
This test is opportunistically enabled when postscreen(8) has
to use the built-in SMTP engine anyway. This is to make postscreen(8) logging
more informative.
and similarly for pipelining.
(1) Is this an example of that opportunistic enabling^ of ps' after-220 tests?
So, I'm not inadvertently causing any of those delays?
(2) I've not yet seen examples of those long "...000\..." strings. Is that
typical, and simply logging what's being sent? Or is that evidence of some
attempt at input buffer overrun, etc?
Mainly I just want to make sure I've not missed or misconfigured something, and
that this is just business as normal.
Jason
