From: Karl Kleinpaste <karl@justresearch.com>
Subject: broken MIME parse? also, another MIME error thrown
Date: 17 Nov 1998 17:32:01 -0500 [thread overview]
Message-ID: <vxkd86mx866.fsf@beaver.jprc.com> (raw)
In p0.48 + last evening's patch to fix `2 b' failing in *Article*...
I got a message off a mailing list which had MIME-Version and
Content-Type headers, including a boundary="..." spec, but then there
were no parts in the message containing that boundary. The result was
that the message did not display at all. Also, not recognizing the
nature of the problem at first, I tried `1 b' to render something I
thought must be hidden, which threw this error:
Signaling: (wrong-type-argument integer-or-marker-p nil)
gnus-mime-display-alternative(nil nil (#<marker at 1214 in *Article*>) 1)
(lambda (handles) (gnus-mime-display-alternative (quote nil) nil (quote ...) 1))(nil)
gnus-article-press-button()
gnus-article-view-part(1)
call-interactively(gnus-article-view-part)
Disregarding the error thrown, is this proper behavior in the MIME
context, that the entire content be left unrendered in the absence of
boundaries?
E.g., given source for a message:
________________
From: nobody@no.where
To: karl
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01BE1207.AEDC5960"
Subject: MIME failure test
Random junk here.
In fact, a lot more random garbage here.
________________
I fed that to "sendmail -t"; the result in Gnus was:
________________
X-From-Line: nobody@no.where.jprc.com Tue Nov 17 17:26:57 1998
Return-Path: <nobody@no.where.jprc.com>
Received: (from karl@localhost)
by beaver.jprc.com (8.8.7/8.8.7) id RAA05548;
Tue, 17 Nov 1998 17:26:56 -0500
Date: Tue, 17 Nov 1998 17:26:56 -0500
From: nobody@no.where.jprc.com
Message-Id: <199811172226.RAA05548@beaver.jprc.com>
To: karl@beaver.jprc.com
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01BE1207.AEDC5960"
Subject: MIME failure test
Lines: 4
Xref: beaver.jprc.com mailer-daemon:30887
Random junk here.
In fact, a lot more random garbage here.
________________
But it displays as just:
________________
From: nobody@no.where.jprc.com
Subject: MIME failure test
To: karl@justresearch.com
X-Sent: 2 minutes, 49 seconds ago
1.
________________
next reply other threads:[~1998-11-17 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 22:32 Karl Kleinpaste [this message]
1998-11-18 1:09 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vxkd86mx866.fsf@beaver.jprc.com \
--to=karl@justresearch.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).