On Thu, 16 Dec 2004, Barry Pederson wrote:
> Anyhow, I've found that using
>
> hosts_avoid_tls = *.psmtp.com
>
> in the remote_smtp transport seems to be doing the trick
Thanks for circulating this.
It appears that during the night-time we had a number of cases of "A
TLS packet with unexpected length was received" followed by "closed
connection in response to end of data" in our logs in relation to
hosts which matched *.psmtp.com; however, before I had got to applying
any kind of fix, the mail seems to have been transmitted successfully,
via the same relays that were previously (temp-)failing.
R=lookuphost T=remote_smtp H={*SNIP*}.s8a1.psmtp.com [64.18.7.10]
X=TLS-1.0:RSA_ARCFOUR_SHA:16
and so on.
Does this mean that they've sorted out the problem from their side,
and no further workaround is needed?
