add faq entry about configuring mox to send through a smart host

suggested by arnt & friend, thanks for reporting!
This commit is contained in:
Mechiel Lukkien 2024-03-27 10:23:37 +01:00
parent 6516a27689
commit 54b24931c9
No known key found for this signature in database
3 changed files with 20 additions and 2 deletions

View file

@ -429,6 +429,24 @@ the SMTP transaction that explains why. In the case of big email providers the
error message often has instructions on how to prove to them you are a error message often has instructions on how to prove to them you are a
legitimate sender. legitimate sender.
## Can mox deliver through a smarthost?
Yes, you can configure a "Transport" in mox.conf and configure "Routes" in
domains.conf to send some or all messages through the transport. A transport
can be an SMTP relay or authenticated submission, or making mox make outgoing
connections through a SOCKS proxy.
For an example, see https://www.xmox.nl/config/#hdr-example-transport. For
details about Transports and Routes, see
https://www.xmox.nl/config/#cfg-mox-conf-Transports and
https://www.xmox.nl/config/#cfg-domains-conf-Routes.
Remember to add the IP addresses of the transport to the SPF records of your
domains. Keep in mind some 3rd party submission servers may mishandle your
messages, for example by replacing your Message-Id header and thereby
invalidating your DKIM-signatures, or rejecting messages with more than one
DKIM-signature.
## Can I use existing TLS certificates/keys? ## Can I use existing TLS certificates/keys?
Yes. The quickstart command creates a config that uses ACME with Let's Encrypt, Yes. The quickstart command creates a config that uses ACME with Let's Encrypt,

View file

@ -1306,7 +1306,7 @@ examples with "mox example", and print a specific example with "mox example
# Example transport # Example transport
# Snippet for mox.conf, defining a transport called Example that connects on the # Snippet for mox.conf, defining a transport called Example that connects on the
# SMTP submission with TLS port 465 ("submissions), authenticating with # SMTP submission with TLS port 465 ("submissions"), authenticating with
# SCRAM-SHA-256-PLUS (other providers may not support SCRAM-SHA-256-PLUS, but they # SCRAM-SHA-256-PLUS (other providers may not support SCRAM-SHA-256-PLUS, but they
# typically do support the older CRAM-MD5).: # typically do support the older CRAM-MD5).:

View file

@ -135,7 +135,7 @@ WebHandlers:
"transport", "transport",
func() string { func() string {
const moxconf = `# Snippet for mox.conf, defining a transport called Example that connects on the const moxconf = `# Snippet for mox.conf, defining a transport called Example that connects on the
# SMTP submission with TLS port 465 ("submissions), authenticating with # SMTP submission with TLS port 465 ("submissions"), authenticating with
# SCRAM-SHA-256-PLUS (other providers may not support SCRAM-SHA-256-PLUS, but they # SCRAM-SHA-256-PLUS (other providers may not support SCRAM-SHA-256-PLUS, but they
# typically do support the older CRAM-MD5).: # typically do support the older CRAM-MD5).: