Subj : 2022 FTSC Standing Member Election - Votes Received
To   : Wilfred van Velzen
From : Bj�rn Felten
Date : Mon Mar 07 2022 04:19 pm

BF>> X-JAM-PATH2D: 313/41 240/1120 301/1 280/464 203/0 2

WvV> There is nothing wrong with this path, and you got it. The problem is
WvV> Andrew didn't get it.

  Rest assured, I'm not trying to point finger at anyone, I'm only curious. Every message I get from Andrew is the same:

X-JAM-PATH2D: 320/219 203/0 2

  And almost the same from every other Fidoweb connected system, like e.g. yours:

X-JAM-PATH2D: 280/464 203/0 2

  So why does Helmut's path look like the above?

  And the same for a Z1 node like Dan's:

X-JAM-PATH2D: 123/115 3634/12 240/1120 301/1 280/464 203/0 2

  Why didn't I get that directly from Andrew?

  Then we have the messages from Terry from down under:

X-JAM-PATH2D: 640/1321 1384 221/1 203/0 2

  Yes, Tommi is often the fastest system in the Fidoweb, so no surprise that I get the message the fastest from his system. But I got it.

  So, somewhere in our Fidoweb there seem to be a system that adds s-b lines without being properly connected to our Fidoweb. And the only new links I can find in any of the path lines I have looked upon is:

   -> 240/1120 -> 301/1

  Usually it works, sometimes it does not?

  Well, I guess only Andrew can properly investigate the reason that he did not receive this (for once) important message. Maybe that intermediate 240/1120 system is one of those rabid NAB systems, that refuse to handle the Fidoweb properly?



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se:4119 (2:203/2)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.