From: Karl Kleinpaste <karl@justresearch.com>
Subject: Re: try to toggle this one. Go ahead, I dare ya.
Date: 17 Dec 1998 10:28:33 -0500 [thread overview]
Message-ID: <vxkiufapz32.fsf@beaver.jprc.com> (raw)
In-Reply-To: Harry Putnam's message of "17 Dec 1998 06:45:08 -0800"
Wes Hardaker <wjhardaker@ucdavis.edu> writes:
>> Enclosed is a uuencoded message that has a mime encapsulation of a
>> message, which in turn has one...
Harry Putnam <reader@newsguy.com> writes:
> What have I got set wrong? Your message came through as what is
> apparently an inline Uuencoded message.
I'm with Harry on this one. All I see is the uuencoded file,
displayed inline, which is proper, considering that the segment in
question contains these headers:
Content-Disposition: inline;
filename="~/tmp/msg.uu"
Content-Description: uuencoded mail message
There's nothing in there to indicate that anything fancy should be
done about an enclosed message/rfc822. There's no encoding
information at all; it's just an inline file, displayed as-is.
next prev parent reply other threads:[~1998-12-17 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-17 0:38 Wes Hardaker
1998-12-17 14:45 ` Harry Putnam
1998-12-17 15:28 ` Karl Kleinpaste [this message]
1998-12-18 15:44 ` Wes Hardaker
1998-12-18 17:25 ` Jack Vinson
1998-12-19 21:59 ` 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=vxkiufapz32.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).