On May 1st 3:47 am Wilfred van Velzen said...
 WV> 12:34:20 [9475] call to 1:226/16@fidonet  TK>>>>>  18 Apr 12:34:20 [9475] 
 WV> trying f16.n226.z1.binkp.net  TK>>>>> [98.124.199.3]...
 WV> 
 WV>  >>>> i get the same IP for the listed newfrontier.net... possbly they 
 WV> had  >>>> their mailer down while doing work on it when you attempted 
 WV> your  >>>> connection?
 WV>

It's 'frontierbbs.net' 1:226/16 is the default Bink port. (BinkD) (BBS Name
"The Amiga Frontier BBS) (frontierbbs.net:8888) "

1:226/17 - frontierbbs.net:24556/binkit


 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

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



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
 * Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)
SEEN-BY: 1/100 123 103/705 124/5013 5014 5015 5016 130/230 803 15/2 154/10
SEEN-BY: 18/200 19/33 35 203/0 221/0 226/16 17 229/1014 200 354 426 452
SEEN-BY: 240/5832 2452/250 249/206 307 317 400 261/38 280/464 5003 5555 310/31
SEEN-BY: 317/3 31999/99 322/757 342/200 3828/7 387/21 393/68 396/45 423/120
SEEN-BY: 712/848 770/1