On 19 Apr 2022, at 16:11, Michael Peddemors via mailop <mailop@mailop.org> wrote: > > And we also see that they have not yet 'hard enforced', but it looks like > some trigger on a domain results in requiring SPF for that domain.
It wouldn’t surprise me if there were some triggers that made authentication be looked at harder. But it is demonstrably incorrect to say that Google is requiring certain types of authentication for delivery. > Of course, we don't expect Google to reveal their secrets, but we can assume > things like new IP(s), new domains, sudden traffic surges, or customers > clicking on 'this is spam' all might cause the requirement for SPF on a > certain domain. This was a brand new IP without any rDNS (ie, it’s not intended to send mail). I do expect volume plays into it. But, as I’ve been saying: Google’s filtering is nuanced and tries to do the right thing most of the time. laura -- The Delivery Experts Laura Atkins Word to the Wise la...@wordtothewise.com Email Delivery Blog: http://wordtothewise.com/blog
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
