🚀 go-pugleaf

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.

In article <129@bull.bull.fr>, jpaul@gwx400A.bull.fr writes:
|> 
|> -- 
|> 
|> Hello every body,
|> 
|>   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.
|> 
|> 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.


In RFC 1123 - Requirements for Internet Hosts -- Application and Support:

5.2.14  RFC-822 Date and Time Specification: RFC-822 Section 5

         The syntax for the date is hereby changed to:

            date = 1*2DIGIT month 2*4DIGIT


         All mail software SHOULD use 4-digit years in dates, to ease
         the transition to the next century.

         There is a strong trend towards the use of numeric timezone
         indicators, and implementations SHOULD use numeric timezones
         instead of timezone names.  However, all implementations MUST
         accept either notation.  If timezone names are used, they MUST
         be exactly as defined in RFC-822.

         The military time zones are specified incorrectly in RFC-822:
         they count the wrong way from UT (the signs are reversed).  As
         a result, military time zones in RFC-822 headers carry no
         information.

         Finally, note that there is a typo in the definition of "zone"
         in the syntax summary of appendix D; the correct definition
         occurs in Section 3 of RFC-822.

In article <129@bull.bull.fr>, jpaul@gwx400A.bull.fr writes:
|> 
|> -- 
|> 
|> Hello every body,
|> 
|>   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.
|> 
|> 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.


The answer is: RFC 1123

      5.2.14  RFC-822 Date and Time Specification: RFC-822 Section 5

         The syntax for the date is hereby changed to:

            date = 1*2DIGIT month 2*4DIGIT

         All mail software SHOULD use 4-digit years in dates, to ease
         the transition to the next century.

         There is a strong trend towards the use of numeric timezone
         indicators, and implementations SHOULD use numeric timezones
         instead of timezone names.  However, all implementations MUST
         accept either notation.  If timezone names are used, they MUST
         be exactly as defined in RFC-822.

         The military time zones are specified incorrectly in RFC-822:
         they count the wrong way from UT (the signs are reversed).  As
         a result, military time zones in RFC-822 headers carry no
         information.

         Finally, note that there is a typo in the definition of "zone"
         in the syntax summary of appendix D; the correct definition
         occurs in Section 3 of RFC-822.

Most software is not able to handle this at the moment, but it begins to
change.

|> 
|> Thanks per advance,
|> Best regards,
|> -------------------------------- 	Jean-Paul OLIVIER
|> Email : J.P.Olivier@frso.bull.fr	BULL.S.A.
|> Phone : (1) 49 45 50 40			20, rue Dieumegard
|> bullcom : 222 5040			93406 SAINT-OUEN CEDEX
|> fax : (1) 49 45 53 36			France

-- 

Michael Storz
================================================================================
                                      !   X.400 : G=michael;S=storz;OU1=lrz;
   Leibniz-Rechenzentrum              !           P=lrz-muenchen;A=dbp;C=de
   Barer Str. 21                      !   RFC822: storz@lrz.lrz-muenchen.dbp.de
   8000 Muenchen 2                    !   Fax   : ++ 49 89 2809460
   Germany                            !   Tel   : ++ 49 89 2105 7420
================================================================================