Hi,
On 2014-11-21 19:11:48, Nicholas Boel wrote to Wilfred van Velzen:
about: "Re: Final Test":
WV>> It had the date set to:
WV>> 01 Jan 70 00:00:00
NB> Maybe that's what Golded, HPT, or sbbsecho starts their dates of messages
NB> with?
If you know a little bit about programming in C. You would know that:
time_t t = 0;
Defines the date: 00:00 hours, Jan 1, 1970 UTC
http://www.cplusplus.com/reference/ctime/time_t/
So you are probably right! ;)
WV>> It seems one of the in between systems (140/1 221/1 203/0) "fixed"
WV>> the date on the message. I don't know if that's the behaviour you
WV>> want? My system dumped it in the BAD area with a "message too old"
WV>> error.
NB> Personally, I would rather messages NOT be fixed by any system. How do you
NB> find and fix errors out there if systems are auto-correcting the original
NB> date/time?
Indeed. But when a system does fix a date it should at least report it did so.
Not just in the systems logs, which probably won't be noticed. But with for
instance a warning in a kludge line in the message...
Bye, Wilfred.
--- FMail-W32-1.69.1.95-B20140716
* Origin: Native IPv6 connectable node (2:280/464)
|