TID: FMail-W32 2.1.3.7-B20170919   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP850 2   
   MSGID: 2:280/5555 605a0014   
   REPLY: 2:221/360.0 6059f0f0   
   Hello Tommi,   
      
   On Tuesday March 23 2021 15:45, you wrote to me:   
      
    >>  TK>   13:15 [32278] trying fido.vlist.eu via proxy   
    >> 192.168.1.24:8118...   
      
    TK> =                             =============   
      
    TK> That information is from the nodelist. That is the address where the   
    TK> proxy connects. By default linux uses ipv6 address.   
      
   Where does that port 8118 come from?   
      
    >> But contrary to incoming, you have to make a rule for each node to   
    >> be called by the proxy.   
      
    TK> No. Nothing more to be done as your binkd does. Use .binkp.net domain   
    TK> or nl2binkd or nodelist.pl.   
      
   Then obviously your XinetD? Linux proxy works different then the ones I am   
   familiar with: Relay6 or netsh in Windows.   
      
      
   Care to write an article about it?   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: he.net certified sage (2:280/5555)   
   SEEN-BY: 1/123 19/10 90/1 105/81 120/340 123/131 203/0 221/0 6 226/30   
   SEEN-BY: 227/702 229/424 426 550 664 700 1016 240/5138 5411 5824 5832   
   SEEN-BY: 240/5853 249/206 317 400 250/1 280/464 5003 5006 5555 282/1038   
   SEEN-BY: 310/31 317/3 320/219 322/757 342/200 460/58 633/280 640/1384   
   SEEN-BY: 712/848 2452/250 2454/119 5019/40 5020/545 1042 12000 5053/58   
   PATH: 280/5555 240/5832 229/426