Re: Strange problem replying to message

[aalinovi]

Thank you, that worked.
And I actually manaaged to impress myself by being able to use mhfixmsg(1) to 
correct it.

In message <9036-1705244612.226485@cATk.GdDq.exgE>, David Levine writes:
>Arthur wrote:
>
>> Yesterday everything worked. Today, trying to reply to a message I get:
>>
>> --------
>> In message <CANCnwiKNNCedEXZVYNLG=3DgwV+aSxnNvNC4wBaAfATAU5W7Quhg@mail.g=
>mail.com>,
>> "B. William via Remind-fans" writes:
>> >SG1tbW0gdGhpcyBsaW5lIGRvZXMgVEhJUyBXRUVLLCArIDMgTU9SRSBXRUVLUyBhbmQgZ2l=
>2ZXMg
>> >dGhlIGRhdGVzOgoKcmVtaW5kIC1zKzQgLXEgLXIgfi8ucmVtaW5kZXJzIHwgY3V0IC1jNi0=
>xMCwx
>
>It looks like the text part of the message that you're replying to was
>not base64-decoded.  You could verify that by viewing the message with
>"show -nocheckmime -showproc less".
>
>If the text part is still encoded, you could decode it in the message itse=
>lf,
>or a copy, with mhfixmsg(1).
>
>I don't know why it would have worked yesterday but not today.
>
>David
>