Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: total-expiry
Date: 31 Jul 1999 10:35:13 -0500	[thread overview]
Message-ID: <wkwvvgq1ce.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Shaun Lipscombe's message of "30 Jul 1999 09:45:34 +0100"

>>>>> "SL" == Shaun Lipscombe <shaun.lipscombe@gasops.co.uk> writes:

SL> I have now decided to mark add to my group params, for mailing list
SL> groups, total-expiry.  After doing this, and then entering/leaving the
SL> group I expected the expiry process to run.  Do I need to mark all the
SL> 'O'ld mail as 'R'ead instead.  I though 'O' was a 'kind of' read
SL> mark.  I have tried doing gnus-summary-expire-articles-now but I
SL> expect that this would only work for messages actually marked as
SL> 'E'xpirable.

I don't know what all the conventions are but 'O'ld mail does not get
expired on my total-expiry groups either.  I notice this when I enter
groups with 'C-u g' and discover a bunch of 'O'ld messages that haven't
been expired.  

Messages that are 'R'ead or 'E'xpirable will vanish at the appropriate time
in total-expire groups.  The manual isn't written completely clear on this
matter.

I also forgot that adaptive scoring and auto-expire conflict with each
other.  If one wants to use adapting, one should either use total-expire
(which doesn't change article marks) or nothing.  The problem is (and this
isn't in the manual) that auto-expire changes the marks _before_ adaptive
scoring peruses the articles to see what is interesting and what is not.

-- 
Jack Vinson
Zippy: Well, I'm on the right planet---everyone looks like me!!!



  parent reply	other threads:[~1999-07-31 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-30  8:45 total-expiry Shaun Lipscombe
1999-07-30 11:10 ` total-expiry Kai Großjohann
1999-07-30 12:28   ` total-expiry Shaun Lipscombe
1999-07-31 15:35 ` Jack Vinson [this message]
1999-08-02  9:27   ` total-expiry Robert Bihlmeyer

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=wkwvvgq1ce.fsf@chevax.ecs.umass.edu \
    --to=vinson@unagi.cis.upenn.edu \
    /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).