TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 5df4ba2a   
   REPLY: 2:221/360 5df4a484   
   Hi Tommi,   
      
   On 2019-12-14 10:51:08, you wrote to me:   
      
    WV>>>> /etc/stunnel # cat binkps.conf   
    WV>>>> cert=/etc/letsencrypt/live/vlzn.nl/fullchain.pem   
    WV>>>> key=/etc/letsencrypt/live/vlzn.nl/privkey.pem   
    WV>>>> connect=24554   
      
    TK>>> Ok. I can live with that. :)   
      
    WV>> Those are the files letsencrypt generates by default. Don't you need   
    WV>> to specify your (private) key?   
      
    TK> Yes. That "web.pem" of mine contains both.   
      
   Aha.   
      
    TK> Your way is better, I changed to that. Thanks!   
      
   So you don't have to regenerate your web.pem, when your letsencrypt files get   
   updated?   
      
    WV>> I'm only a bit surprised it came in on IPv4 not like your regular   
    WV>> connections on IPv6!?   
      
    TK> I wonder why openssl in linux prefers ipv4..?   
      
   Indeed. Did you try ncat as Oli suggested?   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/0 227/114 229/101 200   
   SEEN-BY: 229/354 426 1014 240/5832 249/307 317 280/464 5003 5555 292/854   
   SEEN-BY: 310/31 342/200 396/45 423/120 712/848 770/1 2452/250   
   PATH: 280/464 229/426