Tom R wrote: > $ command show +nmh/test 2 > mhshow: invalid parameter in message 2's Content-Type: field > parameter ; charset=UTF-8 (error detected at offset 0)
Here's the offending line:
Content-Type: text/calendar; method=REQUEST;; charset=UTF-8
Removing the second semicolon fixes it. mhfixmsg relies on the nmh MIME
parser, which trips over this. At this point, with just one report, I don't
think it's worth the effort to try to handle this case.
David
