Does anyone know how to add a SPF record to sites, so I dont see this message when I do a DNS report.
Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
My domain, kiretsu.net, is hosted on my Iworx server. That server sends mail. Therefore, I add “a” to the SPF record. Additionally, the MX record points to mail.kiretsu.net, which is also allowed to send mail, so I add “mx” to the SPF record. Since NO OTHER HOST is allowed to send mail from @kiretsu.net, I add “~all” to the end of the record. Here’s how it looks in Interworx:
Add new record:
Host Type Target TTL
[kiretsu.net] [TXT] [v=spf1 a mx ~all] 
Tinydns is painfully confusing, and Interworx users don’t configure it directly, anyway, so the “instructions” on pobox aren’t very useful. Use the above example, just replace the target portion with the result you got (the part to the left of the [explain] button).
When a zombie computer at compuserve.net tries to send email from firstname.lastname@example.org to someone that checks SPF, they see that compuserve customers aren’t allowed to send mail from @kiretsu.net, and drop the forged mail before it is even delivered.
Iworx devs: any possibility of incorporating pobox’s SPF wizard into the CP?
I’m having a problem with this working correctly. I have a SPF record created as such in Nodeworx:
somedomain.com TXT v=spf1 a mx ~all 43200
Also in DNS:
mail.somedomain.com A 65.110.xx.xx 43200
mail2.somedomain.com A 66.23.xx.xx 43200
mail.somedomain.com MX 10 43200
mail2.somedomain.com MX 20 43200
mail.somedomain.com being the Interworx box, mail2 being a local exchange server (which really isn’t answering for the domain yet, but will).
Mail for that domain is being pulled via POP3 to the above mentioned local MSExchange server running GFIMailEssentials, which checks SPF records as a means of spam prevention. The local Exchange server does not answer for this particular domain (yet), but simply delivers that domain’s email to local accounts.
GFI for Exchange is marking any mail from this domain as spam via SPF. It doesn’t seem like it should, since the record (and what’s actually happening) seem correct.
Anyone have any thoughts on what to troubleshoot?
*** Edit *** I should be a bit more specific … it’s generating a “SoftFail,” not an absolute forgery – just a probable forgery.
I need some clarification on the SPF records. My server is hosting a number of domains, and from what I can tell they all send out mail on the same IP and the reverse DNS for that IP will point back to smtp.maindomain.com (for example). So, do I only need to add a TXT record for maindomain.com or will I need to add one for every domain on the server with the [v=spf1 a mx ~all] value?
I’m trying to do the same thing. I always get this from the SPF Test
Input accepted, querying now...
SPF records are primarily published in DNS as TXT records. The TXT
records found for your domain are:
"v=spf1 mx -all"
SPF records should also be published in DNS as type SPF records. This is new and
most implementations do not support it yet.
No type SPF records found.
Checking to see if there is a valid SPF record.
No valid SPF record found of either type TXT or type SPF.
When I’m on nodeworks do I enter the string with or without the quotes?
I’ve tried both and it still tells me it’s not finding a record on my server. The issue is I have an IPB Forum and e-mail is not working when I send bulk e-mail or to notifity users to reply notifications. I contacted my host and they said it could have something to do with not havbing SPF records setup and not having RDNS setup. But SPF doesn’t seem to want to setup.