Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    ELIST    |    [ADM] ELIST Conference    |    7,279 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 4,605 of 7,279    |
|    Vincent Coen to Dan Clough    |
|    Can't connect for update    |
|    05 Feb 22 15:16:52    |
      REPLY: 2936.fido_elist@1:123/115 2661ccb4       MSGID: 2:250/1@fidonet 61fe95aa       CHRS: UTF-8 2       TZUTC: 0000       TID: MBSE-FIDO 1.0.7.24 (GNU/Linux-x86_64)       Hello Dan!              Thursday February 03 2022 19:44, you wrote to me:               > -=> Vincent Coen wrote to Dan Clough <=-               >> Trying to do the MOD-UPD for the NHL echo, and can't seem to        >> connect to your system... I see others have recently updated other        >> echos, so it's a little strange. Haven't changed anything here,        >> and have done UPD's in the past. Here's what I see in my logs:               >> BINKOUT Attempting callout for 2:250/1@fidonet, file:        >> /sbbs/fido/outbound.002/00fa0001.dlo BINKOUT JSBinkP/4 callout to        >> 2:250/1@fidonet started BINKOUT Connecting to 2:250/1@fidonet at        >> 80.229.38.173:24554 BINKOUT Connection to 80.229.38.173:24554        >> failed (Error: Unable to connect)               >> Any idea why I can't connect? Thanks               VC>> Nope as I cannot find a failed inbound poll but I notice that you        VC>> had a successful update a few hours later.               VC>> It could have been because my system was busy as one site was        VC>> rejecting some files and my system retried multi times to resend        VC>> all 12+ hours of it.               VC>> This is usually caused by the receiving system not ack'g the file        VC>> once received - I Think.               VC>> So all sorted then ?               > Yes, all good. I did make another post here explaining what I found        > wrong - I was using an OLD fidonet nodelist so it was trying to        > connect to an old/wrong IP address. All updated and good, thanks.              All sysop's should be obtaining and installing the latest nodelist - I have        now       switched to also using Z2DAILY as it is on a daily update from all zones.              For the moment the NODELIST also comes in and updates the system although it       might only last minutes or hours before the DAILY comes in - I will give it a       few more weeks and drop NODELIST and stick to the Dailies providing there are       no issues but so far it is good.                     Vincent              --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707        * Origin: The Elist Maintainer (2:250/1)       SEEN-BY: 1/120 123 15/0 18/0 200 25/0 21 90/1 105/81 106/201 116/116       SEEN-BY: 120/340 123/0 25 115 131 180 200 755 129/305 330 331 134/101       SEEN-BY: 135/300 138/146 153/757 7715 222/2 226/30 227/114 229/110       SEEN-BY: 229/206 317 400 424 426 664 700 240/1120 5832 250/0 1 3 4       SEEN-BY: 250/5 6 7 8 10 21 261/1466 263/0 266/512 275/100 1000 282/1038       SEEN-BY: 292/854 299/6 300/4 301/1 317/3 320/219 322/757 342/11 200       SEEN-BY: 396/45 460/58 633/280 640/1321 712/848 3634/0 12 15 24 27       SEEN-BY: 3634/50 119 5020/1042       PATH: 250/1 3634/12 153/7715 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca