On 2/27/2018 8:29 PM, J Doe wrote: > Hello, > > I read the “Postfix ETRN Howto” [1] as well as man 5 postconf with regards to: > > postscreen_discard_ehlo_keywords > smtpd_discard_ehlo_keywords > > ... and disabled the announcement of ETRN via: > > postscreen_discard_ehlo_keywords = ETRN > smtpd_discard_ehlo_keywords = ETRN > > I then restarted the server and observed an inbound connection from Gmail: > > Feb 27 21:12:19 server postfix/smtpd[2369]: connect from > mail-oi0-x22f.google.com > Feb 27 21:12:19 server postfix/smtpd[2369]: discarding EHLO keywords: ETRN > Feb 27 21:12:19 server postfix/smtpd[2369]: Trusted TLS connection > established ... > Feb 27 21:12:19 server postfix/smtpd[2369]: discarding EHLO keywords: ETRN > > My question is: > > ** Is the Gmail SMTP server attempting to use ETRN on the first, unencrypted > SMTP session with my server and then attempting to request it again after > STARTTLS when the TLS connection is established and this is why it is logging > that it is discarding ETRN each time or ...
Not this. > > ** Is Postfix logging that ETRN is disabled on the first, unencrypted SMTP > session and then logging this again for the encrypted session (ie: Postfix is > just logging I disabled this and Google is not attempting to issue ETRN each > time) ? Yes, this. The informative message is logged as soon as the client sends EHLO, and before the client sends any other commands. Now that you know it's working, you can use the silent_discard keyword to clean up the logs. -- Noel Jones
