> On 29 Apr 2024, at 16:02, Mendel Kucharzeck via mailop <mailop@mailop.org> > wrote:
[snip] > Questions: > > - Anyone else seeing this behaviour from gmail recently? > - Could the newly created, custom MAIL-FROM-domain cause a behaviour like > this? The MAIL-FROM-Domain has not yet been used before, but the sending > email address was the same You changed a domain that is important in authentication. That changed the identity of the message. That meant you were treated as a semi-new sender by the machine learning filters. > Any insights or hints on how to investigate this would be highly appreciated. You may need to back off and go through a short warmup phase to introduce that this SPF + this DKIM + this Header From from SES shared pool is a valid source of mail. ALSO - did you actually have any delivery problems? One thing I’ve noticed (at Gmail in particular) is that changes in an authenticated domain often result in a lower rate of pre-fetching of images *without* any corresponding change in delivery. Before you start freaking out about things, check to see if your delivery is different. Pixel loads are fickle beasts and it’s worthwhile to understand if this is a change in display behavior (ie, it’s a new sender of email, so Google isn’t going to prefetch mail until it knows if this is a valid and wanted mail stream or if it’s someone faking your sending domain) or if it’s a change in delivery behavior (ie, Google dropped all the mail in the spam folder). If it’s simply prefetch behavior, there’s nothing you can do. Google gonna Google. laura -- The Delivery Expert Laura Atkins Word to the Wise la...@wordtothewise.com Delivery hints and commentary: http://wordtothewise.com/blog
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
