Re: expiring with gnus-parameters

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Harry Putnam <reader@newsguy.com> writes:

> 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.

Does 'C-c C-M-X' (`gnus-group-expire-all-groups') do the trick? You
could put that in a hook to be called when gnus is started or stopped...