From 6cb1a0b76841d3f7bcddb697fdd07927d84304b4 Mon Sep 17 00:00:00 2001 From: Jean-Denis Vauguet Date: Fri, 12 Jun 2020 06:28:27 +0200 Subject: [PATCH] Updated A mail server's 101 (markdown) --- docs/content/a-mail-server's-101.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/a-mail-server's-101.md b/docs/content/a-mail-server's-101.md index 254ffc9c..d174027c 100644 --- a/docs/content/a-mail-server's-101.md +++ b/docs/content/a-mail-server's-101.md @@ -158,8 +158,8 @@ One may then customize all aspects of its internal components. On the subject of security, one might consider docker-mailserver's **default** configuration to _not_ be 100% secure: -- it enables unencrypted trafic on port 25 for Transfer/Relay (between MTAs for MX service) -- it enables Explicit TLS (STARTTLS) on port 587 for SMTP, instead of Implicit TLS on port 465 +- it enables unencrypted trafic on port 25 +- it enables Explicit TLS (STARTTLS) on port 587, instead of Implicit TLS on port 465 We believe docker-mailserver's default configuration to be a good middle ground: it goes slightly beyond "old" (1999) [RFC 2487](https://tools.ietf.org/html/rfc2487); and with developper-friendly configuration settings, it makes it pretty easy to abide by the "newest" (2018) [RFC 8314](https://tools.ietf.org/html/rfc8314).