Hello Wilfred,

On Monday June 06 2022 18:03, you wrote to me:

 MvdV>> 109  2:240/49     Ergo Paalman           T-6in4  he.net

 MvdV>> Ergo congratulations and welcome to the Fidonet IPv6 club!

 WV> We can connect, but he still uses the default binkd configuration
 WV> file:

That is not what I see:

  17:24 [992] creating a poll for 2:240/49@fidonet (`d' flavour)
  17:24 [992] clientmgr started
+ 17:24 [3952] call to 2:240/49@fidonet
  17:24 [3952] trying f49.n240.z2.binkp.net [2001:7d0:4f41:1b00:5da5:cde2:78d6:9068]...
  17:24 [3952] connected
+ 17:24 [3952] outgoing session with f49.n240.z2.binkp.net:24554
               [2001:7d0:4f41:1b00:5da5:cde2:78d6:9068]
- 17:24 [3952] OPT CRAM-MD5-9c32d534f7fd2740d7d93d481976bc47
+ 17:24 [3952] Remote requests MD mode
- 17:24 [3952] SYS RedFrog BBS
- 17:24 [3952] LOC Tallinn/Estonia
- 17:24 [3952] ZYZ Eku
- 17:24 [3952] TIME Mon, 06 Jun 2022 18:24:04 +0300
- 17:24 [3952] VER Mystic/1.12A47 binkp/1.0
- 17:24 [3952] BUILD 2021/12/24 21:21:08 Raspberry Pi/32
+ 17:24 [3952] addr: 21:4/182@fsxnet (n/a or busy)
+ 17:24 [3952] addr: 2:240/49@fidonet
- 17:24 [3952] QSIZE 0 files 0 bytes
+ 17:24 [3952] done (to 2:240/49@fidonet, OK, S/R: 0/0 (0/0 bytes))
  17:24 [3952] session closed, quitting...
  17:24 [992] the queue is empty, quitting...



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303