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)

Vincent Coen wrote to All <=-

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.

That is a problem for me sometimes also with my being the main hub for Micronet. I've let Andrew know to look for this message. Mike is not
part of Fidonet right now so I will forward this to him.

-- Sean

... She got her good looks from her father. He's a plastic surgeon.
--- MultiMail/Linux
* Origin: Outpost BBS * Johnson City, TN (1:18/200)