Hi,

On 2016-11-17 09:51:52, Nicholas Boel wrote to Wilfred van Velzen:
  about: "Re: Testing echomail script.":

 WV>> Date/time and path of first to arrive here:

 WV>> 2016-11-17 02:19:15
 WV>> @PATH: 340/800 154/10 123/500 140/1 120/544 227/51

 WV>> Second (dupe):

 WV>> 2016-11-17 02:31:00
 WV>> @PATH: 340/800 154/10 221/6 0 140/1 261/38 712/848

 WV>> So the date/time was changed in both paths, but on different systems,
 WV>> or at different times, because 140/1 is in there twice and didn't
 WV>> recognise it as dupe. And on the second path it might have had its
 WV>> seconds removed later by a mystic system... But this is all irrelevant
 WV>> ;), because the problem is the original date/time stamp...

 NB> I've confirmed there are no Mystic systems in either of those paths. So it
 NB> seems some other software out there is doing the same thing (dropping
 NB> seconds off the timestamp), according to your dupe.

It could be the new timestamp was created on second :00. Which is probably a
bigger chance than 1/60th, because some systems start their tossers with a
scheduler... ;)


Bye, Wilfred.


--- FMail-W32 1.73.4.38-B20161116