From: Ted Stern <stern@tera.com>
Subject: reading digests that aren't in traditional digest format
Date: 04 Nov 1999 11:28:50 -0800 [thread overview]
Message-ID: <ycc1za6oy31.fsf@orff.sea.tera.com> (raw)
I'm on a mailing list for a digest that is put together using some homegrown
software. The digests come in a format as follows:
=========================================
Date: Thu, 04 Nov 1999 02:26:25 -0800
From: User Foo <foo@bar.com>
message ...
=========================================
From: User Bar <bar@foo.com>
Date: Thu, 04 Nov 1999 02:26:25 -0800
message ...
without the leading tabs, of course. Pgnus doesn't seem to recognize the
separate messages. Is there a way to tell gnus that the separator is a line
of equals signs rather than a line of dashes?
Ted
--
Tera Computer Company http://www.tera.com
411 First Avenue South, Suite 600 Direct 206/701-2182, Main 701-2000
Seattle, WA 98104-2860 Fax1 206/701-2205, Fax2 701-2500
next reply other threads:[~1999-11-04 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-04 19:28 Ted Stern [this message]
1999-11-04 22:04 ` Kai Großjohann
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=ycc1za6oy31.fsf@orff.sea.tera.com \
--to=stern@tera.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).