References: <5cd7f16b6435bf40b67862e29e1a516e.squirrel@webmail.plus.net>
 <87k2gchjia.fsf@qmul.ac.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <87k2gchjia.fsf@qmul.ac.uk>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <B79EEECE-417D-4CED-8E4E-393E87C3AFE9@bubblegen.co.uk>
Cc: notmuch@notmuchmail.org
From: Matthew Lear <matt@bubblegen.co.uk>
Subject: Re: Missing headers when forwarding html message as RFC822
Date: Sat, 23 Jul 2016 13:30:41 +0100
To: Mark Walters <markwalters1009@gmail.com>
Precedence: list

Hi Mark. I will do, but would you mind sending me one of your test messages?=
 At least that way, I can test against something that is 'known working'.
Thanks,
  Matt

> On 23 Jul 2016, at 08:59, Mark Walters <markwalters1009@gmail.com> wrote:
>=20
>=20
> Hi
>=20
> I have tried several cases, including generating a message with just the
> two parts [ multipart/related ] [ text/html ] and forwarding that, and
> they all work for me. Can you provide a test message where it fails?
>=20
> Also what version of emacs are you running? I think all the rfc822
> forwarding is handled by emacs/gnus message-mode
>=20
> Best wishes
>=20
> Mark
>=20
>=20
>=20
>> On Fri, 22 Jul 2016, Matthew Lear <matt@bubblegen.co.uk> wrote:
>> Hi,
>>=20
>> With notmuch built from very recent git (sha 3a45d29) it would seem that
>> when forwarding an HTML only message as RFC822, once received, the messag=
e
>> does not have any headers and notmuch-show merely displays 'Date: Thu, 01=

>> Jan 1970 00:00:00 +0000'. I've stripped my .emacs back to a bare minimum
>> configuration and the behaviour is the same.
>>=20
>> With a message (incidentally sent by MS Outlook) that contains the
>> following parts:
>>=20
>> [ multipart/related ]
>> [ text/html ]
>>=20
>> Once forwarded as RFC822 by notmuch and received, it is displayed by
>> notmuch-show as:
>>=20
>> [ message/rfc822 ]
>> Date: Thu, 01 Jan 1970 00:00:00 +0000
>>=20
>> [ multipart/mixed ]
>> [ multipart/related ]
>> [ text/html ]
>>=20
>> While with a message that contains the following parts:
>>=20
>> [ multipart/mixed ]
>> [ text/plain ]
>>=20
>> Once forwarded as RFC822 by notmuch and received, it is displayed by
>> notmuch-show as:
>>=20
>> [ message/rfc822 ]
>> From: xxxx
>> Subject: xxxx
>> To: xxxx
>> Date: Fri, 15 Jul 2016 17:48:17 +0000
>>=20
>> [ multipart/mixed ]
>> [ text/plain ]
>>=20
>> So the headers are missing in the first case. I'm sure this is a regressi=
on.
>>=20
>> Can anybody verify this?
>> Cheers,
>> --  Matt
>>=20
>>=20
>> _______________________________________________
>> notmuch mailing list
>> notmuch@notmuchmail.org
>> https://notmuchmail.org/mailman/listinfo/notmuch