Hello mark,   
      
   On Monday December 18 2017 20:11, you wrote to me:   
      
    MV>> If all servers were bysy, one would expect it to be busy on IPv4   
    MV>> as well, at least occasionally.   
      
    ml> i was thinking of a situation where one would have two different   
    ml> configs sharing the same in/out dirs but having other settings   
    ml> different... eg: bonding to an address, limiting servers, online at   
    ml> certain times only...   
      
   Ah, one of your exotic scenarios... ;-) I suppose such a setup is possible,   
   binkd can be configured to listen only on IPv6 or IPv4 (listen [::] or listen   
   0.0.0.0) and it can be forced to only make IPv6 or IPv4 outgoing call with the   
   -6 or -4 option for every node and the default line in the config. But I see   
   no added value for such a complication in the setup, I do not know of any IPv6   
   capable node set up this way and it is certainly not something one would   
   expect from a beginner in the IPv6 environment.   
      
   In case of a system with native IPv6 it is almost always either a firewall   
   problem or a version of the mailer that does not support IPv6. So those are   
   the first things to look at.   
      
   Whatever. Het got it fixed already. I have no feedback yet as to the nature of   
   the problem, but if I were to put my money where my mouth is, your scenario is   
   not what I'd put my money on.   
      
   Firewall is nr one on my list, IPv4 only binkd version second.   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: he.net certified sage (2:280/5555)