Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!newstop!sun!argv
From: argv@turnpike.Eng.Sun.COM (Dan Heller)
Newsgroups: comp.mail.misc
Subject: Re: timezone names
Message-ID: <143826@sun.Eng.Sun.COM>
Date: 17 Oct 90 19:10:36 GMT
References: <1990Oct16.002131.28178@csis.dit.csiro.au>
Sender: news@sun.Eng.Sun.COM
Organization: O'Reilly && Associates
Lines: 32

In article <1990Oct16.002131.28178@csis.dit.csiro.au> ken@csis.dit.csiro.au (Ken Yap) writes:
> I wish Berkmail would use numeric timezones instead of three letter
> abbreviations in Date: lines. Australian Eastern Standard Time is also
> EST.  (Hey, I didn't pick the abbreviation.) Thus mail sent my friends

Actually, it's AEST, not EST.  But the standards say that timezones
*outside* of the US must use numeric representations, not  the ascii
versions.  Conversely, Mail *in* the US must use the 3-letter ascii
abbreviations.

why are you using Berkmail!?

> Down with TLAs, let's go numeric.
let's go with standards...
But the -real- solution is to allow the MTA to supply the Date: header.

> Grumble. Yet another reason to prefer MH.
MH has nothing to do with this.  In fact, if MH is adding a Date: header,
it's yet another reason *not* to use MH.  Mush provides a date header
by default because there are many non-rfc compliant MTAs out there that
people are using and Mush has to work with them.  You can (and should)
configure this out before building Mush if you use 822-complaint MTAs.
Admittedly, the current version of Mush does not produce the correct
822-Date header for sites outside the US (because it uses the timezone
abreviations rather than the numeric), but this will be fixed in the
next patch being posted later this week.

--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.