问题原文
原帖链接 · comfreak · CC BY-SA 3.0
I am running an email server which is currently set up to use TLS if possible, when sending and receiving emails.
When you read in the documentation about this, there is also the option to enforce TLS and not accept plain text transmission of emails. It also warns you that some mail servers might not support encryption yet and enforcing encryption could block these servers.
But is this still an issue one should think about or is it safe to say that enforcing encryption won't be a problem anymore?
Is there possibly some big provider who is already doing this or what do you consider best practice these days?
社区高分解答
原帖链接 · Ángel · CC BY-SA 3.0
No
RFC 821 is 33 years old. You will find emails relayed by programs notsupporting STARTTLS. Sometimes they will be stub email senders (eg. internal scripts), sometimes full fledged systems that are old, have TLS disabled/not compiled in, systems without enough entropy…
I witnessed not so long ago outbound emails failing because the receiving end had it configured to only allow SMTP over TLS. It was a problem in the sender (it shouldn't had been using that configuration), but shows that it does happen.
I would only restrict incoming messages from manually configured IP addresses. If your credit card processor fails to start STARTTLS, you probably prefer to abort the connection (and page the local admin so he can warn them!) rathen than receive that (potentially sensitive) data unencrypted. For outbound messages, if you connected to that host using STARTTLS previously, you may want not to do that insecurely again, treating it as a potential compromise instead. You may also have a list of known-to-always-use-STARTTLS hosts, such as gmail or yahoo.
There's https://www.eff.org/starttls-everywhere project providing a list of smtp servers for which you can (should?) confidently enforce starttls usage.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
