Google has recent started requiring SPF. I don't know if they require it
100% of the time but they do now reject emails from domains that either
don't have it, or have it improperly configured, and they won't accept
it from those domains until it's fixed. It has helped me a good bit,
making it easier to identify my customers that are violating my policy
and sending without valid SPF.
At least, by this point, we should be able to say that everyone has had
an opportunity to at least adopt SPF. Anyone who doesn't, by now,
generally doesn't care about their delivery quality.
On 2022-08-27 17:09, Darrell Budic via mailop wrote:
Anyone else seeing this? Customer of mine just got some bounces from
gmail for invalid SPF/DKIM. He doesn’t have either, so I’m not
sure what this is about?
Mind you, I did send him to setup a valid SPF entry, and
authentication is good, but this seems like a misleading error
message...
The mail system
<[email protected]>: host gmail-smtp-in.l.google.com
[1][142.251.4.27] said:
550-5.7.26 This message does not pass authentication checks (SPF
and DKIM
both 550-5.7.26 do not pass). SPF check for [musichael.com [2]]
does not pass
with ip: 550-5.7.26 [204.130.133.20].To best protect our users
from spam,
the message 550-5.7.26 has been blocked. Please visit 550-5.7.26
https://support.google.com/mail/answer/81126#authentication for
more 550
5.7.26 information.
b185-20020a2567c2000000b006953ea7fad6si1842767ybc.571 -
gsmtp (in reply to end of DATA command)
Reporting-MTA: dns; smtp.ohgnetworks.com [3]
X-Postfix-Queue-ID: 358D21F4D4
X-Postfix-Sender: rfc822; [email protected]
Arrival-Date: Sat, 27 Aug 2022 13:10:52 +0000 (UTC)
Links:
------
[1] http://gmail-smtp-in.l.google.com
[2] http://musichael.com
[3] http://smtp.ohgnetworks.com
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
