On 2017 Aug 11 17:08:58, you wrote to me:

 ml>> radius and derivitives have a bug dealing with U,Txy flags...
 ml>> specifically that they should not be UFlags in this day in time...

 PQ> That is an interesting POV on a standard that was in widespread use for
 PQ> over a decade, and which was rescinded/modified to fix a clerical fault in
 PQ> FTSC administrative requirements.

what??? what i'm saying is that U,Txy flags should be just Txy with no U... the
 problem with radius and others is/was that they insisted on the U or they
would not properly process the flag, IIRC... Txy hasn't been a user flag since
it was approved many years back after it went through a testing period as a U
flag...

 PQ> Fortunately it is not binding on individual system override settings.

there is that...

 PQ>>> Nevertheless, can't binkD be *stalled* for a node by utilizing *.?sy
 PQ>>> flags?

 ml>> that is one possible solution... one would need to look at
 ml>> traditional binkleyterm utilities to see what they did for things
 ml>> like this... SOB and SOSOB are two utils that may provide an

oops... that should be BONK and SOB (Son of BONK)...

 ml>> answer... too bad that so many binkleyterm related tools are simply
 ml>> no longer available and/or are otherwise forgotten in the mists of
 ml>> time 

 PQ> Dude, we're talking binkD only.

it is a BSO mailer and should follow standard BSO ops... BONK and SOB can be
used by all BSO systems...

 PQ> Pavel Gulchouck (2:463/68) wrote in the binkD echo back on Mon, 25 Jan
 PQ> 16...

 PQ> "*.csy are used a similar way to *.bsy but they set on start calling
 PQ> node, before handshake. It prevents simultaneous calls to the remote
 PQ> node by several binkd processes."

yeah... using a BSY semaphore is fine... that's what i was saying about looking
 at BONK and SOB to see what they do when they are processing existing waiting
outbound mail... BONK and SOB are also used to "qualify" mail for sending at
specific times in a similar manner to frontdoor's schedule qualifier stuff for
mail... in other words, the files are named different so that the mail cnn't
see them but at, say, 0200, BONK or SOB are run and will see that you want to
send to system x:y/z so it will rename those files for that system so the
mailer can see them now... actually scheduling and qualifying outbound mail for
 sending... unfortunately if x:y/z polls you before their mail is qualified,
they won't get it since the mailer cannot see it due to the file names...
that's different than frontdoor which handles it all internally and does
provide unqualified mail to polling systems...

yeah yeah yeah, i know but i cannot help really really really liking the
intelligence that frontdoor has built in compared to the rocks and stones that
binkleyterm and most of its derivitives plod along with...

 PQ> That is _the_ solution in binkD usage canon.  I just don't know of
 PQ> anyone who uses it (.csy)... yet.  Nudge, nudge.  ;-)

the only BSO stuff i currently use is mainly a poll file creator written in
4DOS and bash... i couldn't get the 4OS2 side to process the script properly...
 something about missing functions and other functions working differently...
anyway, the script just touches or creates ?LO semaphores once it validates the
 address the poll is for...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Live a little - butter both sides of the bread.
---
 * Origin:  (1:3634/12.73)
SEEN-BY: 116/116 18 120/302 331 123/140 141 124/5014 5015 128/187 130/20 210
SEEN-BY: 510 803 135/300 140/1 154/10 19/25 75 218/700 220/60 222/2 230/150
SEEN-BY: 2320/100 240/1120 249/303 250/1 261/100 38 266/404 267/155 280/1027
SEEN-BY: 282/1031 1056 292/908 31999/99 320/119 219 34/999 340/400 3634/12 15
SEEN-BY: 22 24 27 50 387/21 25 393/68 396/45 5020/1042 712/848 801/161 189 90/1