From: Chris Knadle <Chris.Knadle@coredump.us>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Broken email
Date: Tue, 07 Oct 2014 03:30:28 +0000 [thread overview]
Message-ID: <1578751.LKacbMl1qM@trelane> (raw)
In-Reply-To: <CAPcb_GLkCEA6jPGqTE-jOmTax79m4=WoOsFyRSPSpg9bgQFxMA@mail.gmail.com>
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
next prev parent reply other threads:[~2014-10-07 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 23:21 [mlmmj] Broken email Gavin Henry
2014-10-07 3:30 ` Chris Knadle [this message]
2014-10-07 6:25 ` Gavin Henry
2014-10-07 6:29 ` Ben Schmidt
2014-10-07 6:30 ` Ben Schmidt
2014-10-07 7:25 ` Gavin Henry
2014-10-07 7:38 ` Chris Knadle
2014-10-07 8:11 ` Richard Mortimer
2014-10-07 8:43 ` Chris Knadle
2014-10-07 19:28 ` Gavin Henry
2014-10-07 19:50 ` A. Schulze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1578751.LKacbMl1qM@trelane \
--to=chris.knadle@coredump.us \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.