After reading on dnsreport.com that one was suppose to add Sender Policy Framework to ones DNS zone before October 1st, I decided to add it to my two domains tsn.dk and dreamcoder.dk. I registered both in The SPF Registry.
I have to admit it’s a bit scary to add something which could potentially kill mails you send to someone. I followed the guide, however I am still in doubt as to my setup being correct, I don’t think the guide explains it very well what the policy means in different circumstances, or maybe it’s just me.
My SPF looks like so: v=spf1 a mx ptr ~all, I added the ~all because that will cause mails to soft bounce, I am such a chicken :)
In any case you can bet your ass SPF won’t become mainstream before Postfix supports it natively (as far as I know, it doesn’t atm.). Right now it’s just a stupid perl plugin and I am under no circumstances going to put that into my Postfix installations.
eCarlos
September 22, 2004 at 13:05
Read a really easy to understand guide at GratisDNS’s forum.
http://forum.gratisdns.dk/viewtopic.php?t=4401
plumsauce
September 23, 2004 at 07:18
I suggest that you ignore SPF because of the business agenda behind the certification process. Look to the model of SSL certs. Self signed certs are unacceptable for general use. Once SPF gains momentum, the push will come for commercial certification at a cost to be determined.
DNS Watch
July 25, 2005 at 10:30
Is SPF not that very framework that Microsoft claims patent rights on? :( If this is true, I’d better not add any SPF records to my domains…