Tuesday January 12 2016 04:07, BjЎrn Felten wrote to Tommi Koivula:
TK>> I do not have such a problem. BjЎrn did. BF> BF> I did? Really? How do you come to that conclusion? I just was the BF> one that first spotted and reported this crazy behaviour from Benny's BF> system. I never said I had a problem with it, did I?
No, you said "WTF?" Swedish synonym to "seventeen also" :D
BF> Of course my system would never try to send mail to an 0.0.0.0 BF> system.
Oh? Please do read back to you original comment to Benny with "WTF?"
20 Dec 00:36:10 [1684] call to 2:230/0@fidonet 20 Dec 00:36:10 [1684] trying themultixpoint.noip.me [0.0.0.0]... 20 Dec 00:36:10 [1684] connection to 2:230/0@fidonet failed: 20 Dec 00:36:10 [1684] holding 2:230/0@fidonet (2015/12/20 01:36:10)
BF> I'm using fucking binkd for outgoing calls, remember?
I remember. It sure did try to send mail to a system which address was 0.0.0.0.
My binkd/2 does even worse:
=== Begin test.inc === node 2:221/9999 -noproxy 0.0.0.0 === End test.inc ===
09:52 [17861] BEGIN, binkd/1.1a-75/OS2 -p -P 9999 binkd_client.cfg 09:52 [17861] creating a poll for 2:221/9999@fidonet (`d' flavour) 09:52 [17861] clientmgr started 09:52 [17862] call to 2:221/9999@fidonet 09:52 [17862] trying 0.0.0.0 [0.0.0.0]... 09:52 [17862] connected 09:52 [17862] outgoing session with 0.0.0.0:24554 09:52 [17862] OPT CRAM-MD5-ddd2eb0b199a9079550ae4bd3f586cee 09:52 [17862] Remote requests MD mode 09:52 [17862] SYS RBB/2 [S] 09:52 [17862] ZYZ Tommi Koivula 09:52 [17862] LOC Lake Ylo, Finland 09:52 [17862] NDL IBN,CM 09:52 [17862] TIME Tue, 12 Jan 2016 09:52:28 +0200 09:52 [17862] VER binkd/1.1a-75/OS2 binkp/1.1 09:52 [17862] all akas was removed as shared 09:52 [17862] done (to 2:221/9999@fidonet, failed, S/R: 0/0 (0/0 bytes)) 09:52 [17862] session closed, quitting... 09:52 [17861] rc(17862)=0 09:52 [17861] the queue is empty, quitting...
