Wednesday, December 3, 2014

Proper SPF record

Our company emails are usually treated as spam. When we checked our score on Spamassassin, our score was pretty bad, 3.3 and the main reason was our SPF record.



We would like to update our SPF record so that we resolve this issue. However, we are not very familiar with SPF records, so we would like to get your help:



Our outside third party mail server uses three SMTP servers (let's call them 1.1.1.1, 2.2.2.2 and 3.3.3.3). Our mx is forwarded to 4.4.4.4. Currently, our mx record is the following:



v=spf1 +a +mx +ip4:1.1.1.1 +ip4:2.2.2.2 +ip4:3.3.3.3 ~all




When we tested our email, we have received the following info from mail-tester.com:



softfail
domain.com.tr: Sender is not authorized by default to use 'aaa.aaa@domain.com.tr' in 'mfrom' identity, however domain is not currently prepared for false failures (mechanism '~all' matched)



domain.com.tr: Sender is not authorized by default to use 'aaa.aaa@domain.com.tr' in 'mfrom' identity, however domain is not currently prepared for false failures (mechanism '~all' matched)



Received-SPF: softfail (domain.com.tr: Sender is not authorized by default to use 'aaa.aaa@domain.com.tr' in 'mfrom' identity, however domain is not currently prepared for false failures (mechanism '~all' matched)) receiver=ns303428.ip-94-23-206.eu; identity=mailfrom; envelope-from="aaa.aaa@domain.com.tr"; helo=smtp.54.36.145.12.eu01.server.plus; client-ip=54.36.145.12




Any help would be appreciated!

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...