On Wed, May 13, 2015 at 01:27:44PM +0200, Eric Ripa wrote: > Okay. So I've looked further into this, the destination MX record contains 6 > addresses. The first 5 generates the below TLS IO Error, but the 6th doesn't > seem to be up to respond on SMTP queries. So what I believe is happening is > that OpenSMTPD retries all alternative MX records when TLS is failing on the > first ones.. but then the last isn't up so it lingers with 'Network error on > destination MXs' > > Any input on how to do a workaround? Is it possible to force non-tls on > certain destinations or change the fallback algorithm? >
I'll have a look today -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
