: Adding SPF records in GoDaddy I have the GoDaddy hosting and send mail using the following code: $to = "demomail@gmail.com"; $subject = "Test mail"; $message = "Hello! This is a simple email

@Ravi8258870

I wouldn't use -all, unless you have everything else set up correctly, so stick with ~all.

The only time to use -all is if you have SRS - Sender Rewriting Scheme set up on your mail server. Anyone you send email to that has a forwarder set up, it will hard fail the SPF check on the message and not deliver it.

Here's an example of how this exact scenario plays out.

SRS Example

There's a lot to setting up and configuring emails, SPF, DKIM, DMARC, SRS, Etc. There's plenty of resources on the web on how to do it all, you just have to search for them.

The only way to know for sure if your email is properly authenticating, so that link doesn't show is to use one of the mail email authentication tools out there to verify your configuration. Here's a popular report a lot of people use to test their setup.

Email Authentication Report

Vote Up Vote Down

@Eichhorn148

SPF is only one of two parts of fixing this. The other is DKIM signing.
support.google.com/mail/bin/answer.py?hl=en&answer=1311182

I'm a sender and I don't want my recipients to see the "via" link. What can I do?

Gmail checks whether emails are correctly authenticated. If your messages are sent by a bulk mailing vendor or by third-party affiliates, please publish an SPF record that includes the IPs of the vendor or affiliates which send your messages and sign your messages with a DKIM signature that is associated with your domain.

Vote Up Vote Down

@Nimeshi995

Your spf line is wrong, let's break it down:

v=spf1


Version 1 SPF, everything right there, let's see the next parameters:

include:_spf.google.com


Here you're specifying that your mail is valid if you're sending it from a Google Apps domain. Are you using Google Apps?, the next parameter:

~all


Denies every other domain, so if you send from a non Google Apps domain, you'll be invalid in terms of SPF. You must change your include parameter to point to your sending server (probably something like include:spf.secureserver.net inferring from the image you posted).

Also, see ceejayoz response respecting DKIM. I forgot that for a non Google Apps Domain you have to include that.

Vote Up Vote Down