The first mail that I sent to one of our mailing lists with my new e-mail account, bounced with: Reporting-MTA: dns; outbound.soverin.net X-Postfix-Queue-ID: D30316020C X-Postfix-Sender: rfc822; marja11@xxxxxxx.nl Arrival-Date: Fri, 1 Oct 2021 19:56:12 +0000 (UTC) Final-Recipient: rfc822; discuss@ml.mageia.org Original-Recipient: rfc822;discuss@ml.mageia.org Action: failed Status: 5.7.4 Diagnostic-Code: X-Postfix; TLS is required, but was not offered by host neru.mageia.org[163.172.148.228] I already turned that requirement off for my new mail account. However, filing this enhancement request anyway, because it would be nice to have and because likely more e-mail providers will start requiring this by default.
commit ef8883f73a36ead4c26a42b413baa913c008cfa6 Author: Dan Fandrich <danf@...> Date: Fri Feb 9 00:53:52 2024 -0800 Create a self-signed certificate for incoming mail (mga#29514) This still needs to be enabled once it's checked. --- Commit Link: https://gitweb.mageia.org/infrastructure/puppet/commit/?id=ef8883f73a36ead4c26a42b413baa913c008cfa6
commit f64014e2a3c2431211dda1f6bf9f28eaf56c4536 Author: Dan Fandrich <danf@...> Date: Fri Feb 9 10:36:06 2024 -0800 Enable opportunistic TLS when receiving mail (mga#29514) --- Commit Link: https://gitweb.mageia.org/infrastructure/puppet/commit/?id=f64014e2a3c2431211dda1f6bf9f28eaf56c4536
This is now done. All mails to and from Mageia mail servers now have opportunistic TLS available. The certificate used for incoming mail is self-signed, but that doesn't seem to be an issue in the current Internet.
CC: (none) => danStatus: NEW => RESOLVEDResolution: (none) => FIXED
Thanks, Dan :-)