Please fix up your SPF record

[jeffpan]

I saw the new IP 103.168.172.197 was added as sender server.
But it's not included in Fastmail's official SPF record.
Please fix up it. Thanks.

[n5bb]

This forum is not guaranteed to be monitored by Fastmail staff. You need to report this directly to Fastmail.

[chrisjj]

Originally Posted by jeffpan

it's not included in Fastmail's official SPF record.

Goodness. That's an appalling blunder.

[n5bb]

The IP 103.168.172.197 is assigned to fastmailteam.com, which is used by Fastmail staff (and perhaps other uses). The SPF record for fastmailteam.com includes spf.messagingengine.com, which I believe includes the IP range of 103.168.172.197. So I don’t see any problem.

Bill

[Bamb0]

Originally Posted by jeffpan

I saw the new IP 103.168.172.197 was added as sender server.
But it's not included in Fastmail's official SPF record.

Maybe they forgot buddy,Im sure they will get round to it

[jeffpan]

Originally Posted by n5bb

The IP 103.168.172.197 is assigned to fastmailteam.com, which is used by Fastmail staff (and perhaps other uses). The SPF record for fastmailteam.com includes spf.messagingengine.com, which I believe includes the IP range of 103.168.172.197. So I don?t see any problem.

Bill

Really? currently fastmail has such IP addresses for their SPF:

spf.messagingengine.com. 86400 IN TXT "v=spf1 ip4:103.168.172.128/27 ip4:202.12.124.128/27 -all"

Certainly 103.168.172.197 is not included in their SPF ip space.

[jeffpan]

And another sender IP was found 202.12.124.196
which is also missed from their official SPF.

[SideshowBob]

Check spfall.messagingengine.com. This is not a mistake, it's deliberate policy.

See

https://www.emaildiscussions.com/showthread.php?t=76295

[n5bb]

Sorry - you are correct that the *.*.*.128/27 address range does not include *.*.*.196.

What was the actual FROM sending domain name? That?s the domain whose SPF record must be checked. Since you are complaining about a Fastmail SPF record, I assume that the emails in question were sent with envelope-FROM at a Fastmail-owned domain or a private domain hosted at Fastmail. I just sent a test message with FROM at my Fastmail-hosted private domain and it passed SPF with a sender IP address of 103.168.172.159, which is within the 103.168.172.128/27 CIDR range.

Bill

[jeffpan]

Originally Posted by SideshowBob

Check spfall.messagingengine.com. This is not a mistake, it's deliberate policy.

See

https://www.emaildiscussions.com/showthread.php?t=76295

That's nice knowledge. This matches my case.

I have a domain which is not hosted on fastmail, but uses fastmail as auth-smtp server. When messages sent with this domain from fastmail smtp server, they fall into spfall SPF space.

I have tested that if I use the regular fastmail domains to send email from webmail, they fall into the normal spf.messagingengine.com space.

I am so confused FM takes this policy for their auth-smtp servers including the one used by Pobox.

[SideshowBob]

Originally Posted by jeffpan

I am so confused FM takes this policy for their auth-smtp servers including the one used by Pobox.

Did you create a matching entry under "My email addresses" at Fastmail, and/or somewhere at Pobox (I'm assuming the domain was hosted at Pobox)? I did see this happen even with an @username.sent.com address because there was no webmail identity for the subdomain.

[jeffpan]

Originally Posted by SideshowBob

Did you create a matching entry under "My email addresses" at Fastmail, and/or somewhere at Pobox (I'm assuming the domain was hosted at Pobox)? I did see this happen even with an @username.sent.com address because there was no webmail identity for the subdomain.

My domain was not hosted on fastmail/pobox. But used FM/Pobox as the auth-smtp server for sending email. Some of friends on this forum are using the domain email as their private email. There was no problem in the past time. But recently FM upgraded their architecture, the mails were sent from unlisted-SPF IPs which caused the receive provider such as gmail think they were spams.

[SideshowBob]

Originally Posted by jeffpan

My domain was not hosted on fastmail/pobox. But used FM/Pobox as the auth-smtp server for sending email. Some of friends on this forum are using the domain email as their private email. There was no problem in the past time. But recently FM upgraded their architecture, the mails were sent from unlisted-SPF IPs which caused the receive provider such as gmail think they were spams.

It will be a gmail change; the thread I started when I first noticed this is from over 4 years ago.

If the domain isn't hosted at fastmail, you can't fix it by setting an identity, you will need to use spfall, or equivalent.