From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: MIME Message Problem
Date: 23 Sep 1999 13:40:35 -0400 [thread overview]
Message-ID: <5b1zbpedbg.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Jake Colman's message of "23 Sep 1999 13:40:22 -0400"
>>>>> "Jake" == Jake Colman <colman@ppllc.com> writes:
Jake> I am forwarding a sample of a type of email that I get fairly
Jake> regularly. When I receive it, it shows up as an
Jake> "application/octet-stream" attachment and is not visible. If I
Jake> press 'C-u g' to see the complete content of the MIME-based
Jake> message, it tells me that it is base64-encoded and all I see is
Jake> a bunch of gibberish (of course). How can I easily see these
Jake> attachments? In almost all cases the attachment is simply a
Jake> forwarded email that the sender wants me to read.
Jake> I'm not sure how this email will get posted to the mailing list
Jake> given that I am forwarding the problem MIME email as a part of
Jake> this message. Hopefully, I am not going to screw anything up.
Press 'i' on the "application/octet-stream" button. Though the
attached message is not treated as message/rfc822, you can see the raw
text.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-09-23 17:40 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 [this message]
1999-09-23 18:58 ` Jake Colman
1999-09-23 19:12 ` Shenghuo ZHU
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=5b1zbpedbg.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).