From: Colin Rafferty <craffert@ms.com>
Subject: Re: A message/rfc822 test
Date: 17 Dec 1998 10:55:58 -0500 [thread overview]
Message-ID: <vgvww3q9301.fsf@ms.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "17 Dec 1998 10:23:19 -0500"
Karl Kleinpaste writes:
> Colin Rafferty writes:
>> I don't know if you realized it, but the Content-Transfer-Encoding:
>> header of your included message was not included, so it really did end
>> up being quoted-unreadable.
> Hm, not as I received it here....
> If you didn't get this, I suspect some transport has bitten you badly.
My error, it was there.
My problem was a combination of Gnus misleading me and me not reading
accurately. I guess I expected Gnus to handle the MIME stuff
appropriately in the *mm* buffer, and then missed what I expected not
see.
--
Colin
next prev parent reply other threads:[~1998-12-17 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-17 12:30 Robert Bihlmeyer
1998-12-17 14:16 ` Colin Rafferty
1998-12-17 15:23 ` Karl Kleinpaste
1998-12-17 15:55 ` Colin Rafferty [this message]
1998-12-17 15:53 ` Robert Bihlmeyer
1998-12-17 17:39 ` Lars Magne Ingebrigtsen
1998-12-17 23:53 ` Kai.Grossjohann
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=vgvww3q9301.fsf@ms.com \
--to=craffert@ms.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).