🚀 go-pugleaf

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.