Re: [mailop] "header is missing" at Gmail
On 11/8/2022 2:03 PM, Mary via mailop wrote: 've seen this before, when the header above the From header is broken: Authentication-Results: server; dkim=blah reason="blah"; From: "Valid" To: mailop The parser thinks that the From: header is part of the previous header, thus ignoring it and ending with a missing header error. On the offchance anyone reading this thread misses the basic point -- and no, I don't expect that include most or possibly any of... you: The From field, here, is in fact part of the A-R field. Because 'from' is indented, it IS a continuation of the preceding field. On 11/8/2022 3:11 PM, Brandon Long via mailop wrote: Another one I've seen is an extra newline which ends the headers, ie: Subject: foo To: b...@example.net From: campa...@example.org And again, to state the obvious, just to document it explicit;y in this thread: The blank line means that the From field is in the body, not the header. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net mast:dcrocker@mastodon.social ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] "header is missing" at Gmail
These sound likely different, but I wonder if the German app mistakenly is translating the From header name into German. It could also be doing something wrong with adding non-ascii characters to the From header contents, though our parser should be more lenient about that. In general, though, the phone should be connecting to an MSA to send the message. The Gmail MSA will add a From header if it's missing, so you shouldn't see this issue. Whatever MSA you're using for your test should also be doing that, I would think that level of message correction would be normal, but maybe not. Brandon On Wed, Nov 9, 2022 at 7:26 AM jose.morales.velazq...@mailtrust.com < jose.morales.velazq...@mailtrust.com> wrote: > Hello, > > I am also seeing this error sending to Gmail. > In our case, the client/sender seems to be using the Email client feature > on a Samsung android mobile and it happens when used on German language. I > tested this locally on my own Samsung and had the same result. > > Is a non-English language also being used for your case or also related to > an Android app? > > > Sincerely, > Jose > > -Original Message- > From: "John Stephenson via mailop" > Sent: Wednesday, November 9, 2022 8:47am > To: "Brandon Long" > Cc: mailm...@ionos.gr, mailop@mailop.org > Subject: Re: [mailop] "header is missing" at Gmail > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop > 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 > wrote: > > > Another one I've seen is an extra newline which ends the headers, ie: > > > > Subject: foo > > To: b...@example.net > > > > From: campa...@example.org > > > > 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: campa...@example.org > > > > Brandon > > > > On Tue, Nov 8, 2022 at 2:15 PM Mary via mailop > wrote: > > > >> > >> I've seen this before, when the header above the From header is broken: > >> > >> Authentication-Results: server; > >> dkim=blah reason="blah"; > >> From: "Valid" > >> To: mailop > >> > >> > >> 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 < > >> mailop@mailop.org> 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 > >> mailop@mailop.org > >> https://list.mailop.org/listinfo/mailop > >> > > ___ > > mailop mailing list > > mailop@mailop.org > > https://list.mailop.org/listinfo/mailop > > > > > ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] "header is missing" at Gmail
Hello, I am also seeing this error sending to Gmail. In our case, the client/sender seems to be using the Email client feature on a Samsung android mobile and it happens when used on German language. I tested this locally on my own Samsung and had the same result. Is a non-English language also being used for your case or also related to an Android app? Sincerely, Jose -Original Message- From: "John Stephenson via mailop" Sent: Wednesday, November 9, 2022 8:47am To: "Brandon Long" Cc: mailm...@ionos.gr, mailop@mailop.org Subject: Re: [mailop] "header is missing" at Gmail ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop 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 wrote: > Another one I've seen is an extra newline which ends the headers, ie: > > Subject: foo > To: b...@example.net > > From: campa...@example.org > > 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: campa...@example.org > > Brandon > > On Tue, Nov 8, 2022 at 2:15 PM Mary via mailop wrote: > >> >> I've seen this before, when the header above the From header is broken: >> >> Authentication-Results: server; >> dkim=blah reason="blah"; >> From: "Valid" >> To: mailop >> >> >> 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 < >> mailop@mailop.org> 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 >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop >> > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop > ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] "header is missing" at Gmail
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 wrote: > Another one I've seen is an extra newline which ends the headers, ie: > > Subject: foo > To: b...@example.net > > From: campa...@example.org > > 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: campa...@example.org > > Brandon > > On Tue, Nov 8, 2022 at 2:15 PM Mary via mailop wrote: > >> >> I've seen this before, when the header above the From header is broken: >> >> Authentication-Results: server; >> dkim=blah reason="blah"; >> From: "Valid" >> To: mailop >> >> >> 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 < >> mailop@mailop.org> 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 >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop >> > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop > ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] "header is missing" at Gmail
Another one I've seen is an extra newline which ends the headers, ie: Subject: foo To: b...@example.net From: campa...@example.org 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: campa...@example.org Brandon On Tue, Nov 8, 2022 at 2:15 PM Mary via mailop wrote: > > I've seen this before, when the header above the From header is broken: > > Authentication-Results: server; > dkim=blah reason="blah"; > From: "Valid" > To: mailop > > > 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 < > mailop@mailop.org> 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 > mailop@mailop.org > https://list.mailop.org/listinfo/mailop > ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] "header is missing" at Gmail
I've seen this before, when the header above the From header is broken: Authentication-Results: server; dkim=blah reason="blah"; From: "Valid" To: mailop 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 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 mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] "header is missing" at Gmail
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 mailop@mailop.org https://list.mailop.org/listinfo/mailop
