03 May 19 19:23, KrUpTiOn wrote to Wilfred van Velzen:


 WV>>  TK>>> The .dlo is still there...
 WV>>
 WV>>  >> And 2 days later it's still in my outbound...
 WV>>
 WV>> TK> Yes. Still "doing work on it".
 WV>>
 WV>> + 01 May 08:56:49 [13721] call to 1:226/17@fidonet   01 May 08:56:49
 WV>> [13721] trying frontierbbs.net [76.188.66.199]:24556...   01 May 08:56:49
 WV>> [13721] connected + 01 May 08:56:49 [13721] outgoing session with
 WV>> frontierbbs.net:24556 [76.188.66.199] - 01 May 08:56:49 [13721] OPT
 WV>> CRAM-MD5-3163dff974502d29a534d58f01d67acb CRYPT + 01 May 08:56:49 [13721]
 WV>> Remote requests MD mode + 01 May 08:56:49 [13721] Remote requests CRYPT

 Kr> You might have tried to connect while I was doing some upgrading.  Both
 Kr> systems have been running about 90% uptime over the last month. I might
 Kr> have been down 1 entire day, twice in the last 2 months. Both run around
 Kr> 6-7 days continuously before I reboot to clear things up.

Well then you may have a firewall or something blocking our connections. It is
still not working:

 08:08 [1128] BEGIN, binkd/1.1a-99/CYGWIN_NT-6.1 -p -P 1:226/16 binkd.cfg
 08:08 [1128] Cannot find domain for zone 1, assuming 'fidonet'
 08:08 [1128] creating a poll for 1:226/16@fidonet (`d' flavour)
 08:08 [1128] clientmgr started
 08:08 [7172] call to 1:226/16@fidonet
 08:08 [7172] trying newfrontier.net [98.124.199.3]...
 08:08 [7172] connection to 1:226/16@fidonet failed: Connection refused
 08:08 [1128] rc(7172)=0
 08:08 [1128] the queue is empty, quitting...

'Tommi

---
 * Origin: 2001:470:1f15:cb0:f1d0:2:221:1 (2:221/1)