REPLY: 2:280/464.47 6090490c   
   MSGID: 2:301/1 60910cf7   
   CHRS: CP850 2   
   TZUTC: 0200   
   Hello Oli!   
      
    MH>> True. Try to keep your outbound clear and always use the same   
    MH>> address to poll a system. If you have automated polls to the same   
    MH>> system, but it's othernet address, don's poll it in the same   
    MH>> minute.   
      
    MH>> That said, polling the same system to get othernet's mail makes   
    MH>> no sense at all because the othernet's stuff will be transmitted   
    MH>> during your fidonet poll.   
      
    MH>> Therefore: Use a singe address to initiate polls and the problem   
    MH>> will go away. Inspect your outbound and see what's causing the   
    MH>> calls.   
      
    Ol> This is not how BSO is supposed to work. The tosser creates flow files   
    Ol> for all nodes that receive mails (files), the mailer does the polling   
    Ol> and should be able to sort it out.   
      
   Oehm, i think BSO is exactly supposed to work like that. Only true within   
   a single network, of course. Rule of thumb is: Only one outgoing file per   
   destination system within the same network ... or at least all of them   
   addressed to the same nodenumber - WITHIN the same network.   
      
   Matthias   
   --- GoldED+/W64-MSVC 1.1.5-b20180707   
    * Origin: MHS Systems (2:301/1)   
   SEEN-BY: 1/123 30/0 30 90/1 103/705 105/81 114/709 120/340 123/131   
   SEEN-BY: 124/5016 129/305 154/10 203/0 220/50 221/0 6 226/30 227/114   
   SEEN-BY: 229/100 101 200 424 426 550 664 700 1016 1017 240/1120 5832   
   SEEN-BY: 249/109 110 206 307 317 280/464 5003 5555 282/1038 288/100   
   SEEN-BY: 292/854 8125 301/0 1 101 103 113 812 310/31 317/3 322/757   
   SEEN-BY: 342/200 396/45 423/120 460/58 633/280 712/848 770/1 2452/250   
   PATH: 301/1 280/464 229/101 426