[mlmmj] Broken email

[mlmmj] Broken email

[Gavin Henry]

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

Hi all,

We've set up mlmmj but emails come through broken in Gmail and just shoe
this in the body with no Subject :

MIME-Version: 1.0
X-Received: by 10.68.209.138 with SMTP id
mm10mr27452276pbc.88.1412636264404;
 Mon, 06 Oct 2014 15:57:44 -0700 (PDT)
Received: by 10.70.32.68 with HTTP; Mon, 6 Oct 2014 15:57:44 -0700 (PDT)
Received: by 10.70.32.68 with HTTP; Mon, 6 Oct 2014 15:57:44 -0700 (PDT)
Date: Mon, 6 Oct 2014 23:57:44 +0100
Message-ID: <CAPcb_GLbsXNC7w6VHq
<CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>-
<CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>
FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw
<CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>@
<CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>
mail.gmail.com
<CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>>
Subject: [NOC Alerts] test
From: Gavin Henry <ghenry@ <ghenry@suretec.co.uk>suretec.co.uk
<ghenry@suretec.co.uk>>
To: noc <noc-alerts@lists.suretec.net>-alerts@
<noc-alerts@lists.suretec.net>lists.suretec.net
<noc-alerts@lists.suretec.net>
Content-Type: multipart/alternative; boundary=047d7b111c77bcb66a0504c902b3
Delivered-To: noc <noc-alerts@lists.suretec.net>-alerts@
<noc-alerts@lists.suretec.net>lists.suretec.net
<noc-alerts@lists.suretec.net>

--047d7b111c77bcb66a0504c902b3
Content-Type: text/plain; charset=ISO-8859-1

What's breaking it?

Thanks.

--
Kind Regards,

Gavin Henry.

http://www.surevoip.co.uk

OpenPGP (GPG/PGP) Public Key: 0x8CFBA8E6 - Import from hkp://subkeys.pgp.net
or http://www.suretecgroup.com/0x8CFBA8E6.gpg

