Re: base64 message body decode when replying???

Kevin Cosgrove skrev:
> On 22 March 2010 at 15:43, [email protected] wrote:
>
>   
>>> I just can't figure this out.  I've done quite a bit of
>>> manual reading and net searching on this, but can't seem to
>>> find what I'm after.  Anyone know how to achieve what I'm
>>> after?
>>>       
>> This is a known deficiency in nmh (is anybody using any other
>> mh variants under the exmh hood anymore?).  The basic problem
>> is the repl command is not MIME-aware.
>>     
>
> That makes sense.  Has anyone scripted a filter, maybe triggered
> via ~/.mh_profile, which pre-formats the message before handing
> off the content to the actual repl?  I'm not trying to handle
> the entire world of MIME via repl, just base64 encoding for
> now.  I'm happy to prefilter the messages in place before
> replying.  I do that now to get rid of Outlook's special version
> of quoted-printable.
>
>   
Solutions (in order of incresing sanity):

1) Google for a recipe to make a button to get the incoming, decoded 
text into the clip-board, and use some kind of "paste as quote" command 
(also available on the web). I'm sure someone on this list has a recipe 
for this that works in the current exmh.

2) Filter all incoming mail, (.procmailrc or something such), and 
reformat text/whatever from base64. Keep all text parts in your mailbox 
in plain 8-bit to enable grepping and such in your mailbox. Remember to 
rewrite the mime headers to reflect the updated coding.

3) Use a different mail-client (sad to say, this is the least 
frustrating in the long run).
    ---
It is actually fairly easy to use readily available command-line tools 
to unpack and rewrite such emails. Last i remember i found what I needed 
in the mencoder package (or maybe not). There may also  be perl 
building-blocks available. However, whenever you get a new account or a 
new machine you need to research the the proper commands and syntax and 
tweak until it runs smoothly. Since this normally happens only every 
three years or so, the exact steps to get option 1 running will be 
forgotten (and slightly different), so depending on your stubborn-ness 
and nerd-factor you will most likely end up with solution 3 after 10-15 
years of working against the flow of "good enough" solutions out there. 
Frequently politics and ideas about "The rigtht thing" get into the 
details of what command-line switches are available in such tools, 
making for endless frustration.