mirror of
https://github.com/docker-mailserver/docker-mailserver.git
synced 2024-01-19 02:48:50 +00:00
Updated A mail server's 101 (markdown)
This commit is contained in:
parent
c57122514e
commit
51e497b848
|
@ -125,7 +125,7 @@ My MTA will thus have to support two kinds of Submission:
|
|||
┌────────────────────┐ ┌┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┐
|
||||
Me ---------------> ┤ ├ -----------------> ┊ ┊
|
||||
│ My MTA │ ┊ Third-party MTA ┊
|
||||
Me <--------------- ┤ ├ <----------------- ┊ ┊
|
||||
│ ├ <----------------- ┊ ┊
|
||||
└────────────────────┘ └┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┘
|
||||
┗━━━━━━━━━━ Inward Submission ━━━━━━━━━━┛
|
||||
```
|
||||
|
@ -162,6 +162,18 @@ Granted it's still very difficult enforcing encryption between MTAs (Transfer/Re
|
|||
- It does not enable Explicit TLS (STARTTLS) on port 25 by default. One may enable it through advanced custom configuration, either as a replacement (bad!) or as a supplementary mean of secure Inward Submission.
|
||||
- One may also secure Inward Submission using advanced encryption scheme, such as DANE/DNSSEC and/or MTA-STS.
|
||||
|
||||
Overall, `docker-mailserver`'s default configuration for SMTP looks like this:
|
||||
|
||||
```txt
|
||||
┏━━━━ Outward Submission ━━━━┓
|
||||
┌────────────────────┐ ┌┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┐
|
||||
Me -- cleartext --> ┤(25) (25)├ --- cleartext ---> ┊ ┊
|
||||
Me -- STARTTLS ---> ┤(587) My MTA │ ┊ Third-party MTA ┊
|
||||
│ (25)├ <---cleartext ---- ┊ ┊
|
||||
└────────────────────┘ └┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┘
|
||||
┗━━━━━━━━━━ Inward Submission ━━━━━━━━━━┛
|
||||
```
|
||||
|
||||
### Retrieval - IMAP
|
||||
|
||||
A MUA willing to fetch an email from a mail server will most likely communicate with its [IMAP](https://en.wikipedia.org/wiki/IMAP) server. As with SMTP described earlier, communication will take place in the form of data packets exchanged over a network that both the client and the server are connected to. The IMAP protocol makes the server capable of handling _Retrieval_.
|
||||
|
|
Loading…
Reference in a new issue