From: Jake Colman <colman@ppllc.com>
Subject: Expiring Old Messaes
Date: 10 Nov 2000 14:50:34 -0500 [thread overview]
Message-ID: <76puk3ip2t.fsf@newjersey.ppllc.com> (raw)
I recently discovered the joys of auto-expiry and have configured a numbr of
groups to auto-expire as needed. The problem is that some of these groups
contain hundreds of read messages. How do I automagically mark them as
expirable without manually marking or rereading them?
TIA!
--
Jake Colman
Principia Partners LLC Phone: (201) 946-0300
Harborside Financial Center Fax: (201) 946-0320
902 Plaza II Beeper: (800) 928-4640
Jersey City, NJ 07311 E-mail: colman@ppllc.com
E-mail: jcolman@jnc.com
web: http://www.ppllc.com
microsoft: "where do you want to go today?"
linux: "where do you want to go tomorrow?"
BSD: "are you guys coming, or what?"
next reply other threads:[~2000-11-10 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 19:50 Jake Colman [this message]
2000-11-11 10:43 ` 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=76puk3ip2t.fsf@newjersey.ppllc.com \
--to=colman@ppllc.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).