Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: expiring with gnus-parameters
Date: Mon, 01 Jul 2013 09:38:37 -0400	[thread overview]
Message-ID: <877ghao0wy.fsf@newsguy.com> (raw)

This is a re-post from the gnus.user list.  I didn't get any answers
there and hoped maybe someone here would have some idea how to do
this. 

-------        ---------       ---=---       ---------      -------- 
From: Harry Putnam <reader@newsguy.com>
Subject: expiring with gnus-parameters
Newsgroups: gmane.emacs.gnus.user
To: info-gnus-english@gnu.org
Date: Thu, 27 Jun 2013 20:35:36 -0400 (3 days, 12 hours, 58 minutes ago)
Message-ID: <87ppv79inb.fsf@newsguy.com>

I've used "gnus-parameters" for yrs to run total-expire with specific
expiry-wait periods on certain groups... but there is always this
problem. 

Gnus wants me to actually open and close these groups before the
expiry takes place.

Some of the groups I rarely if ever have need of opening unless
just to run the expiry code.  I want to keep the backlog... just in
case I should need to use it.

I want to just let these groups move along by themselves and find some
way to trick them into thinking the group has been opened and closed
so total-expire will be run, or maybe just run code periodically (on
auto pilot) that opens and closes the groups.

Maybe there is some completely different way to do this:

Can anyone tell me how to arrange for certain groups to be opened and
closed with no human intervention and for that to be automated?

The result I'm after is to have certain groups maintain a specific
backlog of messages like 90 days worth or whatever, and to
periodically total-expire them down to the actual 90 day backlog,
without me actually doing any intervention.




             reply	other threads:[~2013-07-01 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 13:38 Harry Putnam [this message]
2013-07-01 13:53 ` Eric Abrahamsen
2013-07-01 17:31   ` Harry Putnam

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=877ghao0wy.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.org \
    /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).