Subj : Re: binkd.conf has changed??
To : Michael Dukelsky
From : Wilfred van Velzen
Date : Thu Aug 04 2016 06:10 pm
Hi,
On 2016-08-04 19:02:14, Michael Dukelsky wrote to Wilfred van Velzen:
about: "binkd.conf has changed??":
ml>>> apparently there's a system in your feed line that is ""fixing""
ml>>> what it considers to be "too old" or "invalid" dates...
WV>> It shouldn't do that! ;)
WV>> I got James message 3 times. Only one had a current date, and the
WV>> 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 remain...
MD> My system definitely does not do such things.
Than 140/1 remains as the cause, which is Bob Seaborn.
If you have a backup of incomming .pkt files you could verify this?
Bye, Wilfred.
--- FMail-W32 1.69.22.178-B20160706
* Origin: Native IPv6 connectable node (2:280/464)