This is a result from isnotspam.com
SPF Check : softfail Sender-ID Check : neutral DomainKeys Check : neutral DKIM Check : neutral SpamAssassin Check : ham (non-spam)
HELO hostname: in6.hostgator.in Source IP: 119.18.60.5 mail-from: [email protected] Anonymous To: [email protected]
Result: softfail ID(s) verified: [email protected] DNS record(s): propertyfirst.in. 14394 IN TXT "v=spf1 a mx include:websitewelcome.com ~all"
Result: neutral
ID(s) verified: [email protected] DNS record(s): propertyfirst.in. 14394 IN TXT "v=spf1 a mx include:websitewelcome.com ~all"
Result: neutral (message not signed) ID(s) verified: [email protected] Selector= domain= DomainKeys DNS Record=
Result: neutral (message not signed) ID(s) verified: [email protected] Selector= domain= DomainKeys DNS Record=
---------------------------------------------------------- SpamAssassin check details: ---------------------------------------------------------- SpamAssassin v3.3.1 (2010-03-19)
Result: ham (non-spam) (05.9points, 10.0 required)
pts rule name description
Can someone please tell me what is the issue here and what spf and how do I set it up.
Will setting up a spf help me in anyways ?
Indeed, an SPF SoftFail can cause your email to be classified as spam.
Judging from the current state of the TXT record for propertyfirst.in, you have already figured it out on your own, but for future reference, SPF is a way for the domain administrator to designate hosts as legitimate senders for the domain in question. The policy is published in DNS using a TXT or SPF RR.
In this particular case, the SPF policy of propertyfirst.in did not designate your web server 119.18.60.5 as a permitted sender. Consequently, emails from your web server were considered to be forged and marked as spam.
Your current SPF policy is v=spf1 +a +mx +ip4:119.18.60.5 +include:propertyfirst.in ~all, which explicitly permits 119.18.60.5 to send emails in the name of propertyfirst.in.
By the way you can lose the "+" PASS qualifiers, SPF mechanisms default to that.