mox/http
Mechiel Lukkien 8096441f67
new feature: when delivering messages from the queue, make it possible to use a "transport"
the default transport is still just "direct delivery", where we connect to the
destination domain's MX servers.

other transports are:

- regular smtp without authentication, this is relaying to a smarthost.
- submission with authentication, e.g. to a third party email sending service.
- direct delivery, but with with connections going through a socks proxy. this
  can be helpful if your ip is blocked, you need to get email out, and you have
  another IP that isn't blocked.

keep in mind that for all of the above, appropriate SPF/DKIM settings have to
be configured. the "dnscheck" for a domain does a check for any SOCKS IP in the
SPF record. SPF for smtp/submission (ranges? includes?) and any DKIM
requirements cannot really be checked.

which transport is used can be configured through routes. routes can be set on
an account, a domain, or globally. the routes are evaluated in that order, with
the first match selecting the transport. these routes are evaluated for each
delivery attempt. common selection criteria are recipient domain and sender
domain, but also which delivery attempt this is. you could configured mox to
attempt sending through a 3rd party from the 4th attempt onwards.

routes and transports are optional. if no route matches, or an empty/zero
transport is selected, normal direct delivery is done.

we could already "submit" emails with 3rd party accounts with "sendmail". but
we now support more SASL authentication mechanisms with SMTP (not only PLAIN,
but also SCRAM-SHA-256, SCRAM-SHA-1 and CRAM-MD5), which sendmail now also
supports. sendmail will use the most secure mechanism supported by the server,
or the explicitly configured mechanism.

for issue #36 by dmikushin. also based on earlier discussion on hackernews.
2023-06-16 18:57:05 +02:00
..
account.go log a consistent log line for failed authentication attempts, with the remote ip 2023-05-31 20:39:00 +02:00
account.html the mbox export also contains all message flags, so fix the text along the export links 2023-03-29 21:21:43 +02:00
account_test.go unbreak the subcommands that talk to the mox instance of the ctl socket 2023-06-16 13:27:27 +02:00
accountapi.json make http(s) path for serving the account and admin pages configurable 2023-03-12 11:52:15 +01:00
admin.go new feature: when delivering messages from the queue, make it possible to use a "transport" 2023-06-16 18:57:05 +02:00
admin.html new feature: when delivering messages from the queue, make it possible to use a "transport" 2023-06-16 18:57:05 +02:00
admin_test.go change mox to start as root, bind to network sockets, then drop to regular unprivileged mox user 2023-02-27 12:19:55 +01:00
adminapi.json new feature: when delivering messages from the queue, make it possible to use a "transport" 2023-06-16 18:57:05 +02:00
autoconf.go make it easier to run with existing webserver 2023-03-04 00:49:02 +01:00
autoconf_test.go mox! 2023-01-30 14:27:06 +01:00
import.go update to latest bstore (with support for an index on a []string: Message.DKIMDomains), and cyclic data types (to be used for Message.Part soon); also adds a context.Context to database operations. 2023-05-22 14:40:36 +02:00
mtasts.go add basic webserver that can do most of what i need 2023-02-28 22:19:24 +01:00
mtasts_test.go mox! 2023-01-30 14:27:06 +01:00
web.go add reverse proxying websocket connections 2023-05-30 22:11:31 +02:00
web_test.go unbreak the subcommands that talk to the mox instance of the ctl socket 2023-06-16 13:27:27 +02:00
webserver.go add reverse proxying websocket connections 2023-05-30 22:11:31 +02:00
webserver_test.go unbreak the subcommands that talk to the mox instance of the ctl socket 2023-06-16 13:27:27 +02:00