[mew-int 3185] Re: problems forwarding messages

[Joao Pedro Pedroso]

[Adding some information to my previous message.]

> In some situations, when forwarding messages with Mew, the text that
> should be forwarded is crippled -- an example follows below.

It seems that when Mew forwards with some messages, the markers of
Base64 are not added.  Below is part of the header of the message
which is not correctly forwarded by mew.

jpp
--
[...]
Received: from smtp.fc.up.pt ([unix socket])
	 by imap.fc.up.pt (Cyrus v2.4.16-Invoca-RPM-2.4.16-1.el6) with LMTPA;
	 Mon, 13 Jan 2014 13:22:47 +0000
X-Sieve: CMU Sieve 2.4
Received: from [10.0.102.112] (jnt.fc.up.pt [10.0.102.112])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.fc.up.pt (Postfix) with ESMTPSA id 144A3240699;
	Mon, 13 Jan 2014 13:22:44 +0000 (WET)
Message-ID: <52D3E8A8.70007 at example.com>
Date: Mon, 13 Jan 2014 13:22:48 +0000
From: =?UTF-8?B?Sm/Do28gTnVubyBUYXZhcmVz?= <friend at example.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23
MIME-Version: 1.0
To: Joao Pedro Pedroso <jpp at example.com>
CC: another.friend at example.com
Subject: Re: Oporto meeting
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

[message text]