On October 18, 2001 at 11:34, Doug Porter wrote:
> > It is bogus multipart content. Notice that the boundary
> > specified on the content-type line is "NextPart". This means
> > that "--NextPart" lines are boundary markers. But, in the
> > remainder of the document they're "- --NextPart".
>
> No, the `- --NextPart' is showing up because forw(1) will put a
> `- ' at the beginning of any line that begins with a dash (when
No, regardless of the reason of why "- --NextPart" occurs, the
message, as given, is malformed. What you have stated may help the
original sender of the malformed message to correct the problem
for future messages. Nothing Jon wrote was incorrect.
Since I use MH and nmh, there are things that can make either
mailer from not displaying a message due to some formatting error
that should be easily recovered from, but they do not.
Hence, I defined the following shell (csh) alias to show messages
with no mime processing:
alias sh.m 'show -noshowproc \!* | mhl'
There are probably other methods for nmh, but the above works with MH
and the version of nmh I currently use. This is useful if mh/nmh
cannot grok a malformed MIME message. I also find it useful to use for
MIME messages with attachments if I want to quickly see the text of the
message and avoid the processing overhead of decoding the message.
It would be nice that nmh be modified to fallback to displaying
a message in non-mime processing mode when MIME errors are encountered.
I.e. If some formatting problem exists for an entity, display an
error message, but allow the user to see the entity as if it was
text/plain data.
--ewh
