Ken Hornstein <[email protected]> writes: >>Not in 1.6; this change is not on the branch: > > I WAS sort of vague on the details; I guess I should have said, "1.6 > if you've got the right configuration, newer versions it will work > automatically." But I didn't want to get bogged down into the weeds here. > >>But I wonder if most people wouldn't prefer that you just stop >>including these; it's funny that the last post to mh-e-users >>before yours was a post about forcing MH-E not to download... :) > > The archives (at least ones that are driven by MHonArc) and I'm told > Gmail does the right thing with those message/external-body parts. > Although that message DID break MHonArc (but any message with RFC 2231 > parameter encoding would have done that; previous messages that didn't > have RFC 2231 encoding were fine). > > What do others think? I kind of think MH-E should be fixed! I know those > are out of fashion now, but I still think they're convenient.
Agreed :-). https://sourceforge.net/p/mh-e/bugs/475/ -- Bill Wohler <[email protected]> aka <[email protected]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
