From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: MIME Message Problem
Date: 23 Sep 1999 15:12:04 -0400 [thread overview]
Message-ID: <5bk8phcuij.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Jake Colman's message of "23 Sep 1999 14:58:09 -0400"
>>>>> "Jake" == Jake Colman <colman@ppllc.com> writes:
Jake> But why is this necessary? Is this the way it us _supposed_ to
Jake> work? If pressing 'i' allows me to see the message, that's
Jake> great. I'd just like to understand what is going on?
Gnus does not display it, because Gnus does not know what the content
of attachment actually is. Content-type application/octet-stream is
"a catch-all type, this is the most widely abused MIME content-type".
If the sender want to you to read the attachment, message/rfc822,
instead of application/octet-stream, should be used as content-type
just like what Gnus does, but some MUAs use the later.
Pressing 'i' on MIME button forces the attachment show as plain text.
I guess it is the last easy resort.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-09-23 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-23 17:40 Jake Colman
1999-09-23 17:40 ` Shenghuo ZHU
1999-09-23 18:58 ` Jake Colman
1999-09-23 19:12 ` Shenghuo ZHU [this message]
1999-09-23 19:14 ` David S. Goldberg
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=5bk8phcuij.fsf@giga.cs.rochester.edu \
--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).