|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
31 Oct 2024, 07:33 AM | #1 |
The "e" in e-mail
Join Date: Sep 2005
Location: Macao
Posts: 2,300
Representative of:
tls-mail.com |
Please fix up your SPF record
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. |
31 Oct 2024, 08:15 AM | #2 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 9,005
|
This forum is not guaranteed to be monitored by Fastmail staff. You need to report this directly to Fastmail.
|
31 Oct 2024, 08:55 AM | #3 |
Cornerstone of the Community
Join Date: Jul 2003
Posts: 780
|
|
31 Oct 2024, 09:17 AM | #4 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 9,005
|
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 |
31 Oct 2024, 09:31 AM | #5 | |
The "e" in e-mail
Join Date: Feb 2005
Location: USA
Posts: 2,011
|
Quote:
|
|
31 Oct 2024, 01:37 PM | #6 | ||
The "e" in e-mail
Join Date: Sep 2005
Location: Macao
Posts: 2,300
Representative of:
tls-mail.com |
Quote:
Quote:
|
||
31 Oct 2024, 08:30 PM | #7 |
The "e" in e-mail
Join Date: Sep 2005
Location: Macao
Posts: 2,300
Representative of:
tls-mail.com |
And another sender IP was found 202.12.124.196
which is also missed from their official SPF. |
31 Oct 2024, 11:15 PM | #8 |
Essential Contributor
Join Date: Jan 2017
Posts: 316
|
Check spfall.messagingengine.com. This is not a mistake, it's deliberate policy.
See https://www.emaildiscussions.com/showthread.php?t=76295 Last edited by SideshowBob : 1 Nov 2024 at 12:00 AM. |
1 Nov 2024, 06:25 AM | #9 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 9,005
|
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 |
1 Nov 2024, 07:35 AM | #10 | |
The "e" in e-mail
Join Date: Sep 2005
Location: Macao
Posts: 2,300
Representative of:
tls-mail.com |
Quote:
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. |
|
2 Nov 2024, 01:05 AM | #11 |
Essential Contributor
Join Date: Jan 2017
Posts: 316
|
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.
|
2 Nov 2024, 06:55 AM | #12 | |
The "e" in e-mail
Join Date: Sep 2005
Location: Macao
Posts: 2,300
Representative of:
tls-mail.com |
Quote:
|
|
2 Nov 2024, 11:24 PM | #13 | |
Essential Contributor
Join Date: Jan 2017
Posts: 316
|
Quote:
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. |
|
Thread Tools | |
|
|