MSGID: 2:280/464.47 6090490c   
   REPLY: 2:301/1 60902367   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Matthias wrote (2021-05-03):   
      
    MH> Hello Oli!   
      
    TK>>> Setting "maxclients 1" might help.   
    Ol>> but it would be only a workaround and doesn't fix the root cause of   
    Ol>> the problem.   
      
    MH> True. Try to keep your outbound clear and always use the same address to   
    MH> poll a system. If you have automated polls to the same system, but it's   
    MH> othernet address, don's poll it in the same minute.   
      
    MH> That said, polling the same system to get othernet's mail makes no sense   
    MH> at all because the othernet's stuff will be transmitted during your   
    MH> fidonet poll.   
      
    MH> Therefore: Use a singe address to initiate polls and the problem will go   
    MH> away. Inspect your outbound and see what's causing the calls.   
      
   This is not how BSO is supposed to work. The tosser creates flow files for all   
   nodes that receive mails (files), the mailer does the polling and should be   
   able to sort it out.   
      
   I think we missed an important clue:   
      
    RS> ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such AKA   
      
   We need a complete session log and/or the config file to see what's wrong.   
      
   ---   
    * Origin: . (2:280/464.47)   
   SEEN-BY: 1/123 90/1 103/705 105/81 114/709 120/340 123/131 124/5016   
   SEEN-BY: 129/305 154/10 203/0 221/0 226/30 227/114 229/101 200 424   
   SEEN-BY: 229/426 550 664 700 1016 1017 240/2100 5138 5411 5824 5832   
   SEEN-BY: 240/5853 6309 249/109 206 307 317 280/464 5003 5555 282/1038   
   SEEN-BY: 288/100 292/854 8125 301/1 310/31 320/219 322/757 342/200   
   SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 2432/390 2452/250   
   SEEN-BY: 2454/119   
   PATH: 280/464 240/5832 229/426