Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!nsc!voder!pyramid!bgg From: bgg@pyramid.pyramid.com (Ben Golding) Newsgroups: comp.mail.mh Subject: Re: Timezone interpretation problem Message-ID: <124018@pyramid.pyramid.com> Date: 20 Aug 90 20:40:04 GMT References: <123900@pyramid.pyramid.com> <316@hollie.rdg.dec.com> <9008201520.AA24431@somewhere> Organization: Pyramid Technology Corp., Mountain View, CA Lines: 36 In article <9008201520.AA24431@somewhere> aks@HUB.UCSB.EDU (Alan Stebbens) writes: >> [...] Can I suggest that in the next MH distribution, that the >> timezone names be commented out (or removed)? If people want them, >> they can uncomment them. > >Well, Ben, that's really drastic -- removing, or changing the defaults >to suit, albeit in a more general fashion, the constraints of using MH >in Australia. You seem to have missed the point of my article. The timezone name mapping will not work twice each year for a couple of weeks on mail sent internationally (but in the same hemisphere) because of the differing dates when countries change to summer time. When mail goes between hemispheres, the code only works twice each year when the conversions overlap. So it's not surprising that the problem is more noticeable in the southern hemisphere. Basically, it's broken everywhere, not just in Australia as you implied. Assuming that all mail comes from within your country is a xenophobic attitude that is all too common in the US. John Haxby <316@hollie.rdg.dec.com> suggested that it is already controlled by the ATZ option. It's not, we have it turned off. Our options are: version: MH 6.7 #6[UCI] (pta) of Thu Jun 14 16:32:43 EST 1990 options: [BSD42] [BSD43] [FOLDPROT='"0700"'] [ISI] [LINK='"#"'] [MHE] [MHRC] [OVERHEAD] [RPATHS] [SBACKUP='"#"'] [TYPESIG='int'] [UK] [WHATNOW] [SENDMTS] [SMTP] [BPOP] [NNTP] (oh, and I did just #ifdef them out.) I believe the best solution is to put this under the control of an option in mh-config and discourage people from using it. Ben Golding