From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Re: Problem with mailing-list digests in latest Oort
Date: Tue, 01 Apr 2003 16:15:34 -0500 [thread overview]
Message-ID: <vuowuid7wcp.fsf@csa.bu.edu> (raw)
In-Reply-To: <84adfaxjlk.fsf@lucy.is.informatik.uni-duisburg.de> (Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "Tue, 01 Apr 2003 18:34:15 +0200")
Kai Großjohann writes:
> 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.
That's odd, because I have some saved messages from earlier this week
that worked with older versions of Oort, but they no longer work with
the latest version of Oort out of CVS. I can certainly ask the list
maintainer to update the digests, but has something in the digest code
changed recently (just out of curiousity)?
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "how young are you, how old am i?
emerick@cs.bu.edu /\/ let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats
next prev parent reply other threads:[~2003-04-01 21:15 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
2003-04-01 21:15 ` Emerick Rogul [this message]
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=vuowuid7wcp.fsf@csa.bu.edu \
--to=emerick@cs.bu.edu \
/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).