From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Broken email
Date: Tue, 07 Oct 2014 06:30:00 +0000 [thread overview]
Message-ID: <54338868.10506@yahoo.com.au> (raw)
In-Reply-To: <CAPcb_GLkCEA6jPGqTE-jOmTax79m4=WoOsFyRSPSpg9bgQFxMA@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2014-10-07 6: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
2014-10-07 6:25 ` Gavin Henry
2014-10-07 6:29 ` Ben Schmidt
2014-10-07 6:30 ` Ben Schmidt [this message]
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=54338868.10506@yahoo.com.au \
--to=mail_ben_schmidt@yahoo.com.au \
--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.