Am I missing something as well? Google just rejected a client due to PTR on mailop-boun...@mailop.org but it seems fine to me
-----Original Message----- From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Philip Paeps via mailop Sent: July 13, 2022 3:31 AM To: mailop Subject: [mailop] Did Google become stricter about RFC 5322? In the past couple of days, I'm seeing an uptick in rejects from Gmail as follows: <[elided]@gmail.com>: host gmail-smtp-in.l.google.com[2607:f8b0:4004:c17::1a] said: 550-5.7.1 [2610:1c1:1:606c::19:2] Our system has detected that this message is 550-5.7.1 not RFC 5322 compliant. To reduce the amount of spam sent to Gmail, 550-5.7.1 this message has been blocked. Please review 550 5.7.1 RFC 5322 specifications for more information. bp41-20020a05620a45a900b006a64dbdb75asi7765031qkb.308 - gsmtp (in reply to end of DATA command) As far as I can tell, the message is compliant. It doesn't have any of the obvious problems, at least. From, To, Message-ID and Date are supplied. No duplicate headers. These are text/plain messages: commit mail from an svn repository. I like to think I have a reasonably robust understanding of RFC 5322. I'm sure I must be missing something very subtle. Has anyone else seen (more of) these? Thanks. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
