From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61892 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: Total expiry not working -- is clock skew the problem? Date: Wed, 08 Feb 2006 12:37:09 +0900 Organization: Emacsen advocacy group Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1139370141 569 80.91.229.2 (8 Feb 2006 03:42:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Feb 2006 03:42:21 +0000 (UTC) Original-X-From: ding-owner+m10421@lists.math.uh.edu Wed Feb 08 04:42:16 2006 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F6gDg-0002LX-7p for ding-account@gmane.org; Wed, 08 Feb 2006 04:42:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1F6gDb-0006Od-00; Tue, 07 Feb 2006 21:42:11 -0600 Original-Received: from nas01.math.uh.edu ([129.7.128.39]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1F6g8s-0006OX-00 for ding@lists.math.uh.edu; Tue, 07 Feb 2006 21:37:18 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas01.math.uh.edu with esmtp (Exim 4.52) id 1F6g8q-0003FN-8E for ding@lists.math.uh.edu; Tue, 07 Feb 2006 21:37:18 -0600 Original-Received: from washington.hostforweb.net ([66.225.201.13]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1F6g8p-0003PG-00 for ; Wed, 08 Feb 2006 04:37:15 +0100 Original-Received: from [205.234.185.198] (port=39813 helo=mail.jpl.org) by washington.hostforweb.net with esmtpa (Exim 4.52) id 1F6gAC-0006wO-6P for ding@gnus.org; Tue, 07 Feb 2006 21:38:40 -0600 Original-To: ding@gnus.org X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:dAc3LqL25oyLpzUNdZifM1sIAwA= X-Hashcash: 1:20:060208:ding@gnus.org::n2rCO7mA3WvTk+kT:00003TrO X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - washington.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.6 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:61892 Archived-At: >>>>> In Ted Stern wrote: > One more note -- if I set expiry-wait to 0.0 on a topic, that works > perfectly. It is only non-zero values that do not work. > On 7 Feb 2006 at 08:28 UTC-0800, Ted Stern wrote: >> I started a new job about 100 days ago and had to reconstitute my >> entire Gnus setup, almost from scratch. In my old job, I had total >> expiry turned on and articles expired with no problems. Now I have >> total expiry turned on in the group parameters for an entire topic, >> but nothing has expired automatically since day one. Well, you're talking about nnfolder groups, aren't you? If so, how does the X-Gnus-Article-Number header in old articles look? (You may need to type `t' in the summary buffer.) For example, it should be something like: X-Gnus-Article-Number: 1234 Tue Feb 7 08:28:55 2006 Where 1234 is an article number and the rest is a timestamp. Gnus will look at this timestamp to decide whether to expire the article, so if there's no such header, the time stamp is corrupted or it shows a future date, expiring will not take place. I have no more idea if those are going well. BTW, expiring might be executed in your machine eight hours earlier than the time specified with expiry-wait. It is because the timestamp in the X-Gnus-Article-Number header is made by the current-time-string function and doesn't have a timezone info. For instance: (progn (setenv "TZ" "PST8PDT") ;; -0800 (/ (time-to-seconds (time-since (current-time-string))) 3600)) => 8.000075615555556