Emails from "Send a Message" bounce with bad Message-ID header

I sometimes get a bounce message trying to deliver a forwarded email from "Send a Message" to my gmail account from my personal self-hosted email server.
Mar 1 15:40:14 ``my server name`` postfix/smtp[396296]: E774DC08BEC: to=<``my gmail address``>, relay=gmail-smtp-in.l.google.com[142.250.141.27]:25, delay=3.9, delays=0.07/0.08/0.37/3.4, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[142.250.141.27] said: 550-5.7.1 [``my email server IP``] Messages missing a valid messageId header are not 550 5.7.1 accepted. j21-20020a632315000000b004fc235bd318si11928124pgj.669 - gsmtp (in reply to end of DATA command))

What I find interesting is that the Message-ID header the church creates does not follow the RFC. The actual header in the email is formatted like this:
Message-ID: ESM_Email_Serivce.JavaMail.e6bcffe7-abd3-4337-a7c8-fb2f8d48524a

When emails get delievered, I see google has "fixed" the Message-ID header:
Message-ID: <63ff70ca.170a0220.87b3e.71dfSMTPIN_ADDED_BROKEN@mx.google.com>
X-Google-Original-Message-ID: ESM_Email_Serivce.JavaMail.e6bcffe7-abd3-4337-a7c8-fb2f8d48524a

The RFC for Message-ID format wants it to be in angle brackets and look sort of like an email address, the way google "fixes" it.
https://www.rfc-editor.org/rfc/rfc5322

Not to mention someone misspelled "Service" as "Serivce".

I'm really hoping that this might be related to some of the issues reported in this thread about emails not being delivered:
viewtopic.php?t=40965

But since I host my own email server, and I'm certainly not stopping emails from going through, I only have this one Message-ID thread to pull on.

Is there a way to report this to someone who can "fix" it? Or maybe I should just fix it myself and see if it helps?
https://serverfault.com/questions/33598 ... message-id

Good find! It might be worth sending this report using the feedback link in Leader and Clerk Resources.
There are other issues with Send a Message delivery, so it wouldn't solve all the problems, but it would probably be good for the Church to get the Message-ID up to spec in any case.