From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: ding@gnus.org
Subject: Re: try to toggle this one. Go ahead, I dare ya.
Date: 18 Dec 1998 07:44:40 -0800 [thread overview]
Message-ID: <x7lnk5xxnb.fsf@des.castles.com> (raw)
In-Reply-To: Harry Putnam's message of "17 Dec 1998 06:45:08 -0800"
>>>>> On 17 Dec 1998 06:45:08 -0800, Harry Putnam <reader@newsguy.com> said:
Harry> What have I got set wrong? Your message came through as what is
Harry> apparently an inline Uuencoded message.
Right. Sorry for the mis-lead. You should uu-decoded it and store it
in a nnml folder and view it there...
I wasn't sure the proper method of reproducing the problem, so I
simply uuencoded an offending message and mailed it off (something
Lars has previously suggested for submitting problematic messages)...
It's not expected you try to read "my message", but rather you
de-encode the message in side and try to read "that one".
(It's more of a bug report to Lars than anything else, but it was a
topic that I thought might warrent a discussion, hence this list
instead of a bug report).
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-12-18 15:44 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
1998-12-18 15:44 ` Wes Hardaker [this message]
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=x7lnk5xxnb.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
--cc=ding@gnus.org \
/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).