From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/24529 Path: main.gmane.org!not-for-mail From: Toby Speight Newsgroups: gmane.emacs.gnus.general Subject: Re: suggestion for expiry Date: 28 Jul 1999 14:08:02 +0100 Organization: Citrix Systems (Cambridge) Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035162081 9240 80.91.224.250 (21 Oct 2002 01:01:21 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 01:01:21 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id JAA00125 for ; Wed, 28 Jul 1999 09:12:52 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.3/8.9.3) with ESMTP id IAB08295; Wed, 28 Jul 1999 08:12:38 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 28 Jul 1999 08:13:34 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id IAA04034 for ; Wed, 28 Jul 1999 08:13:15 -0500 (CDT) Original-Received: from ironside.ansa.co.uk (ironside.ansa.co.uk [192.5.254.44]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id JAA00110 for ; Wed, 28 Jul 1999 09:12:08 -0400 (EDT) Original-Received: from lanber.cam.citrix.com (LANBER.ansa.co.uk [10.70.1.235]) by ironside.ansa.co.uk (Netscape Mail Server v2.02) with ESMTP id AAA65 for ; Wed, 28 Jul 1999 14:12:49 +0100 Original-To: ding@gnus.org Original-Lines: 14 In-Reply-To: Max Froumentin's message of "Wed, 28 Jul 1999 13:03:44 GMT" X-Author-Info: Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:24529 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:24529 Max> Max Froumentin 0> In , Max wrote: Max> May I suggest that expiry be based on another date than the Max> message's 'Date:' field? Rather, another field storing the Max> date of the last time the message was read seems to me more Max> appropriate. What do people think? I'm not sure another field would be necessary for nnml or nnmh: they could use the access-time from the filesystem (on Unix-like filesystems; I don't know whether other OSes have a comparable concept). If it were implemented, I'd be happier.