On 2019 May 18 15:23:50, you wrote to me:

 Ni>>> I've been using BinkIt for FTN networks for the past several months
 Ni>>> or so. I recently added FSXNet to my BBS, and it seems BinkIt isn't
 Ni>>> always connecting to every FTN host when the BINKPOLL event
 Ni>>> executes.  I have set it up according to the BinkIt page on the
 Ni>>> Synchronet wiki.  It seems to only connect to the appropriate FTN
 Ni>>> host when there's an outgoign message.

 ML>> this is proper...

 Ni> If that's the proper way, then how would my BBS download new messages from
 Ni> the hub?  Would the hub have to be set up to crash-poll mine when there
are
 Ni> new (outgoing?) messages at the hub?

i think it was Al that explained the difference between BINKPOLL and BINKOUT...
 if not it is basically like this...

  BINKPOLL is for scheduled outbound connections to certain
  selected systems and to deliver still waiting outbound FTN
  mail. both except for those systems marked HOLD.

  BINKOUT is for all-the-time-any-time delivery of any/all
  waiting outbound FTN mail except to those systems marked
  HOLD.

my system has BINKPOLL configured but it is not used by anything here... all
FTN mail is attempted to be delivered immediately after it is processed via
BINKOUT... i might have one system that i have set to HOLD because i cannot
connect to their mailer for some reason... not sure if it is a firewall issue
(eg: no port forward) or what but they do connect here (via the BINKP service)
and are able to pull their waiting mail in a timely fashion... in any case, my
system is basically doing "crashme/crashyou" with all linked systems...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Playing "ghost in the closet" at a nursing home isn't appropriate.
---
 * Origin:  (1:3634/12.73)