SPF Fails IP Address Not Permitted Sender

0

My emails SPF are failing because 209.222.82.148 is not a designated sender for my subdomain used in the MAILFROM setup.

My TXT Record for the MAILFROM setup is:
v=spf1 include:amazonses.com -all
I have tried ~all as well, but I wouldn't expect that to work.

I am getting this TXT record when looking at amazonses.com for the allowed IP addresses. This IP address does not seem to fit any of these ranges:
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:76.223.180.0/23 ip4:76.223.188.0/24 ip4:76.223.189.0/24 ip4:76.223.190.0/24 -all

What is causing the sender IP to be different than those allowed from amazonses.com? The only thing that I can imagine it being is that my SES is currently under sandbox access.

已提問 5 年前檢視次數 898 次
2 個答案
0

Hi,

Sandbox mode has no relation. If you were sending to a non verified recipient in sandbox mode, it will give you an address not verified error.

Regarding SPF - All mechanisms may specify qualifiers for how to handle a match:

  • for pass
  • for fail
    ~ for soft fail
    ? for neutral

Now checking the IP address "209.222.82.148" that you have mentioned looks to be from Barracuda email security service. Is your email being relayed via some other SMTP?

$ dig -x 209.222.82.148 +short
mail.ess.barracuda.com.

Can you please provide the complete header details from the receiving side?

Regards,
Gaurav @ AWS

已回答 5 年前
0

Thank you, that made me realize I needed to add the barracuda SPF domain for mail for subdomain's SPF record

Record
TXT v=spf1 include:spf.ess.barracudanetworks.com include:amazonses.com -all

已回答 5 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南