[-- Attachment #2: Type: text/html, Size: 2252 bytes --]

Re: [mlmmj] Broken email

[Chris Knadle]

On Tuesday, October 07, 2014 00:21:50 Gavin Henry wrote:
> Hi all,
> 
> We've set up mlmmj but emails come through broken in Gmail and just shoe
> this in the body with no Subject :
> 
> MIME-Version: 1.0
> X-Received: by 10.68.209.138 with SMTP id
> mm10mr27452276pbc.88.1412636264404;
>  Mon, 06 Oct 2014 15:57:44 -0700 (PDT)
> Received: by 10.70.32.68 with HTTP; Mon, 6 Oct 2014 15:57:44 -0700 (PDT)
> Received: by 10.70.32.68 with HTTP; Mon, 6 Oct 2014 15:57:44 -0700 (PDT)
> Date: Mon, 6 Oct 2014 23:57:44 +0100
> Message-ID: <CAPcb_GLbsXNC7w6VHq
> <CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>-
> <CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>
> FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw
> <CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>@
> <CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>
> mail.gmail.com
> <CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>>
> Subject: [NOC Alerts] test
> From: Gavin Henry <ghenry@ <ghenry@suretec.co.uk>suretec.co.uk
> <ghenry@suretec.co.uk>>
> To: noc <noc-alerts@lists.suretec.net>-alerts@
> <noc-alerts@lists.suretec.net>lists.suretec.net
> <noc-alerts@lists.suretec.net>
> Content-Type: multipart/alternative; boundary\x047d7b111c77bcb66a0504c902b3
> Delivered-To: noc <noc-alerts@lists.suretec.net>-alerts@
> <noc-alerts@lists.suretec.net>lists.suretec.net
> <noc-alerts@lists.suretec.net>
> 
> --047d7b111c77bcb66a0504c902b3
> Content-Type: text/plain; charset=ISO-8859-1
> 
> What's breaking it?
> 
> Thanks.
> 
> --
> Kind Regards,
> 
> Gavin Henry.

The headers above show numerous errors and do not show an external email 
sending attempt; all of the Received: lines show IP addresses that are always 
in a private IP range.  The To and From headers seem to have invalid email 
addresses in them like there's some kind of encapsulation going on; same with 
the Message-ID header.  That's all I can determine from the above text.

  -- Chris

--

Chris Knadle
Chris.Knadle@coredump.us

Re: [mlmmj] Broken email

[Gavin Henry]

[-- Attachment #1: Type: text/plain, Size: 54 bytes --]

Thanks. I'll no paste the full raw email later today.

[-- Attachment #2: Type: text/html, Size: 76 bytes --]

Re: [mlmmj] Broken email

[Ben Schmidt]

On 7/10/14 10:21 AM, Gavin Henry wrote:
> Hi all,
>
> We've set up mlmmj but emails come through broken in Gmail and just shoe this in
> the body with no Subject :
>
> MIME-Version: 1.0
> X-Received: by 10.68.209.138 with SMTP id mm10mr27452276pbc.88.1412636264404;
>   Mon, 06 Oct 2014 15:57:44 -0700 (PDT)
> Received: by 10.70.32.68 with HTTP; Mon, 6 Oct 2014 15:57:44 -0700 (PDT)
> Received: by 10.70.32.68 with HTTP; Mon, 6 Oct 2014 15:57:44 -0700 (PDT)
> Date: Mon, 6 Oct 2014 23:57:44 +0100
> Message-ID: <CAPcb_GLbsXNC7w6VHq
> <mailto:CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>-
> <mailto:CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw
> <mailto:CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>@
> <mailto:CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>mail.gmail.com
> <mailto:CAPcb_GLbsXNC7w6VHq-FpqNDqUrA4rXEHu6awi8N2xnyuCvBiw@mail.gmail.com>>
> Subject: [NOC Alerts] test
> From: Gavin Henry <ghenry@ <mailto:ghenry@suretec.co.uk>suretec.co.uk
> <mailto:ghenry@suretec.co.uk>>
> To: noc <mailto:noc-alerts@lists.suretec.net>-alerts@
> <mailto:noc-alerts@lists.suretec.net>lists.suretec.net
> <mailto:noc-alerts@lists.suretec.net>
> Content-Type: multipart/alternative; boundary\x047d7b111c77bcb66a0504c902b3
> Delivered-To: noc <mailto:noc-alerts@lists.suretec.net>-alerts@
> <mailto:noc-alerts@lists.suretec.net>lists.suretec.net
> <mailto:noc-alerts@lists.suretec.net>
>
> --047d7b111c77bcb66a0504c902b3
> Content-Type: text/plain; charset=ISO-8859-1
>
> What's breaking it?

Looks like the headers are being ended early somehow.

Do you have a customheaders tunable that has an extra newline at the end
of it? That could do it.

Ben.

Re: [mlmmj] Broken email

[Ben Schmidt]

> The headers above show numerous errors and do not show an external
> email sending attempt; all of the Received: lines show IP addresses
> that are always in a private IP range.

That will be because the external sending attempt is still in the
message headers (before they were ended prematurely). Only the headers
after the erroneous newline that's ending them are showing in the
message body the OP pasted.

> The To and From headers seem to have invalid email addresses in them
> like there's some kind of encapsulation going on; same with the
> Message-ID header.

I think that's because you read the plain text version of the email.
Presumably because the OP copied and pasted the message body (which is
actually overflown headers), all the email addresses in it were
converted to hyperlinks by the MUA for HTML mail, and then the
hyperlinks were converted to plain text in a stupid way, totally
mangling them.

So instead of:

To: noc-alerts@lists.suretec.net

you saw:

To: noc <noc-alerts@lists.suretec.net>-alerts@
<noc-alerts@lists.suretec.net>lists.suretec.net
<noc-alerts@lists.suretec.net>

> That's all I can determine from the above text.

Well done for getting that much!

What a mess!

Grins,

Ben.

Re: [mlmmj] Broken email

[Gavin Henry]

Here's the raw email:

http://paste.scsys.co.uk/428484

We're testing with prefix, footer and customerheaders (have now
removed any trailing newlines and will test again):

cat prefix
[NOC Alerts]

cat customheaders
X-Mailinglist: noc-alerts
precedence: bulk
precedence: list
List-Id: <noc-alerts>
List-Unsubscribe: <mailto:noc-alerts+unsubscribe@lists.suretec.net>,
<http://lists.suretec.net/?list=noc-alerts>
List-Owner: Suretec Systems Ltd.


cat footer
-- 
To unsubscribe send a mail to noc-alerts+unsubscribe@lists.suretec.net

Re: [mlmmj] Broken email

[Chris Knadle]

On Tuesday, October 07, 2014 17:30:00 Ben Schmidt wrote:
[...]
> > The To and From headers seem to have invalid email addresses in them
> > like there's some kind of encapsulation going on; same with the
> > Message-ID header.
> 
> I think that's because you read the plain text version of the email.

That's correct.

> Presumably because the OP copied and pasted the message body (which is
> actually overflown headers), all the email addresses in it were
> converted to hyperlinks by the MUA for HTML mail, and then the
> hyperlinks were converted to plain text in a stupid way, totally
> mangling them.

Ah.  Yes, looks like it -- the HTML version of the message looks better.
Thanks for pointing this out, it shows that the email that was sent was in a 
lot better shape than it first appeared.

  -- Chris

--

Chris Knadle
Chris.Knadle@coredump.us

Re: [mlmmj] Broken email

[Richard Mortimer]

Hi,

On 07/10/2014 08:25, Gavin Henry wrote:
> Here's the raw email:
>
> http://paste.scsys.co.uk/428484
>
> We're testing with prefix, footer and customerheaders (have now
> removed any trailing newlines and will test again):
>
> cat prefix
> [NOC Alerts]
>
> cat customheaders
> X-Mailinglist: noc-alerts
> precedence: bulk
> precedence: list
> List-Id: <noc-alerts>
> List-Unsubscribe: <mailto:noc-alerts+unsubscribe@lists.suretec.net>,
> <http://lists.suretec.net/?list=noc-alerts>
> List-Owner: Suretec Systems Ltd.
>

I suspect that there is an empty line at the end of the customheaders 
file as Ben suggested earlier. That matches with the blank line in your 
raw email (the Message-Id, From and Date headers were added by 
subsequent mail systems after it left mlmmj).

Regards

Richard

>
> cat footer
>

Re: [mlmmj] Broken email

[Chris Knadle]

On Tuesday, October 07, 2014 08:25:42 Gavin Henry wrote:
> Here's the raw email:
> 
> http://paste.scsys.co.uk/428484

Within the email headers there's a blank line between the Date header and the 
MIME-Version header; a blank line after the headers is the usual breakpoint 
for where the body of the email starts.  I think this explains why the body of 
the email starts with the MIME-Version header.

> We're testing with prefix, footer and customerheaders (have now
> removed any trailing newlines and will test again):

There's another oddity: there are TWO Date headers; one after headers added by 
MLMMJ and one that looks like comes from the mail client, and the Date headers 
differ in time.  Additionally not all of the Received headers are contiguous 
and that's unusual.  I suspect that there may be an Exim misconfiguration when 
it comes to handling mailing list mail.

  -- Chris

--

Chris Knadle
Chris.Knadle@coredump.us

Re: [mlmmj] Broken email

[Gavin Henry]

All working, thanks.

Was the newline.

Re: [mlmmj] Broken email

[A. Schulze]

Gavin Henry:

> All working, thanks.
> Was the newline.

maybe the code should check such error conditions?