Hello Alexey!

19 Dec 20 06:48, you wrote to Maurice Kinal:

 AV> The "Date:" kludge containing the date and time in RFC-3339 format
 AV> with one variation - allow the space between the time and UTC offset.
 AV> The "datestr" format for that would be "%F %T %:z" (try `date '+%F %T
 AV> %:z'`).

 AV> Rules:
 AV> 0. The "Date:" kludge _must_ contain valid time in either "%F %T %:z"
 AV> or "%F %T%:z" format. 1. Once the "Date:" kludge is present in a
 AV> received message, the compatible software (that's aware of the "Date:"
 AV> kludge) _must_ use the time from the kludge. 2. When composing a
 AV> message, the compatible software _must_ fill the "Date:" kludge and
 AV> _should_ fill the legacy header with the valid time (considering
 AV> precision limitation) or it _may_ fill the legacy header with all zero
 AV> bytes.

The legacy date/time field _must_ be filled with the valid time (considering 
precision limitations.)  If the legacy date/time field is filled with NULs, 
the packet may be discarded as old or invalid by existing software.

 AV> This would allow us to get rid of ancient software without breakind
 AV> almost everything.

Agreed.

 AV> Also, the example of the "Date:" kludge can be found in this my
 AV> message :-)

I didn't see it... ;-)

Andrew

--- GoldED+/LNX 1.1.5-b20180707