From: Colin Rafferty <craffert@spspme.ml.com>
Subject: digests and MIME
Date: 20 Nov 1996 09:43:02 -0500 [thread overview]
Message-ID: <ocrpw18ketl.fsf@spssunp.spspme.ml.com> (raw)
Howdy-
It seems that MIME encoded messages that are read as digests are not
being decoded before they are split. I think that they should be.
An example is the FAQ that Steven L. Baur (RIP) just posted. It is
formatted incorrectly if it has not been decoded.
What do people think?
--
Colin Rafferty
next reply other threads:[~1996-11-20 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-20 14:43 Colin Rafferty [this message]
1996-11-20 18:20 ` Steven L Baur
1996-11-20 20:45 ` Colin Rafferty
1996-11-20 21:34 ` Lars Magne Ingebrigtsen
1996-11-20 23:00 ` Colin Rafferty
1996-11-21 2:26 ` Lars Magne Ingebrigtsen
1996-11-21 5:02 ` Steven L Baur
1996-11-21 5:49 ` Hrvoje Niksic
1996-11-20 22:45 ` Steven L Baur
1996-11-20 23:13 ` Colin Rafferty
1996-11-21 0:15 ` Steven L Baur
1996-11-21 2:29 ` Lars Magne Ingebrigtsen
1996-11-21 6:58 ` Jacob Morzinski
1996-11-21 15:58 ` François Pinard
1996-11-21 16:29 ` Lars Magne Ingebrigtsen
1996-11-21 18:20 ` Steven L Baur
1996-11-21 19:39 ` 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=ocrpw18ketl.fsf@spssunp.spspme.ml.com \
--to=craffert@spspme.ml.com \
--cc=craffert@ml.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).