Thanks.
It's actually the mailing script this client is using that is adding the
headers in this way. I will have to get with the client to resolve this.
That answers that issue.
On Mon, Sep 18, 2023 at 9:53 AM Scott Mutter
wrote:
> We're seeing an increase of errors from Google's mail
On 2023-09-18 at 10:53:16 UTC-0400 (Mon, 18 Sep 2023 09:53:16 -0500)
Scott Mutter via mailop
is rumored to have said:
I'm not sure if a leading space in a message header is proper.
Nope.
Any leading whitespace in a header line indicates that it is logically
part of the prior header. You're
Scott,
Hmmm, I believe the leading space is how "folded" (extra long
header lines) are denoted so Google is likely viewing the MIME
line as an extension of the from line.
--
Larry Smith
lesm...@ecsis.net
On Mon September 18 2023 09:53, Scott Mutter via mailop wrote:
> We're seeing an
No, leading spaces in message headers are not allowed by the spec.
Nor are multiple From headers.
Multiple addresses in a single from header is technically allowed, but
Google has enforced against it since implementing DMARC nearly a decade ago.
A space in front of a header indicates a header
Dnia 18.09.2023 o godz. 09:53:16 Scott Mutter via mailop pisze:
> Headers formatted as:
>
> From: Name
> MIME-Version: 1.0
>
> Generates this multiple addresses in From header error.
Because this header is equivalent to:
From: Name MIME-Version: 1.0
and somehow Google interprets it as
We're seeing an increase of errors from Google's mail servers complaining
about multiple addresses in the From header. But these messages do not
have multiple addresses in the From headers or multiple From headers.
Best I can tell, this seems to be caused by additional spaces in some of
the
