4 ms·

I'm very happy to see this as I have been advocating for something like this for quite a while: a single setup and configuration that handles SPF, DKIM, DMARC

by rsync 2y ago

I'm very happy to see this as I have been advocating for something like this for quite a while: a single setup and configuration that handles SPF, DKIM, DMARC all together. I understand, and appreciate, the modular philosophy behind OpenSMTPD, etc., but in practice it is quite frustrating and difficult to piece it all together - especially if you add rspamd, etc. Speaking of which, how is spam handled ? I see this in the FAQ: "Mox does spam filtering based on reputation of received messages." ... but it is not further elaborated. Also: I assume that the web service can be fully disabled and Mox can be run with no httpd but that is also not specifically called out ... can it ?

mjl- 2y ago
There is some more information about spam filtering at the features page: https://www.xmox.nl/features/#hdr-junk-filtering https://www.xmox.nl/features/#hdr-junk-filtering I'm very happy with how the filtering works for me. Most email gets classified because of being a known sender. The first-time senders will go through the bayesian classifier, which keeps most spam out. For me, 1 spam message gets through every 2 days. If ham is incorrectly rejected as spam, the sender will hear about it, because mox will keep soft-rejecting the email, eventually resulting in a bounce. > I assume that the web service can be fully disabled and Mox can be run with no httpd but that is also not specifically called out ... can it ? You can run without the web interfaces. I think you can set it up without a public web server, but the admin interfaces are pretty convenient (though still spartan!), you could keep those internal. The webserver is needed for ACME, for MTA-STS, and for autoconfig. Btw, mox can also serve static files and do reverse proxying. The mox website is hosted by mox. I added webserver functionality (relatively tiny functionality/code compared with the email code!) so people wouldn't have to run another webserver, which greatly complicates the setup (with reverse proxying).

by rsync 2y ago

mjl- 2y ago

There is some more information about spam filtering at the features page: https://www.xmox.nl/features/#hdr-junk-filtering https://www.xmox.nl/features/#hdr-junk-filtering I'm very happy with how the filtering works for me. Most email gets classified because of being a known sender. The first-time senders will go through the bayesian classifier, which keeps most spam out. For me, 1 spam message gets through every 2 days. If ham is incorrectly rejected as spam, the sender will hear about it, because mox will keep soft-rejecting the email, eventually resulting in a bounce. > I assume that the web service can be fully disabled and Mox can be run with no httpd but that is also not specifically called out ... can it ? You can run without the web interfaces. I think you can set it up without a public web server, but the admin interfaces are pretty convenient (though still spartan!), you could keep those internal. The webserver is needed for ACME, for MTA-STS, and for autoconfig. Btw, mox can also serve static files and do reverse proxying. The mox website is hosted by mox. I added webserver functionality (relatively tiny functionality/code compared with the email code!) so people wouldn't have to run another webserver, which greatly complicates the setup (with reverse proxying).