On Thu, Jul 19, 2018 at 09:14:30AM -0400, James B. Byrne wrote:
> We are encountering errors with several domains similar to the one
> reported by samba.org:
>
> Jul 18 22:36:38 mx31 postfix-p25/smtpd[17802]: lost connection after
> DATA (0 bytes) from mailroot5.namespro.ca[158.85.87.68]
> Jul 18 22:36:38 mx31 postfix-p25/smtpd[17802]: disconnect from
> mailroot5.namespro.ca[158.85.87.68] ehlo=2 starttls=1 mail=1 rcpt=2
> data=0/1 commands=6/7
This does not look *at all* similar to me. The client sent:
EHLO
STARTTLS + TLS complete handshake
EHLO (inside TLS encrypted stream)
MAIL FROM: (inside TLS encrypted stream)
RCPT TO: (inside TLS encrypted stream)
RCPT TO: (inside TLS encrypted stream)
DATA: (inside TLS encrypted stream)
Then connection was lost after "DATA". This is *not* a TLS handshake
failure. Looks rather more like an ordinary message transmission
failure, or perhaps data-stage greylisting, ...
You really need to show more of the (non-verbose) logging for this
session and the below. You're cutting out critical context.
> Jul 18 23:41:45 mx31 postfix-p25/smtpd[97338]: NOQUEUE:
> client=mail.rosedale.ca[66.135.118.147]
> Jul 18 23:41:45 mx31 postfix-p25/smtpd[97338]: lost connection after
> DATA (0 bytes) from mail.rosedale.ca[66.135.118.147]
> . . .
>
> This is causing us problems in our operational departments. Based on
> the message traffic surrounding this issue I have changed the client
> certificate request setting to 'no' to see if that improves delivery.
A good idea, but exceedingly unlikely to make any difference for
the cases above.
--
Viktor.
