Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: suggestion for expiry
Date: 28 Jul 1999 19:09:07 +0100	[thread overview]
Message-ID: <upv1chcjg.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: Simon Josefsson's message of "Wed, 28 Jul 1999 15:28:58 GMT"

Simon> Simon Josefsson <URL:mailto:jas@pdc.kth.se>

0> In <URL:news:iluiu74bxrp.fsf@unikabox.pdc.kth.se>, Simon wrote:

Simon> Max Froumentin <masmef@maths.bath.ac.uk> writes:

>> I don't think that using the filesystem's access-time would work on
>> individual articles in nnfolders.

That's the reason I only mentioned nnml and nnmh ;-)


Simon> Gnus use a date from X-Gnus-Article-Number in nnfolder's when
Simon> expiring articles, it could be modified to update that date to
Simon> indicate when the article actually became eligeble for
Simon> expiring.

Perhaps it could use an Expires header (consistent with news article
format now), with the caveat that when it's changed, it's never made
earlier.  I think some other MUAs generate Expires headers (I'll have
to test this tomorrow, as I'm on my way out now), and so this would
allow those to work.  It would require some checking on incoming mail
(at split time?) to enforce upper and lower bounds on sender-supplied
expire times, with nnmail-expiry-wait being the default.  Then any
significant change to an expirable item pushes the expiry date out.

This has the benefit that the expiry date is visible to the user, too.



  reply	other threads:[~1999-07-28 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-28 13:02 Max Froumentin
1999-07-28 13:08 ` Toby Speight
1999-07-28 14:53   ` Max Froumentin
1999-07-28 15:27     ` Simon Josefsson
1999-07-28 18:09       ` Toby Speight [this message]
1999-07-29 11:50         ` Colin Marquardt
1999-07-28 16:21 ` Thomas Lofgren
1999-07-28 16:25 ` Sam Falkner

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=upv1chcjg.fsf@lanber.cam.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /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).