Hello Matthias,
On Friday June 18 2021 05:31, you wrote to me:
Listing him on the 8th of May was premature. He actually did not
answer incoming calls until the 14th.
That's your perspective,
Wilfred could not connect either until later in the day in the 14th.
your IP was blacklisted there due to your poll-tests. My connection
with him was earlier, but yes, the nodelist entry was a little bit premature.
So we agree on that.
In the meantime an overactive nodelist police deputy's attempts
to poll him before he was ready caused his firewall to block the
deputy's IP number. The firewall was configured to do so when an
attempt to connect to a non existant was made.
He has fail2ban active. Connecting to a non existing service causes blockage. A very long blockage. A too long blockage in my opinion.
The sysop in question was unaware that he already was in the
nodelist.
"Unaware" is a hard word for knowing that work is in progres on both sides.
I am just telling what he told me.
When he found out about this premature action, he was not
amused...
I made the nodelist entry shortly before his system was up and
running, but i knew the progres of his work. Yes, it was not perfect
from my side, but that did not cause the blockage. I've even notified
you about the situation and asked to not test his system already. Unfortunatly, my words were not heard, so i had to arrange an
unblocking later.
Those words were not heard because they were not uttered. You did NOT ask me not to test his system. You asked me not to complain if I failed to connect. And I did not complain. Not only did you not ask me not to attempt to connect, you also did not tell me that failed attempts to connect could result in a blockage of my IP number.
Urban's system was pollig here perfectly before the nodelist entry was created.
But could he accept incoming calls? I guess not. Because you polling him would have caused YOUR IP number to have been blocked as well. Unless he had already configurted an acception for you in his firewall.
In either case, if he was listed at all, he shoud have been listed as Hold or Pvt until he could accept incoming calls.
My attempts to poll him did indeed result in the blockage. But that was only the last step in the chain of events. It started with you listing him before he was able to accept incoming calls from the Fidonet community. The next step was that you did not warn me about his firewall triggering a blockade on an attempt to connect to a non existant service. My attempt to poll was only the last step.
Look, things happen. We live and learn. But don't make it look lile this was all MY fault.
This returnee obviously did not like what he found after his
return.
That's true.
It happens. We have seen it many times before. Urban is not the first to return after decades of absence. The pattern is recognisable. Fidonet is not what it was 25 years ago and many returnees have a problem when they are confronted with that fact and leave again. It is what it is.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin:
http://www.vlist.org (2:280/5555)