From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Multi-part MIME problems
Date: 21 Nov 1999 11:39:41 -0500 [thread overview]
Message-ID: <2n903riysy.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Graham Todd's message of "20 Nov 1999 16:20:46 -0500"
>>>>> "Graham" == Graham Todd <gtodd@yorku.ca> writes:
[...]
Graham> I copied the two offending messages (they're not too personal I hope
Graham> ;-) to:
Graham> ftp://ftp.equilibrio.qc.ca/pub/GnusStuff/
Graham> If anyone wants to read them. If I download a message and do the
Graham> following:
Graham> ~$ echo "From nobody Sat Nov 20 15:27:25 1999" >> Mail/Somefolder
Graham> ~$ cat MIME-message-1 >> Mail/Somefolder
Graham> this puts the message in a mailfolder where I can read it. Reading the
Graham> folder with Pine I see the message and all the attached images and I
Graham> can launch the viewer of my choice without a problem. Pine shows the
Graham> message size as ~ 380k.
Graham> In Gnus the message appears in the folder's Summary Buffer but shows
Graham> the size as 5 megs. The attachements don't show up in the Article
Graham> buffer when I read the message though. I thought perhaps the message
Graham> was just too big (the actual message file for MIME-message-1 is ~380 k
Graham> but as noted Gnus seems to "expand" its size to 5 megabytes in the
Graham> group buffer). However a smaller message prepared in the same way has
Graham> the same problem.
[...]
By default, Gnus report the number of lines not the number of
characters. What you saw is 5326 lines not 5 megs.
$ wc MIME-message-1
5360 5669 382907 MIME-message-1
The attachments don't show up because the content-type is
multipart/related, however W3 does not render it well. You can type
`C-d' on the summary, an ephemeral group will show you all the parts
well.
--
Shenghuo
prev parent reply other threads:[~1999-11-21 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-20 21:20 Graham Todd
1999-11-21 16:39 ` Shenghuo ZHU [this message]
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=2n903riysy.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).