This release fixes TLS interoperability with incoming deliveries from Microsoft
servers by disabling TLS session tickets. If you have MTA-STS and/or DANE
enabled, TLS is required for successful delivery, and updating to v0.0.13 is
required to receive messages from Microsoft again. TLS session tickets may be
enabled again in a future release, possibly per port/service.
Improvements
- In the IMAP server, for the "bodystructure" response item to a "FETCH"
command, add the content-type parameters for multiparts so IMAP clients will
get the MIME boundary without having to parse the message themselves. (issue
#217, 8fa197b) - Add an HTTP handler for the acme http-01 validiation mechanism to all plain
http (non-tls) webservers (ports), not only to the one listening on port 80.
(#issue 218, 0fbf241) - Properly link to matrix room so users can find it. (issue #226, 76f7b9e)
Bug fixes
- Disable session tickets for tls to workaround deliverability issues with
incoming email from Microsoft over smtp with starttls. Without this fix,
email from Microsoft is no long coming in. (issue #237, 22c8911) - In the SMTP server, when logging about problems with recipients, actually
show which recipients were present in the session. (issue #232,
598c5ea). - Webmail: During "send and archive", don't fail with error message when
message that is being responded to is already in archive folder. (issue #233,
879477a) - Webmail: if we don't have loaded account settings yet, abort loading the
popup after showing an error that the settings aren't available yet. (issue
#218, 0430572)
Update instructions
Before upgrading, do a dry-run first.
- Make a temporary backup with the old mox version:
mox-v0.0.12 backup data/tmp/testupgrade - Verify that all is well with the old version:
mox-v0.0.12 verifydata data/tmp/testupgrade - Verify the state with the new version:
mox-v0.0.13 verifydata data/tmp/testupgrade
With a successful dry-run, the upgrade should go smoothly. Make a new backup
with mox-v0.0.12 backup data/tmp/backup (the previous backup was modified by
the dry-run, so couldn't be used to restore!), replace the binary and restart.
For further details, see
https://www.xmox.nl/faq/#hdr-how-do-i-upgrade-my-mox-installation
If you run into any problems, please create a bug report.
Thanks
Thanks for all the contributions/bug reports/feedback/discussions, much
appreciated! Special thanks to mdavids, danieleggert, startup-001-steve,
snabb, mattfbacon, mgkirs, exander77.
Development on mox is funded through the NLnet NGI0 Entrust Fund,
https://nlnet.nl/entrust/, with financial support from the European
Commission's Next Generation Internet programme.