TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 625b15ba   
   REPLY: 1:154/10 625b0c06   
   Hi Nicholas,   
      
   On 2022-04-16 13:26:28, you wrote to me:   
      
    NB>>> @PATH: 154/10 3634/12 5020/1042 301/1 280/464   
      
    WV>> It's odd that this path is 4 minutes faster then our direct link for   
    WV>> this area!?   
      
    NB> Not sure what to tell you. Anything I write should leave here to all links   
    NB> at roughly the same time. Does the order of callouts have anything to do   
    NB> with how you list nodes in binkd.conf? If so, my list starts with 1: and   
   2:   
    NB> is further down the list in numerical order. Otherwise, who knows.   
      
   It of course depends on in what order your tosser presents the files to binkd.   
   But besides that it should handle most of the outgoing mail in parallel,   
   unless you have your maxclients set to a low value...   
      
   But your log should be able to tell you what happend (if you're interested   
   enough ;-))...   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 120/340 123/131 124/5016   
   SEEN-BY: 129/305 330 331 153/757 7715 154/10 203/0 218/700 840 221/0   
   SEEN-BY: 221/1 6 242 360 226/30 227/114 229/110 111 206 307 317 400   
   SEEN-BY: 229/424 426 428 452 550 664 700 230/0 240/5832 266/512 280/464   
   SEEN-BY: 280/5003 282/1038 292/854 8125 301/1 317/3 320/219 322/757   
   SEEN-BY: 335/364 341/66 234 342/200 396/45 423/81 460/58 633/280 712/848   
   SEEN-BY: 2452/250 4500/1   
   PATH: 280/464 221/1 6 229/664 426