This smtp response doesn't match this email message. In any case, both of these messages did pass authentication, but we chose the wrong error message to send in response to this one (the other was accepted). I'll file a bug.
Brandon On Fri, Apr 21, 2023 at 1:02 AM Alessandro Vesely via mailop < mailop@mailop.org> wrote: > This morning I found this: > > 421-4.7.0 This mail is unauthenticated, which poses a security risk to the > 421-4.7.0 sender and Gmail users, and has been blocked. The sender must > 421-4.7.0 authenticate with at least one of SPF or DKIM. For this message, > DKIM > 421-4.7.0 checks did not pass and SPF check for [tana.it] did not pass > with ip: > 421-4.7.0 [94.198.96.74]. The sender should visit > 421-4.7.0 https://support.google.com/mail/answer/81126#authentication for > 421 4.7.0 instructions on setting up authentication. > d9-20020a05640208c900b00504b18d24f8si586620edz.362 - gsmtp > > I changed SPF recently (after changing ISP), while DKIM signing remained > the same. I attach the message. > > Best > Ale > -- > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
