Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site ulysses.UUCP
Path: utzoo!linus!decvax!harpo!floyd!vax135!ariel!hou5f!hou5e!hou5d!hogpc!houxm!hocda!spanky!burl!duke!mcnc!smb@ulysses.UUCP (Steven Bellovin)
From: smb@ulysses.UUCP
Newsgroups: net.news
Subject: Re: dates on articles
Message-ID: <537@ulysses.UUCP>
Date: Tue, 9-Aug-83 17:11:27 EDT
Article-I.D.: ulysses.537
Posted: Tue Aug  9 17:11:27 1983
Date-Received: Wed, 10-Aug-83 18:52:27 EDT
References: <467@ru-cs44.UUCP>
Organization: Bell Labs, Murray Hill
Lines: 11

Cathy Garlick's diagnosis appears to be correct.  Giving getdate a string
containing a date and a day-name means "find the first occurrence of that
day-name on or after the given date".  Thus, if there's a timezone problem,
the date portion could easily yield the next day, in which case specifying
a day-name could move the date even further off.

The root problem is indeed that BST was called "Bering Standard Time";
the list of timezone names was taken from RFC733, which had never heard
of British Summer Time.  It should be an easy fix....

		--Steve Bellovin