@@ -55,12 +55,34 @@ cannot be lower than 4s. The special value 0 disabled RPC timeout checking.
5555Default: \fI 0 \fP
5656.TP
5757\fB outgoing_smtp_url \fP
58- The SMTP server to use for outgoing mails. To use the local maildrop queue, set
59- the value to \fI sendmail://localhost \fP . smtp:// is unqueued(!), and if the
60- SMTP server is offline, submissions will be rejected (and mails stick around in
61- Outbox or whatever folder they were submitted from). For STARTTLS, use
62- smtp+tls://, and for ignoring TLS certificate validation,
63- smtp+unverifiedtls://.
58+ A string which selects how outgoing messages are handed to a mail transfer
59+ agent. The syntax follows the Common Internet Scheme for URIs (RFC 1738 section
60+ 3.1), so something like "sendmail://localhost" or "smtp://[::1]:25/" can be
61+ used.
62+ .br
63+ The sendmail:// transport selects the local maildrop queue (hostname is
64+ ignored). Maildrop is perhaps best known to administrators by the command
65+ /usr/sbin/sendmail. This transport is the most robust one, because local
66+ maildrop implementations generally accept messages even if the MTA is not
67+ running (assuming everything else is fine, e.g. there is enough free disk
68+ space). Partial Delivery Failure handling then is also the MTA's
69+ responsibility, and the MTA will consistently emit NDR/DSN for unreachable
70+ recipients.
71+ .br
72+ Other recognized schemes are smtp:, smtp+tls: (STARTTLS), smtp+unverifiedtls:
73+ (STARTTLS but ignore validation issues) and smtps: (always-on/implicit TLS).
74+ These are only meant for developers who want to avoid running an MTA for having
75+ faster turnarounds. All SMTP transport drivers are \fB locally unqueued \fP ,
76+ which means that, if the SMTP server is unavailable due to network issues,
77+ pressing the "Send" button will immediately produce an error in always-online
78+ MUAs, and the user has to save the message as a draft and try again later on
79+ their own accord. MAPI also has no way to be conveyed Partial Delivery Failure
80+ occuring in SMTP conversations, so a multi-recipient message with one bad
81+ recipient can lead to three bad characteristics all at once: valid recipients
82+ will receive a message copy; the sender got the Send button error; no
83+ Non-Delivery Report is generated for users in the local mail system. The proper
84+ way to use a custom outgoing SMTP server is to configre the localhost MTA to
85+ perform relaying.
6486.br
6587Default: \fI sendmail://localhost \fP
6688.TP
0 commit comments