home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!unipalm!uknet!mcsun!sunic!aun.uninett.no!nuug!ifi.uio.no!enag
- From: enag@ifi.uio.no (Erik Naggum)
- Newsgroups: comp.mail.headers
- Subject: Re: New date format (year) ?
- Message-ID: <23312C@erik.naggum.no>
- Date: 20 Aug 92 19:27:06 GMT
- References: <129@bull.bull.fr>
- Organization: Department of Informatics, University of Oslo, Norway
- Lines: 41
-
- jpaul@gwx400A.bull.fr writes:
- |
- |
- | I have seen that on sendmail 5.65 it seems that the year in the date
- | field is writen with 4 digits :
- |
- | ex :
- | in 5.61 :
- | Tue, 18 Aug 92 12:08:02 +0200
- |
- | in 5.65 :
- | Tue, 18 Aug 1992 12:08:02 +0200
- |
- | I presume this is not a hazard : year 2000 is comming and it is probably
- | the reason of that change.
-
- Actually, RFC 822 changed the allowed 4-digit year specication of RFC
- 733 into a required 2-digit year specification. This was of course
- needlessly short-sighted, and the problem was fixed in RFC 1123, which
- says, in section 5.2.14:
-
- All mail software SHOULD use 4-digit years in dates, to ease
- the transition to the next century.
-
- | But this causes me a problem on a gateway which is not able to manage
- | that format. And I would like to know if there an RFC or some think
- | concerning this before submitting the problem to the gateway's
- | programmer.
-
- RFC 1123 should be all you need. The gateway programmer should be shot
- for being so foolish as to not accept four-digit years to begin with.
- The same applies to automatic date conversion utilities which don't
- understand date specifications like
-
- Thursday, 20 August 1992
-
- which some BITNET sites are wont to send out (clue: ignore the rest of
- the word after you've recognized the three first letters).
-
- Best regards,
- </Erik>
- --
- Erik Naggum | ISO 8879 SGML | +47 295 0313
- | ISO 10744 HyTime |
- <erik@naggum.no> | ISO 10646 UCS | Memento, terrigena.
- <enag@ifi.uio.no> | ISO 9899 C | Memento, vita brevis.
-