3 ms·
The link to part 3 from part 2 is broken (but the one in ToC works). It doesn't mention reverse DNS (PTR for *.in-addr.arpa) records. Though not strictly neces
by defanor 4y ago
The link to part 3 from part 2 is broken (but the one in ToC works).
It doesn't mention reverse DNS (PTR for *.in-addr.arpa) records. Though not strictly necessary, but doesn't harm to have those set, and the author's mail server has those set.
Looks nice overall. The notable differences from how I set those are the lack of postscreen (including its greylisting), of a dedicated submission port, of SRV DNS records (_submission._tcp, _imap._tcp, _imaps._tcp), but presence/use of virtual hosts and users, and of OpenDMARC. Maybe I should try using the latter, though not sure how useful it is (whether it's worth the slight complication of the overall setup), when set on a small/low-traffic mail server.
- merpkz 4y agowhy do you need SRV records for submission,imap and imaps? Are there email clients who make use of those?
- defanor 4y agoNot sure about the support in mail clients (I mostly use mu4e with mbsync, I don't think they can look those up), and they certainly aren't required. But I set them anyway, along those for XMPP (where they should be set), and it's potentially useful. Similarly to setting TLSA, SSHFP, CAA records: those are rarely used, but they do seem nice to me, and it shouldn't harm to provide clients with such an option. Also the more servers provide it, the more motivation there is for clients to support it.
- bandie91 4y agowhy do you need to develop SRV record support in email clients? are there email providers who publish SRV records? it's like why do servers/clients need to support IPv6 if there are few clients/servers doing it :)