From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Problem with mailing-list digests in latest Oort
Date: Tue, 01 Apr 2003 18:34:15 +0200 [thread overview]
Message-ID: <84adfaxjlk.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <vuopto65pgy.fsf@csa.bu.edu>
Emerick Rogul <emerick@cs.bu.edu> writes:
> . [ 178: Aimee Mann listproc ] <* mixed> MANNLIST digest 1773
> . [ 12: Aimee Mann listproc ] <1 text>
> . [ 156: Aimee Mann listproc ] <2.* digest>
> . [ 93: Aimee Mann listproc ] <2.1 text>
> . [ 34: Aimee Mann listproc ] <2.2 text>
> . [ 22: Aimee Mann listproc ] <2.3 text>
According to the text of the message, this looks correct.
The list server is sending MIME that makes Gnus render like this.
Look at the source code of the message (C-u g). You'll see that the
whole thing is multipart/mixed, and each message starts with a
separator and then an empty line and then the message itself.
Before the empty line there should be a line like
Content-Type: message/rfc822
then Gnus would grok the contents. But since the Content-Type header
is missing, text/plain is assumed.
--
A preposition is not a good thing to end a sentence with.
next prev parent reply other threads:[~2003-04-01 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 13:14 Emerick Rogul
2003-04-01 16:34 ` Kai Großjohann [this message]
2003-04-01 21:15 ` Emerick Rogul
2003-04-02 11:42 ` Kai Großjohann
2003-04-01 17:24 ` 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=84adfaxjlk.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).