From: Karl Kleinpaste <karl@justresearch.com>
Subject: MIMEish uudecodable portions are misnumbered.
Date: 23 Nov 1998 16:47:56 -0500 [thread overview]
Message-ID: <vxkn25ijd2r.fsf@beaver.jprc.com> (raw)
If one is looking at a message whose body contains 2 uuencoded images,
so that the message is displayed in the MIMEish manner, the available-
for-viewing parts are misnumbered. E.g., I just experimented with a
couple of messages which have a bit of ordinary text, then 2 images,
with 1 blank line separating text from uuencoding, and separating 1
uuencoding from the other. The display of the body is
intro text
[ 2. image/jpeg (somefilename.jpg)]
[ 4. image/jpeg (someotherfile.jpg)]
"3" is conspicuously absent.
It's not much of a bug, of course, but I am curious as to what would
cause the pseudoMIME analysis to miss "3" somehow.
next reply other threads:[~1998-11-23 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-23 21:47 Karl Kleinpaste [this message]
1998-11-24 4:20 ` Shenghuo ZHU
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=vxkn25ijd2r.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).