From: Jason Molenda <jason-swarelist@molenda.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sourceware.cygnus.com
Subject: Re: RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been digests? (fwd)
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000531135132.A16989@shell17.ba.best.com> (raw)
In-Reply-To: <Pine.BSF.4.21.0005302202140.93459-100000@deneb.dbai.tuwien.ac.at>
On Tue, May 30, 2000 at 10:03:38PM +0200, Gerald Pfeifer wrote:
> A few days ago I forwarded another message by David, which Jason and/or
> Jeff were so kind to have a look at; perhaps the following provides the
> crucial hint?
>
I'll be honest - I don't have a clue. I know next to nothing about
how ezmlm constructs its digests. Maybe it has something to do
with the messages in the archive? I don't know.
ezmlm-get(1) says the following. No -f option is being specified for
the gcc list, so the default (m) should be the one used. From
/qmail/lists-gcc/gcc/editor:
|/qmail/ezmlm/ezmlm-get '/qmail/lists-gcc/gcc' || exit 0
From the man page:
-f is an optional format specifier for -get, -thread, and
-dig requests. It is allowed, but ignored for -index
requests. Currently, the following are allowed:
r rfc1153. This is a ``plain'' non-MIME format for
dumb clients.
m (Default.) MIME multipart/digest with a subset of
ordered headers sorted. Currently, the following
headers are included in the order listed: Date:,
To:, From:, Reply-To:, Cc:, MIME-Version:, Content-
Type:, Message-ID:, and Keywords:. This can be
customized with the optional file dir/digheaders,
which should contain the desired headers up to but
not including the colon.
The format is no longer compliant with rfc1153, as
the rfc1153 format is incompatible with rfc2046,
which which the format is (should be) compatible.
x MIXED: This is the same as the default MIME format,
except that the Content-Type is multipart/mixed.
This helps circumnavigate a Pine bug: when the
digest is content-transfer-encoded, Pine will
refuse to display the initial text/plain part of a
multipart/digest message, but display the same part
of a multipart/mixed message. Some MUAs for some
strange reason treat the two multipart formats
differently. In some cases, ``x'' works better than
``m''.
v VIRGIN: This is MIME multipart/digest with messages
returned without any header filtering.
n NATIVE: This is VIRGIN format without threading,
i.e. messages are presented in numerical order and
the message index is suppressed.
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason-swarelist@molenda.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sourceware.cygnus.com
Subject: Re: RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been digests? (fwd)
Date: Wed, 31 May 2000 13:52:00 -0000 [thread overview]
Message-ID: <20000531135132.A16989@shell17.ba.best.com> (raw)
Message-ID: <20000531135200.i6Dw2OEpSNrtm_xfkM5IdP4fLIej_0qgZem8FHLJzK8@z> (raw)
In-Reply-To: <Pine.BSF.4.21.0005302202140.93459-100000@deneb.dbai.tuwien.ac.at>
On Tue, May 30, 2000 at 10:03:38PM +0200, Gerald Pfeifer wrote:
> A few days ago I forwarded another message by David, which Jason and/or
> Jeff were so kind to have a look at; perhaps the following provides the
> crucial hint?
>
I'll be honest - I don't have a clue. I know next to nothing about
how ezmlm constructs its digests. Maybe it has something to do
with the messages in the archive? I don't know.
ezmlm-get(1) says the following. No -f option is being specified for
the gcc list, so the default (m) should be the one used. From
/qmail/lists-gcc/gcc/editor:
|/qmail/ezmlm/ezmlm-get '/qmail/lists-gcc/gcc' || exit 0
From the man page:
-f is an optional format specifier for -get, -thread, and
-dig requests. It is allowed, but ignored for -index
requests. Currently, the following are allowed:
r rfc1153. This is a ``plain'' non-MIME format for
dumb clients.
m (Default.) MIME multipart/digest with a subset of
ordered headers sorted. Currently, the following
headers are included in the order listed: Date:,
To:, From:, Reply-To:, Cc:, MIME-Version:, Content-
Type:, Message-ID:, and Keywords:. This can be
customized with the optional file dir/digheaders,
which should contain the desired headers up to but
not including the colon.
The format is no longer compliant with rfc1153, as
the rfc1153 format is incompatible with rfc2046,
which which the format is (should be) compatible.
x MIXED: This is the same as the default MIME format,
except that the Content-Type is multipart/mixed.
This helps circumnavigate a Pine bug: when the
digest is content-transfer-encoded, Pine will
refuse to display the initial text/plain part of a
multipart/digest message, but display the same part
of a multipart/mixed message. Some MUAs for some
strange reason treat the two multipart formats
differently. In some cases, ``x'' works better than
``m''.
v VIRGIN: This is MIME multipart/digest with messages
returned without any header filtering.
n NATIVE: This is VIRGIN format without threading,
i.e. messages are presented in numerical order and
the message index is suppressed.
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been digests?(fwd) Gerald Pfeifer
2000-05-30 13:03 ` Gerald Pfeifer
2000-12-30 6:08 ` Jason Molenda [this message]
2000-05-31 13:52 ` RE2: Re: Why have the prior 2 "gcc Digest" emails *not* been digests? (fwd) Jason Molenda
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=20000531135132.A16989@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sourceware.cygnus.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).