Hi David, > > Something for mhfixmsg(1) to correct? > > At this point, I think the trade-off favors manually fixing the > apparently rare offending messages rather than investing effort in > enhancing mhfixmsg.
Fair enough. Either way, I think nmh should baulk at invalid characters in the MIME type so to avoid creating ‘42.2.*’ as it contains shell globbing characters. -- Cheers, Ralph.