Tech Insider					     Technology and Trends


			      USENET Archives

From: al...@primenet.com (Alan Hamilton)
Subject: Exchange timezones
Date: 1995/11/09
Message-ID: <47trqp$hbl@nnrp3.news.primenet.com>#1/1
X-Deja-AN: 118997171
organization: Primenet
newsgroups: comp.os.ms-windows.win95.misc

	I've noticed a problem MS Exchange has with certain "Date:" lines.  
Every so often I get a date line like

Date: Thu, 9 Nov 1995 4:07:19 -0600 (CST)

Apparently, having both the -600 and CST confuses Exchange.  It considers 
this time to be GMT, and thus converts it to the wrong time when converting 
to my local timezone (MST).  I realize that RFC822 doesn't allow this format, 
but it seems to be common.  (For that matter, RFC822 only allows US 
timezones, plus UT, GMT, and single letter military zones.  Zones like CET 
aren't allowed.)

Since I'd like to sort my mail by the Sent time, this is a problem.

--
      /
  /  *  /  Alan Hamilton
 *     *   al...@primenet.com

From: egg...@twinsun.com (Paul Eggert)
Subject: Re: Exchange timezones
Date: 1995/11/10
Message-ID: <4812go$io9@shade.twinsun.com>#1/1
X-Deja-AN: 119074993
references: <47trqp$hbl@nnrp3.news.primenet.com>
organization: Twin Sun Inc, El Segundo, CA, USA
newsgroups: comp.os.ms-windows.win95.misc

al...@primenet.com (Alan Hamilton) writes:

> Date: Thu, 9 Nov 1995 4:07:19 -0600 (CST)

> Apparently, having both the -600 and CST confuses Exchange.  It considers 
> this time to be GMT, and thus converts it to the wrong time when converting 
> to my local timezone (MST).  I realize that RFC822 doesn't allow this format, 

The format is wrong not because of the timezone, but because there's a
missing leading zero.  The time should be `04:07:19' not `4:07:19'.

RFC 822 does allow numeric timezones.  And RFC 1123 section 5.2.14
(which amends RFC 822) recommends them over traditional US names like `CST'.

From: al...@primenet.com (Alan Hamilton)
Subject: Re: Exchange timezones
Date: 1995/11/13
Message-ID: <488dgb$c8v@nnrp3.news.primenet.com>#1/1
X-Deja-AN: 119360640
references: <47trqp$hbl@nnrp3.news.primenet.com> <4812go$io9@shade.twinsun.com>
organization: Primenet
newsgroups: comp.os.ms-windows.win95.misc

In article <4812go$...@shade.twinsun.com>,
   egg...@twinsun.com (Paul Eggert) wrote:
>al...@primenet.com (Alan Hamilton) writes:
>
>> Date: Thu, 9 Nov 1995 4:07:19 -0600 (CST)
>
>> Apparently, having both the -600 and CST confuses Exchange.  It considers 
>> this time to be GMT, and thus converts it to the wrong time when 
converting 
>> to my local timezone (MST).  I realize that RFC822 doesn't allow this 
format, 
>
>The format is wrong not because of the timezone, but because there's a
>missing leading zero.  The time should be `04:07:19' not `4:07:19'.
>
>RFC 822 does allow numeric timezones.  And RFC 1123 section 5.2.14
>(which amends RFC 822) recommends them over traditional US names like `CST'.

I meant that RFC822 allows for -600 or CST, but not both and not a zonename 
in parenthesis.  Exchange seems to handle 04 vs. 4 fine.


--
      /
  /  *  /  Alan Hamilton
 *     *   al...@primenet.com

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO v IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
research.

Electronic mail:			       WorldWideWeb:
   tech-insider@outlook.com			  http://tech-insider.org/