On Fri, 12 Sep 2014, Nicholas Boel wrote to mark lewis:

 NB>> those same issues in the past, so I had to make my binkd only 
 NB>> call out one person at a time (maxclients 1). Otherwise if there 
 NB>> was mail for said person for both networks, it would try to poll 
 NB>> their system at the same time for both addresses with more 
 NB>> maxclients defined.

 ml> yeah, that's when i share one filebox between the two systems... 
 ml> but then again, on my main system, i don't do BSO like BSO is 
 ml> designed... i mainly use it for fileboxes so that others can binkp 
 ml> to my main system... i'd much rather that folks would use a 
 ml> traditional mailer to connect, though... it would save a lot of 
 ml> problems and offer more capabilities than currently possible but 
 ml> that's a topic for another area ;)

 NB> It has nothing to do with fileboxes, either.

i know... i said /I/ use it for the fileboxes...

 NB> If MAIL exists for both nodes (that are the same person) it will 
 NB> have something in the /outbound as well as the /outbound.02e 
 NB> directories, and will try to poll that same person twice. One for 
 NB> each node number.

correct... but i don't have that problem because i use one filebox for both of
that system's addresses... the only reason my main system even has all those
directories is for the BSY, TRY, and HLD files that bink wants/needs... plus
the occasional forced poll [F|C|D]LO file that i create...

 NB> I stopped this by changing my maxclients to 1, whereas I can use
 NB> maxservers 100 and not be affected by it whatsoever.

yup! some time back i had switched my max clients to 1 to make it easier for me
to see what was being sent out... i switched it back later to enable the
traffic to get gone sooner but i don't know that it made any difference in
actual time spent transmitting since i've only 768K up out here... it really
suxorz at times when having to send gert's 50+Meg FDN files to several of my
links at the same time...

)\/(ark