|
By following http://docs.webfaction.com/user-guide/email.html I added a TXT record (SPF) v=spf1 a:smtp.webfaction.com ~all to my DNS records with my external registrar. But messages sent through smtp.webfaction.com using the example Perl script still end up in Spam due to Softfail of spf check. OK. So I added the same record to my domain in Webfaction control panel (I think this is useless). No change. OK. So I changed the spf record to include just "webfaction.com". No change. The SPF checking tool http://tools.bevhost.com/spf/ tells me that the SPF record is set correctly but it indicated problems with IP address of the mail server: I don't know if that means something. I did wait until the DNS records got propagated. What do I do wrong? asked 18 Jun '13, 02:07 futu |
|
We brought 74.55.86.75 up as a temporary workaround for some blacklisting issues that we're presently working to resolve. We're almost out of that situation, and when it is, we'll switch back to 74.55.86.74 (the original IP), and the SPF example in our docs will work again. Your solution to use ip4 modifiers in the records was the correct workaround. answered 18 Jun '13, 17:54 seanf |
|
I have followed the steps on this page to configure my WebFaction hosted domain SPF record: The page recommends using the following SPF record: Unfortunately, I have noticed that Gmail tags e-mail from my domain as softfail: 75.126.24.68 is in fact mail8.webfaction.com which is not covered by the a:smtp.webfaction.com directive of the WebFaction recommended SPF record. Suggestion: Instead of having us hardcode ever-changing server IP addresses in all of our domains, would it be possible for WebFaction to provide us with the INCLUDE directive, like Gmail or Office365 hosting do? For example: Which means: fetch all of the SPF records from that domain and include them in this domain. WebFaction would then need to maintain the SPF record at one place, on their domain, with their mail servers IP addresses and we would be instantly covered by any changes they need to make to their mail infrastructure. To make sure this change doesn't interrupt/overlap with their own SPF records, WebFaction could use another domain to "host" the SPF records, like spfcustomers.webfaction.com. Thank you for considering this! Jimmy. answered 26 Mar '15, 12:37 JPrince Thanks for the suggestion! We're actually already working on providing a consolidated SPF endpoint, but we do not have an ETA for it at this time.
(26 Mar '15, 16:23)
seanf
Great news! In the meantime, can you provide all the IP addresses we should put in the a: directives in our SPF records? Thank you!
(26 Mar '15, 16:45)
JPrince
If you're only using our SMTP, then smtp.webfaction.com is sufficient. If you're using forwarding addresses, then you should include the following hosts as well:
(26 Mar '15, 17:04)
seanf
|
I managed to get spf=pass by setting the SPF records to:
v=spf1 ip4:74.55.86.75 ip4:74.55.86.74 ~all