I appreciate the feedback from you both!  I'll see if this is something we
can confirm/exclude.

J

On Tue, Nov 8, 2022 at 3:15 PM Brandon Long via mailop <[email protected]>
wrote:

> Another one I've seen is an extra newline which ends the headers, ie:
>
> Subject: foo
> To: [email protected]
>
> From: [email protected]
>
> I don't recall how annoying our parser is, whether something like this
> would also cause early end of headers:
>
> Subject: foo
> To: bar@
> example.net
> From: [email protected]
>
> Brandon
>
> On Tue, Nov 8, 2022 at 2:15 PM Mary via mailop <[email protected]> wrote:
>
>>
>> I've seen this before, when the header above the From header is broken:
>>
>> Authentication-Results: server;
>>         dkim=blah reason="blah";
>>         From: "Valid" <[email protected]>
>> To: mailop <[email protected]>
>>
>>
>> The parser thinks that the From: header is part of the previous header,
>> thus ignoring it and ending with a missing header error.
>>
>>
>>
>> On Tue, 8 Nov 2022 13:41:57 -0800 John Stephenson via mailop <
>> [email protected]> wrote:
>>
>> > We've seen the below failure for two different clients (each in one
>> > specific campaign) which resulted in lots of these failures at Gmail for
>> > those respective campaigns.  Our Support/Ops team continue to insist
>> that
>> > we sent these campaigns with the same exact from address/header/domain
>> set
>> > up as all of the other campaigns launched on this day and that the issue
>> > must be on Gmail's side.
>> > I'm praying that somebody here has had experience with this failure and
>> > tracked down some subtle/quirky reason why an otherwise reliable sending
>> > MTA would encounter this failure?
>> >
>> > Best,
>> >
>> > John
>> >
>> >
>> > 550-5.7.1 [142.54.247.27] Our system has detected that this message is
>> not
>> > RFC\r\n550-5.7.1 5322 compliant:\r\n550-5.7.1 'From' header is
>> > missing.\r\n550-5.7.1 To reduce the amount of spam sent to Gmail, this
>> > message has been\r\n550-5.7.1 blocked. Please visit\r\n550-5.7.1
>> > https://support.google.com/mail/?p=RfcMessageNonCompliant\r\n550 5.7.1
>> and
>> > review RFC 5322 specifications for more information.
>> _______________________________________________
>> mailop mailing list
>> [email protected]
>> https://list.mailop.org/listinfo/mailop
>>
> _______________________________________________
> mailop mailing list
> [email protected]
> https://list.mailop.org/listinfo/mailop
>
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop

Reply via email to