> On Apr 17, 2018, at 8:38 AM, @lbutlr <[email protected]> wrote:
>
> Apr 17 00:00:09 mail postfix/postscreen[67061]: CONNECT from
> [94.237.32.243]:46598 to [65.121.55.42]:25
> Apr 17 00:00:09 mail postfix/dnsblog[74920]: addr 94.237.32.243 listed by
> domain hostkarma.junkemailfilter.com as 127.0.0.1
> Apr 17 00:00:09 mail postfix/dnsblog[74920]: addr 94.237.32.243 listed by
> domain hostkarma.junkemailfilter.com as 127.0.1.1
> Apr 17 00:00:09 mail postfix/dnsblog[74865]: addr 94.237.32.243 listed by
> domain score.senderscore.com as 127.0.4.97
> Apr 17 00:00:09 mail postfix/dnsblog[74950]: addr 94.237.32.243 listed by
> domain list.dnswl.org as 127.0.9.2
> Apr 17 00:00:10 mail postfix/postscreen[67061]: PASS OLD [94.237.32.243]:46598
> Apr 17 00:00:11 mail postfix/smtpd[84666]: connect from
> wursti.dovecot.fi[94.237.32.243]
> Apr 17 00:00:39 mail postfix/smtpd[84666]: disconnect from
> wursti.dovecot.fi[94.237.32.243] ehlo=1 mail=0/1 rcpt=0/1 data=0/1 rset=0/1
> quit=1 commands=2/6
The mail/rcpt/data commands were pipelined together, and all three were
rejected, then the remote client issued RSET and QUIT, but RSET was also
rejected! The only way that RSET is rejected (barring unlikely syntax errors)
is indeed if you're enforcing TLS, which would also explain why mail/rcpt/data
were rejected.
--
Viktor.
