I revisiting this for completeness just in case it happens to anyone else too:
Google is dropping messages with Message-Id: headers that do not enclose the Message-Id: in angle brackets. Meaning that Message-Id: 1234567890abcd is invalid, and Message-Id: <1234567890abcd> is valid >From my interpretation of the RFCs, Google is doing it right (even though I wished at the time they did not drop). I contacted the mail producer of said emails and they fixed their system before submitting to Mailgun. On Thu, May 1, 2025 at 7:06 PM Yiorgos [George] Adamopoulos < [email protected]> wrote: > We have a client of theirs sending to us password recovery emails without > proper MessageID. As a result, Google Workspace drops the email message, > thus password recovery is impossible. > > Apr 30, 2025, 12:54:10 PM Received from an SMTP client with IP address: > 69.72.33.38 (TLS enabled) > Apr 30, 2025, 12:54:10 PM Bounced > 550-5.7.1 [209.85.220.69] Messages missing a valid Message-ID header are > not > 550-5.7.1 accepted. For more information, go to > 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant and > review > 550 5.7.1 RFC 5322 specifications. > d9443c01a7336-22db4c039a8sor86173515ad.0 - gsmtp > Apr 30, 2025, 12:54:10 PM Received from an SMTP server with IP address: > 209.85.220.69 (TLS enabled) > 550-5.7.1 [209.85.220.69] Messages missing a valid Message-ID header are > not > 550-5.7.1 accepted. For more information, go to > 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant and > review > 550 5.7.1 RFC 5322 specifications. > Apr 30, 2025, 12:54:10 PM Bounced > If anyone can point me to a contact person to describe this weirdness, > that would be much appreciated. > > -- > > keep raising the bar || https://gr.linkedin.com/yiorgos > -- keep raising the bar || https://gr.linkedin.com/yiorgos
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
