Re: What's up with emails?

On 22 February 2024 17:49:10 CET, Derick Rethans <derick@php.net> wrote: > On Thu, 22 Feb 2024, mjec wrote: > > > On Thu, 2024-02-22 at 10:29 -05:00, Alain D D Williams <addw@phcomp.co.uk> wrote: > >> On Thu, Feb 22, 2024 at 09:05:22AM -0500, Derick Rethans wrote: > >> > >>> Gmail is rejecting emails after we moved the servers without telling us why, in > >>> enough detail to do anything about it. > >> > >> I run other mail lists and have had similar problems with gmail recently. > > > > Gmail explicitly tightened their requirements for senders this month, so while it's > > likely the server change is related, it may not be the entire cause. > > > > Specifically, they require: > > > > - valid spf, with specific rules for quarantining email that has @gmail.com From but > > doesn't pass spf > > - valid dkim > > - dmarc configured if the server sends more than 5k emails to Gmail > > We should have all of that though? > > > > > They also equivocally indicate a requirement for ARC and a List-Id header. > > We have a List-Id header, but I've not even heard of ARC. It is on our list to investigate > though. Our SMTP logs definitely don't say anything about this though. > > > This is all at https://support.google.com/a/answer/81126. > > > > I think ARC is a must; without it we'll never get to passing dkim at least, even if > > we rewrite from so spf passes. > > But SPF is now passing? The postmaster tools show this: > > Date DKIM success rate SPF success rate DMARC success rate > 15 Feb 2024 100.0% 100.0% 0.0% > 16 Feb 2024 100.0% 100.0% 0.0% > 17 Feb 2024 100.0% 100.0% 0.0% > 18 Feb 2024 100.0% 100.0% 0.0% > 19 Feb 2024 100.0% 100.0% 100.0% > 20 Feb 2024 100.0% 100.0% 100.0% > > > I'm happy to pitch in to help getting this configured if that's helpful, though > > I'm also very conscious that too many cooks is often a greater harm than good when it comes to > > administration. But reach out if you think I can be helpful. > > We could definitely use some people that now email delivery. The main issue is that the things came together: Us moving to a new listserver and Gmail introducing new ways of fighting spam. The later is what makes life hars now and would also have caused trouble on the old server. We are currently in the process of implementig all of the stuff that gmail expects us to have. The last ones are ARC and one-click unsubscribe. If you want to know more about the hoops we have to jump in addition to moving the list to a new server check out https://blog.google/products/gmail/gmail-security-authentication-spam-protection/ Cheers Andreas -- Andreas Heigl