SPF should be checked against the connecting IP, but because that's not
a viable option with a POP3 import Google does this horrible thing of
checking a Received header and comparing SPF there. The only way to fix
this is to build your infrastructure around the entire concept and
potentially break other things. You don't want to remove Received
headers for inbound email, that's crazy. Google is wrong on this, and it
should just be accepted as their failure.
My 2 cents.
On 2022-02-22 07:58, Christos Chatzaras via mailop wrote:
Hello,
I have a customer that fetches his e-mails to Gmail accounts using
POP3. And also he configured Gmail accounts to send e-mails using our
SMTP.
When they send e-mails between their e-mail accounts we have this:
https://dpaste.com/8MNNRGMX4.txt
Looks like 209.85.216.48 which is a Gmail POP3 client is used as
"sender IP" and because we don't include include:_spf.google.com in
the SPF record it shows this warning:
"Be careful with this message. Gmail could not verify that it actually
came from web-net.gr. Avoid clicking links, downloading attachments or
replying with personal information.'
The issue started today. Any idea why Gmail does this?
Kind regards,
Christos Chatzaras
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
