2 ms·
A header would probably be more appropriate. Then any client could display it differently. The problem is that your mail server can only tell that the last leg
by cm2187 11y ago
A header would probably be more appropriate. Then any client could display it differently. The problem is that your mail server can only tell that the last leg of the connection was encrypted, not that all connections from the sender's client were all encrypted.
- slasaus 11y agoBut isn't it that in practice most of the time this "last leg" is the only leg that crosses the internet? Most of the servers I see in the mail headers I receive are servers in the internal network of the sender. So IMHO transport encryption still is of real significance against passive attacks.
- cm2187 11y agoActually the first leg (sender client to sender smtp server) is probably the most at risk of a mitm, as it often goes over wifi.
- teekert 11y agohttp://techcrunch.com/2015/11/12/gmail-will-soon-warn-users-when-emails-arrive-over-unencrypted-connections/ http://techcrunch.com/2015/11/12/gmail-will-soon-warn-users-... :)