TID: FMail-W32 2.1.3.7-B20170919   
   TZUTC: 0200   
   CHRS: CP850 2   
   PID: GED+W32 1.1.5-b20170303   
   MSGID: 2:280/5555 62aef7d7   
   Hello Binkd team,   
      
   The bindaddr keyword is used to select the IP address for making outgoing   
   calls in case there is more than one IP address that the system can use. This   
   is usefull in case one has more binkd clients running on one and the same   
   system or when one wants to override the system default in order to present a   
   2001:DB8::f1d0:zone:net:node address instead of a SLAAC or random privacy   
   address.   
      
      
   The problem.   
   ------------   
      
   bindaddr works fine in a single stack envionment (IPv4 or IPv6 only) but it   
   encounters problems in a dual stack environment.   
      
   bindaddr accepts a literal address (IPv4 or IPv6) or a hostname. Specifying   
   multiple bindaddr lines in the config does not result in an error, but only   
   the last takes effect.   
      
   specifying:   
      
   bindaddr fido.vlist.eu   
      
   or   
      
   bindaddr [2001:1c02:1103:2a00:f1d0:2:280:5555]   
      
   Results in binkd using that address for outgoing IPv6 calls.   
      
   In the windows version it results in a warning when making outgoing IPv4   
   calls: "bind: {W32 API error 10049} The requested address is not valid in its   
   context" or ."bind -- getaddrinfo: Der angegebene Host ist unbekannt.  (11001)"   
      
   In the Linux version, the literal address must be specified without the square   
   brackets and attempts to make outgoing IPv4 calls fail. So one can not use   
   bindaddr to specify an outgoing IPv6 address without breaking outgoing IPv4   
   capability.   
      
      
   Proposed solution   
   -----------------   
      
   To remedie the situation I suggest to split up the bindaddr in an IPv6 and an   
   IPv4 part.   
      
   bindaddr6    
      
   This only affects the IPv6 address used for outpoing calls.   
      
   bindaddr4    
      
   This only affects the IPv4 address used for outgoing calls.   
      
   For backward compatibility bindaddr is an alias of bindaddr4   
      
   Or alternatively:   
      
   bindaddr -6    
      
   bindaddr -4    
      
      
   How about it?   
      
      
   Cheers, Michiel   
      
   ---   
    * Origin: http://www.vlist.eu (2:280/5555)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 331 153/757 7715 154/10   
   SEEN-BY: 203/0 218/700 840 220/70 221/0 6 226/17 30 227/114 229/110   
   SEEN-BY: 229/111 112 113 200 206 307 317 424 426 428 470 550 664 700   
   SEEN-BY: 240/5832 250/5 8 266/512 267/800 280/464 5003 5555 282/1038   
   SEEN-BY: 292/854 8125 298/25 301/1 305/3 310/31 317/3 320/219 322/757   
   SEEN-BY: 341/234 342/200 396/45 423/120 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/100 340 772/210 220 230 2452/250 5019/40 5020/1042 5053/58   
   PATH: 280/5555 464 770/1 317/3 229/426