MSGID: 2:221/6.0 5da0b0b0   
   REPLY: 2:280/5555 5da09a12   
   PID: SmapiNNTPd/Linux/IPv6 1.3 20191005   
   CHRS: IBMPC 2   
   TZUTC: 0300   
   TID: hpt/lnx 1.9.0-cur 2019-09-27   
   On Fri, 11 Oct 2019 13:54:08 GMT Michiel van der Vlist <0@5555.280.2> wrote:   
      
   > We have a new one:   
   >   
   >   81  2:243/39     Karl Kral              Native  WEDOS   
      
   I believe you mean 2:423/39.   
      
   > Karl, your system still needs a bit of tuning. Sometimes an attempt to   
   > connect at IPv6 times out and an IPv4 connect results. Sometimes it   
   > takes a while but there is an IPv6 connect anyway. Sometimes there is an   
   > IPv6 connect right away.   
      
   I noticed that too. Over 1 minute.   
      
     11 Oct 19:28:14 [14632] Substituted * to f39.n423.z2.binkp.net. for   
   2:423/39@fidonet by nodelist   
   + 11 Oct 19:28:14 [14632] call to 2:423/39@fidonet   
     11 Oct 19:28:14 [14632] trying f39.n423.z2.binkp.net. [2a02:2b   
   8:2:1::68e3:1]...   
     11 Oct 19:29:18 [14632] connected   
   + 11 Oct 19:29:18 [14632] outgoing session with f39.n423.z2.binkp.net:24554   
   [2a02:2b88:2:1::68e3:1]   
   - 11 Oct 19:29:18 [14632] OPT CRAM-MD5-7eaa2f13af5fa559d7c478c3d733e2ee   
   + 11 Oct 19:29:18 [14632] Remote requests MD mode   
   - 11 Oct 19:29:18 [14632] SYS Plast DATA   
      
   > Suggestions anyone?   
      
   -46 :)   
      
   'Tommi   
      
   --- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)   
    * Origin: smapinntpd/linux @ nntps://news.fidonet.fi (2:221/6.0)   
   SEEN-BY: 1/123 15/2 154/10 203/0 221/0 1 6 360 229/354 426 1014 230/0   
   SEEN-BY: 240/1120 5832 249/206 317 400 280/464 5003 5006 5555 292/854   
   SEEN-BY: 310/31 317/3 322/757 342/200 423/120 633/280 712/848 770/1   
   SEEN-BY: 2452/250 5020/545   
   PATH: 221/6 1 280/464 229/426