Submitted by aitte on Tue, 02/26/2013 - 19:44
The SPF standard says that there must be a TXT record and may be a SPF record.
Virtualmin only inserts the TXT record.
All modern implementations first look for an SPF record and if that's missing they look for a TXT record. Give it a few more years and they will only be looking for the SPF record.
You can cut out a useless query by adding both SPF and TXT records, with identical contents.
This doesn't affect me as I use a custom DNS template but I thought I'd report it anyway.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Tue, 02/26/2013 - 21:07 Comment #1
Another user reported this recently as well. The trouble with creating an SPF record by default is that some BIND versions may not support it, and determining which versions do or do not is tricky. Also, it will take a long time before the majority of clients that support SPF know to check SPF records as well ... and potentially forever until clients stop checking TXT records.
So my plan is to delay making any changes here until the SPF record type becomes more common.
Submitted by aitte on Tue, 02/26/2013 - 22:47 Comment #2
Yeah I am aware that very early BIND versions lack SPF support, but it's easy to determine. BIND 9.4 and up supports it. That was released in Feb 2007. Version can be checked via the system's package manager info or with "named -v".
Submitted by JamieCameron on Tue, 02/26/2013 - 23:02 Comment #3
I'll look into creating an SPF record and keeping these in sync, but I consider it pretty low priority as the TXT record is going to be supported for a long time.
Submitted by aitte on Tue, 02/26/2013 - 23:11 Comment #4
Very low priority, absolutely. :)
Submitted by JamieCameron on Thu, 02/28/2013 - 00:01 Comment #5
Since this turned out to be pretty easy, the next Webmin release will allow you to choose whether to create SPF or TXT records for Sender Permitted From information.
And if SPF is selected, Virtualmin will create both SPF and TXT records, and keep them in sync.
Submitted by aitte on Thu, 02/28/2013 - 01:32 Comment #6
Very nice!
Submitted by Issues on Thu, 03/14/2013 - 02:46 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.