MSGID: 2:250/1@fidonet 621a3b89   
   CHRS: UTF-8 2   
   TZUTC: 0000   
   TID: MBSE-FIDO 1.0.8 (Linux-x86_64)   
   Hello All!   
      
   I have a lot of downlinks now (well over 30) and some create issues in that   
   they some time reject files and/or mail packets and the mbse system keeps   
   trying to resend - a LOT of times immediately after a reject in that it   
   attempts to send each one in the flo file then immediately retries them,   
   possibly as much as 30 times - no I have not counted this.   
      
   This is chewing up bandwidth and time that may prevent other outbound calls so   
   questions arise aimed at the active programmers  :) :   
      
   1. Can we change the number of times that when a file/packet is rejected    
   (which   
   I am guessing is caused because lack of disk space on the receivers system or   
   it has been sent and received before) also see Q 2 so can sysop restrict   
   number of time on hold files/packets are retried during a poll or crash, say    
   to   
   total of 2.   
      
   2. Restrict the attempt count to a specified defined sysop number as set up by   
   mbsetup param.   
      
   3. Cause of 1 could be that any that are accepted earlier are not being    
   removed   
   from the .?LO file so can all files received and accepted be removed from the   
   .?LO file possibly in real time (after the file is sent) so this will reduce   
   the number of failures and retries.   
      
   4. For all Polls and Crash traffic types limit by sysop defined value number    
   of   
   attempts which is currently set as 30 to again by sysop values to say time   
   between retries also as a sysop defined values such as 5 minutes for the 1st,   
   10 for the second and 60 for any remaining so for example with it set to 5   
   retries with 5, 10 and 60 and after the specified count readjust the    
   poll/crash   
   to Hold (by changing the flo file name back to .hlo.   
      
   All retries to go to the back of the polling/crash queue so that the retries   
   only occur after all others have been processed in the sequence [ this might    
   be   
   more difficult to implement as mbse can get new one's added during the process   
   ].   
      
   Thanks for considering any of the above suggestions although some of these   
   ideas may well be easy than the others but the total retry for polls and crash   
   that fail to connect is the most important as the time interval is way too   
   short.   
      
   Vincent   
      
   --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707   
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)   
   SEEN-BY: 1/123 15/0 18/200 25/0 21 90/1 92/1 103/705 105/81 106/201   
   SEEN-BY: 120/340 123/131 129/305 330 331 153/7715 154/10 218/700 221/1   
   SEEN-BY: 221/6 226/30 227/114 229/110 206 317 400 424 426 428 452   
   SEEN-BY: 229/550 664 700 240/1120 5832 250/0 1 2 3 4 5 6 7 8 10 11   
   SEEN-BY: 250/21 263/0 266/512 275/1000 280/464 282/1038 292/854 301/1   
   SEEN-BY: 301/113 317/3 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 640/1321 712/848 3634/12 5020/1042 5058/104   
   PATH: 250/1 301/1 229/426