Am 11.10.19 um 18:10 schrieb Viktor Dukhovni:
> So likely at this point it is safe to conclude that sending SNI is
> unlikely to cause problems. Your mileage may vary.
Hi,
that Gmail enabled SNI on their SMTP client is an indicator that using SNI may
not cause relevant trouble.
But it's also known, Gmail is able to do such stuff very selective to prevent
damage.
In theory, an SMTP client, postfix smtp for example, could always try to
connect to a remote destination
using SNI, log success or failure and fallback to reconnect without SNI.
That would enable users to gather their own statistics.
reading http://www.postfix.org/postconf.5.html#smtp_tls_servername give me the
impression one
could set "smtp_tls_servername = hostname". That would force the SMTP client to
always send SNI.
The admin can monitor the log for additional delivery failures and gather
statistics.
Right?
Andreas
