From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: OT [Archive techniques] What to do when it gets massive
Date: Tue, 07 Sep 2004 13:12:08 +0200 [thread overview]
Message-ID: <86vfeqqqnr.fsf@ketchup.de.uu.net> (raw)
In-Reply-To: <m3hdr95ed1.fsf@newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> I've been archiving a changing list of nntp and mail messages for a
> very long time.
To split mail archives by month, perhaps the easiest method is to let
the messages expire and to configure expiry such that, instead of
deleting the message, it moves the message to an archive group.
And then you configure Gnus such that the archive location is a
different one every month, and you're all set.
But for nntp this seems to be more difficult. Hm. I'm not sure
what's a good method for this. Perhaps extending gnus-agent-expire to
do something similar to the expiry-target feature for mail?
Kai
prev parent reply other threads:[~2004-09-07 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 1:34 Harry Putnam
2004-08-12 13:29 ` Ted Zlatanov
2004-08-13 1:59 ` Harry Putnam
2004-08-16 17:35 ` Ted Zlatanov
2004-08-16 18:02 ` Harry Putnam
2004-09-02 13:07 ` Kai Grossjohann
2004-09-04 19:37 ` Harry Putnam
2004-09-07 11:12 ` Kai Grossjohann [this message]
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=86vfeqqqnr.fsf@ketchup.de.uu.net \
--to=kai@emptydomain.de \
/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).