REPLY: 2:280/5555 605a0014   
   MSGID: 2:5020/545 605a3ba1   
   CHRS: CP866 2   
   TZUTC: 0300   
   Good ${greeting_time}, Michiel!   
      
   23 Mar 2021 15:46:42, you wrote to Tommi Koivula:   
      
    >> TK>   13:15 [32278] trying fido.vlist.eu via proxy   
    ^^^^^^   
   Who fuquped the quoting?   
      
    >>> 192.168.1.24:8118...   
    TK>> That information is from the nodelist. That is the address where the   
    TK>> proxy connects. By default linux uses ipv6 address.   
    MvdV> Where does that port 8118 come from?   
      
   From the configuration of the proxy daemon at TK's 192.168.1.24 :-)   
      
    >>> 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   
    TK>> domain or nl2binkd or nodelist.pl.   
    MvdV> Then obviously your XinetD? Linux proxy works different then the   
    MvdV> ones I am familiar with: Relay6 or netsh in Windows. Care to write   
    MvdV> an article about it?   
      
   There are only two types of proxies (either HTTP connect or SOCKS), and they   
   work exactly the same (very primitive) way in all OSes.   
      
      
   --   
   Alexey V. Vissarionov aka Gremlin from Kremlin   
   gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii   
      
   ... that's why I really dislike fools.   
   --- /bin/vi   
    * Origin: ::1 (2:5020/545)   
   SEEN-BY: 1/123 90/1 105/81 120/340 123/131 124/5016 154/10 203/0 221/0   
   SEEN-BY: 226/30 227/702 229/424 426 550 664 700 1016 240/5138 5411   
   SEEN-BY: 240/5824 5832 5853 249/206 317 400 280/464 5003 5006 5555   
   SEEN-BY: 282/1038 292/854 8125 310/31 317/3 320/219 322/757 342/200   
   SEEN-BY: 423/120 460/58 633/280 712/848 770/1 2452/250 2454/119 5020/545   
   SEEN-BY: 5020/736   
   PATH: 5020/545 280/464 240/5832 229/426