Re: [Nmh-workers] mhfixmsg suggestion

[David Levine]

> >I don't think we want -remove text/plain because that would
> >remove all text/plain parts.
> 
> Hm, well ... if you have a "simple" message that is just a
> multipart/alternative, maybe you do?

I'm coming around to that way of thinking.  Removing all
text/plain subparts from multipart/alternatives that have
another subpart wouldn't be too bad.  A part number would
preclude asynchronous handling, which I want to keep as noted
below.

I had briefly thought of keeping the bogus text/plain subparts
in the message, but I think that's more trouble than it's
worth.  It's easy enough to keep a backup of the original
message per the example in the mhfixmsg man page.

Ralph and Norm, I like the idea of exploding/editing/imploding,
but I think that belongs in enhancements to mhstore and
send/post/front ends.  I view mhfixmsg as being most useful
when it can be invoked asynchronously.  I want to put in a fix
once, not every time I get a broken message.  procmail can
restrict to specific senders or whatever so it can target
specific problems.

David