Re: Total expiry not working -- is clock skew the problem?

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> In <lspy80nozf3.fsf@drip.ca.boeing.com> 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