Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!ucivax!gateway From: SOLOMON%CS.WISC.EDU@cunyvm.cuny.edu Newsgroups: comp.protocols.iso.x400 Subject: Re: Time zones again. Message-ID: <9009011939.aa19391@ICS.UCI.EDU> Date: 2 Sep 90 02:47:52 GMT Lines: 31 Approved: usenet@ICS.UCI.EDU Comments: +++ Changed X.430-Header: +++ x *** GATEWAY INFO: "ADMVM at DFNGATE" was the real originator of this note. TO: x FROM: "Marvin Solomon" x MESSAGE ID: ;9008311153.AA02971(a)gjetost.cs.wisc.edu x CC: x CROSS REF: ;13032.652079954(a)nma.com ;90 1:57 am SENSITIVITY: NORMAL x IMPORTANCE: NORMAL x BODY TYPE: IA5TEXT RFC-822-Headers: X-Mailer: ELM [version 2.2 PL10] BODY TYPE: IA5TEXT > > Aw, Shux Christian -- It seems pretty obvious that a .au top level > Originator Address is virtually certain not be from Miami, Boston, > Chicago, New Oleans, or anywhere in the .us! > > Also, .uk (or .gb) are pretty sure to not be in alaska, while .edu is > pretty certain to not be in the UK (or GB). > > So why not look at the Origiantors address? Best...\Stef > Hi, Stef. Perhaps you missed the beginning of this discussion, but the problem at hand is how to translate an 822 date into something meaningful (like GMT), e.g. to sort messages by time sent, or to convert to X.400. (Then again, perhaps you just forgot to include a smiley face :-). I know of no database that can be used to translate domains into timezones, so looking at the domain, while perhaps helpful to a human user *in some cases*, is of no help whatsoever to the program parsing the date. I say *in some cases* since domains are not necessarily tied to geography: How can I tell that northrop.com is in PDT? Doesn't IBM's Guam office belong under ibm.com (actually, probably really belongs under ibm.ny.us). Is a Delaware corporation necessarily in EDT? Does a Liberian freighter necessarily come from Liberia? Enquiring minds want to know. As Erik Swiggum points out, this discussion is probably on the wrong list (except possibly for the bit about translating from rfc822 to X.400). --Marvin