Subj : binkd.conf has changed??
To   : Wilfred van Velzen
From : Michael Dukelsky
Date : Thu Aug 04 2016 09:06 pm

Hello Wilfred,

Thursday August 04 2016, Wilfred van Velzen wrote to Michael Dukelsky:

 ml>>>> apparently there's a system in your feed line that is
 ml>>>> ""fixing"" what it considers to be "too old" or "invalid"
 ml>>>> dates...

 WV>>> It shouldn't do that! ;)

 WV>>> I got James message 3 times. Only one had a current date, and
 WV>>> the following path lines:

 WV>>> PATH: 322/764 759 123/500 140/1 5020/1042 280/5555

 WV>>> The other two with the old date had these paths:

 WV>>> PATH: 322/764 759 123/500 154/10
 WV>>> PATH: 322/764 759 123/500 261/38 249/303

 WV>>> So one of these three systems must be changing the date:

 WV>>> 140/1 5020/1042 280/5555

 WV>>> Afaik 280/5555 isn't doing that. So 140/1 and 5020/1042
 WV>>> remain...

 MD>> My system definitely does not do such things.

 WV> Than 140/1 remains as the cause, which is Bob Seaborn.

 WV> If you have a backup of incomming .pkt files you could verify this?

Yes, I store all incoming packets for several days. The message with MSGID: 
414.fido-binkd@1:322/764 00ac33a7 that came to me from 1:140/1 had time 03 Aug 
16 10:08:29.

Michael

.... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20151128
 * Origin: Moscow, Russia (2:5020/1042)

.