MSGID: 2:221/242.0@FidoNet 68cc8f62
REPLY: 4:900/733 68caf443
CHRS: LATIN-1 2
PID: NiKom v2.6.0
TID: CrashMail II/Linux 1.7

 J>    Hello Mike!

 J> 17 Sep 25 09:36, you wrote to me:

 J> At first I was changin those numbers for privacy. I finally solved the
 J> issue by commenting out the last line I had in binkf.conf that allowed
 J> to connect to unlisted destinations.

 J> # Default node flags. Binkd will call an unlisted node if "defnode" is
 J> defined.
 J> #
 J> #defnode -nd *

 >>> 16 Sep 14:35:24 [45224] created /var/spool/ftn/outb.015/000300z4.csy
 >>> 16 Sep 14:35:24 [45224] call to 21:x/y00@fidonet
 >>> 16 Sep 14:35:24 [45223] 21:x/y00@fsxnet busy, skipping
 >>> 16 Sep 14:35:24 [45224] getaddrinfo failed: Name does not resolve
 >>> (8)

 MP>> Is there a reason you are obscuring the net/node number, or is it
 MP>> really showing up in the logs as 21:x/y00@fsxnet?

 MP>> If it is really showing up with the x and the y in it, then I am
 MP>> pretty sure that is your issue.  Those should be numbers.

 MP>> If you are obscuring them, I would suggest that maybe you use the
 MP>> node's actual address instead of relying on the zone lookup.  It could
 MP>> be down or not otherwise functioning properly.  There is also
 MP>> something odd going on there with the second line showing '@fidonet'
 MP>> while the third correctly says '@fsxnet' but I am not sure what might
 MP>> be causing that.

You realize there is a nodelist and you will be in it?    :)


--- NiKom v2.6.0
 * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)
SEEN-BY: 1/19 16/0 19/37 40 105/81 106/201 123/130 128/187 129/14
SEEN-BY: 129/305 132/174 142/104 926 153/7715 154/110 201/0 203/0
SEEN-BY: 218/700 221/1 6 242 226/30 227/114 229/110 200 206 275 300
SEEN-BY: 229/307 317 426 428 470 664 700 705 230/0 240/5832 266/512
SEEN-BY: 280/464 5003 291/111 292/854 301/1 320/119 219 319 2119 322/757
SEEN-BY: 322/762 342/200 396/45 423/81 633/280 712/848 902/26
PATH: 221/242 1 320/219 229/426