On Mon, Jan 07, 2019 at 09:18:03AM +0000, John Cox wrote: > Hi > > >> Jan 6 14:35:05 azathoth smtpd[87479]: 92975635cb3d86a4 mta connecting > >> address=smtp://212.54.58.11:25 host=mx.mnd.ukmail.iss.as9143.net > >> Jan 6 14:35:05 azathoth smtpd[87479]: 92975635cb3d86a4 mta connected > >> Jan 6 14:35:05 azathoth smtpd[87479]: 92975635cb3d86a4 mta starttls > >> ciphers=version=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256 > >> Jan 6 14:35:05 azathoth smtpd[87479]: smtp-out: Server certificate > >> verification succeeded on session 92975635cb3d86a4 > >> Jan 6 14:35:05 azathoth smtpd[87479]: 92975635cb3d86a4 mta delivery > >> evpid=00fe7e3a0bda75cf from=<[email protected]> > >> to=<[email protected]> rcpt=<[email protected]> > >> source="46.235.226.138" relay="212.54.58.11 > >> (mx.mnd.ukmail.iss.as9143.net)" delay=1s result="Ok" stat="250 2.0.0 > >> MXIN650 mail accepted for delivery > >> ;id=g9W5guLw5a6xRg9W5gmZtD;sid=g9W5guLw5a6xR;mta=mx4.mnd;d=20190106;t=153505[CET];ipsrc=46.235.226.138;" > >> Jan 6 14:35:16 azathoth smtpd[87479]: smtp-out: Error on session > >> 92975635cb3d86a4: opportunistic TLS failed, downgrading to plain > >> Jan 6 14:35:16 azathoth smtpd[87479]: 92975635cb3d86a4 mta connecting > >> address=smtp+notls://212.54.58.11:25 host=mx.mnd.ukmail.iss.as9143.net > >> Jan 6 14:35:16 azathoth smtpd[87479]: 92975635cb3d86a4 mta connected > >> Jan 6 14:35:16 azathoth smtpd[87479]: 92975635cb3d86a4 mta > >> disconnected reason=quit messages=1 > >> > >> Where I seems to succeed with tls and then it says that it has failed. > >> What is going on? > > I know I put 2 questions in one message but does anyone have any idea > why I seem to both get a TLS success & a TLS failure here? >
you don't get both a TLS success and a TLS failure here, you only have a single MTA session: 92975635cb3d86a4 what happens is that session established a connection then attempted TLS negotiation. this worked fine, the MTA session played out until it hit a TLS error that caused it to drop connection. TLS was opportunistic so it connected again but without TLS. The only "issue" in this log is that there was no need to reconnect, the TLS error happened _after_ message was accepted and there was no message pending delivery after this one. The MTA is being reworked and this bug has no bad side-effect so we will not fix, just ensure the new MTA code doesn't do that same. -- Gilles Chehade @poolpOrg https://www.poolp.org tip me: https://paypal.me/poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
