Bill Wohler writes:
I was just skimming this thread until I hit MH-E :-). Since Eric is
using MH-E and seems to have a bleeding edge nmh, I'll trust him to
pick up any problems in MH-E due to changes he makes.
Well, I'd never introduce a problem that broke MH-E for
*me* anyway! "Works for me" is all too common :(.
I thought nmh already handled RFC 2047 decoding in the Subject and
recipient fields, no? If you think MH-E is doing some decoding, please
send me a sample message that demonstrates what nmh doesn't handle
that MH-E does and I'll check the code.
It can decode, but doesn't by default because it apparently has
no way to *encode*. I let MH-E handle that, so am perfectly
happy adding the decode calls to my repl*comps files.
--
Eric Gillespie <*> epg(_at_)pretzelnet(_dot_)org
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
http://lists.nongnu.org/mailman/listinfo/nmh-workers