3 ms·

Was Gmail actively sending emails with this? Or just not blocking emails from other servers using it? Breaking email deliverability is a pretty serious action t

• behringer 1y ago
  The broken systems would have repaired their systems 8 years ago when users complained.
• deleted 1y ago
  [deleted]
• jeroenhd 1y ago
  With Gmail's spam filter being the way it is, email deliverability issues because of 3DES are probably invisible next to the normal email being silently discarded. Users trying to send email to an outgoing SMTP server that hasn't been maintained this decade may see a warning, but I doubt there are still that many broken server out there that can't be replaced or updated on short notice once the domain admin gets told Gmail can't reach them.
• tialaramex 1y ago
  The latter. What we're talking about here is a TLS negotiation. So, when you connect to a TLS server, in this case to deliver email to Gmail over SMTP - you tell it what ciphers you know [the RFCs list "Mandatory to implement" ciphers, but the IETF do not have an enforcement arm, so you could choose to list only ciphers you made up here for whatever that's worth] - and then the server picks one from your list. Google's change here is when a client calls Gmail and professes that the least awful cipher it knows is 3DES, that's too bad, connection failed. So yes, this only affects email which was previously using this awful cipher and now just can't be delivered instead.