Received-SPF: softfail

[hotshot]

Now this SPF stuff is a real headache, I hate it, is there a way to remove this? Or to solve my problem, I want to accept it that any IP in the world is allowed to send e-mails with my domains as their from e-mail address. So someone overhere explained me that this is standard with DA since they're using the ~all record.


Well when i receive e-mails from my server on my gmail address or when I send an e-mail thru the pop3 of my XS ISP with one of my domains as the from e-mail address than I will see something like this:

Received-SPF: softfail (gmail.com: domain of transitioning [email protected] does not designate 194.134.35.149 as permitted sender)


And i want ti to be a pass, I want to allow this, any IP as a Sender ID of my from domains.

-----
-----

Someone else's server:

And this is what you'll see when there is no SPF record:
Received-SPF: none

And this when there is an SPF record that matches the IP or if it's: ~all
Received-SPF: pass (gmail.com: domain of [email protected] designates 213.244.179.42 as permitted sender)
--> And this is what I want to see in gmail when I receive some e-mail from my server.



Now I'm running one domain on one static IP, but I'm running the DNS for a couple of more domains and they're all pointing to the same static IP of the main domain, they're all having this problem, even the main domain. The website is hosted on IP: 160 but I see IP: 157 back in gmail.


Now there has also been a recent update if the SPF stuff inside DA, but this update didn't change a bling:
http://www.directadmin.com/features.php?id=431

I've tried it with adding some new domains to the DNS and pointing to the same static IP after this update, but no it's still the same.


Now my question is, what's the problem and what can we do about it?



Thanks,
Michel,

 

[nobaloney]

Well when i receive e-mails from my server on my gmail address or when I send an e-mail thru the pop3 of my XS ISP with one of my domains as the from e-mail address than I will see something like this:

Received-SPF: softfail (gmail.com: domain of transitioning [email protected] does not designate 194.134.35.149 as permitted sender)

There isn't any SPF record for tenshap.biz. This is the command that checks it:

dig tenshap.biz txt

And i want ti to be a pass, I want to allow this, any IP as a Sender ID of my from domains.

~all is the proper setting to allow any IP to send email from your domain. Unfortunately many email hosts don't allow it.

Someone else's server:

And this is what you'll see when there is no SPF record:
Received-SPF: none

And this when there is an SPF record that matches the IP or if it's: ~all
Received-SPF: pass (gmail.com: domain of [email protected] designates 213.244.179.42 as permitted sender)
--> And this is what I want to see in gmail when I receive some e-mail from my server.

And it's what you should see if the dig command as above returns a record.

Now I'm running one domain on one static IP, but I'm running the DNS for a couple of more domains and they're all pointing to the same static IP of the main domain, they're all having this problem, even the main domain. The website is hosted on IP: 160 but I see IP: 157 back in gmail.

All email from your box will be sent from the main server IP#. And if you're going to have an IP# in your SPF record it should be the server's main IP#.

I've tried it with adding some new domains to the DNS and pointing to the same static IP after this update, but no it's still the same.

Have you checked to make sure your server is properly creating the SPF records. Based on your example it looks as if it isn't.

Now my question is, what's the problem and what can we do about it?

1) make sure your DA server is creating SPF records when it creates the domain.

2)Make sure all your domians have SPF records as defined not by the DA temporary fix (which was designated by me) but rather by hand creating an SPF record according to the wizard you can find here.

3) pray that everyone who's pushing SPF, and especially failures based on SPF records, get some clue.

Jeff

 

[hotshot]

Re: Re: Received-SPF: softfail

~all is the proper setting to allow any IP to send email from your domain. Unfortunately many email hosts don't allow it.

3) pray that everyone who's pushing SPF, and especially failures based on SPF records, get some clue.

Jeff

I hate SPF

 

[nobaloney]

Having studied it, so do I.

I'll be in Santa Clara, Calif., November 3 - 5 for the ISP.CON show.

Maybe there's going to be a forum on the subject.

Jeff

 

[hotshot]

I checked the headers of some e-mails from PayPal to my Gmail and this is what I saw:

PayPal:
Received-SPF: neutral (gmail.com: 64.74.96.246 is neither permitted nor denied by domain of [email protected])

So that's what I need to see in the headers of my e-mails sent by my server, cause this is what we need to see with the ~all txt record, and I don't )-;

I'm getting something like this:
Received-SPF: softfail (gmail.com: domain of transitioning [email protected] does not designate 194.134.35.149 as permitted sender)

And this aint it either; Received-SPF: none, this will just mean that there is NO SPF record available.

So the ~all txt record implemented by DA is not working here.

Having studied it, so do I.

I'll be in Santa Clara, Calif., November 3 - 5 for the ISP.CON show.

Maybe there's going to be a forum on the subject.

Jeff

Good Luck, Jeff