ikkeben
Verified User
Read here why spf as directadmin does it now is maybe a to old way todo it?
While this document from August 30, 2017
For example:
In this howto and probably more.
While this document from August 30, 2017
For example:
Use of the “a” and “mx” directives§ The use of a and mx directives in SPF records is no longer recommended.
If the domain in question uses a third-party service to host mailboxes, then the service should provide an include directive for the SPF record. Similarly, most websites no longer send email directly from their web servers; they use an email service provider to deliver mail generated by web applications. Again, in this case the vendor should provide an include directive.
§Historically, many SPF generators created records that included a and mx directives by default. As above, these directives should be replaced by ip4/ip6 directives.
M3AAWG Best Practices for Managing SPF Records 6§a and mx directives count against the 10-DNS lookup limit, and can cause security holes when unintentional changes to DNS or compromise of servers lead to accidentally authorization of mail from unintended IPs.
In this howto and probably more.
Last edited: