From: Chris Knadle <Chris.Knadle@coredump.us>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Broken email
Date: Tue, 07 Oct 2014 08:43:11 +0000 [thread overview]
Message-ID: <6217178.v1xnFSImh8@trelane> (raw)
In-Reply-To: <CAPcb_GLkCEA6jPGqTE-jOmTax79m4=WoOsFyRSPSpg9bgQFxMA@mail.gmail.com>
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
next prev parent reply other threads:[~2014-10-07 8:43 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
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 [this message]
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=6217178.v1xnFSImh8@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.