Subj : Something new...
To : Sean Dennis
From : mark lewis
Date : Tue Oct 13 2009 05:34 pm
ml> that depends on your "shim"... in my case, with Warp 3 Connect, i use
ml> Ray Gwinn's SIO package and "dialing" an IP number is no different
ml> than dialing a POTS number as far as FD is concerned... the only
ml> "problem" that need be contended with is special characters in the
ml> dialing string... ie: dots instead of dashes and similar...
SD> The dialing string problem is what I'm concerned about. Like you,
SD> I run SIO 1.60d, so I know I can get out with no problems.
right... i figured that was what you were using...
SD> What I'm wondering is if BT might get confused when I want to send
SD> mail via POTS and what not. When I get the POTS set up going, if
SD> there's problems, I'll probably pull BT off the telnet node.
ahhh... hummm... i don't know your setup or how binkley does in a multi-node
setup... on my frontdoor setup, i have one master config for the pots nodes and
then each of the telnet nodes has its own specific config... FD's routing
tables are done the same way... one master for the pots nodes and then specific
ones for each telnet node... remember, frontdoor is a dynamic routing mailer so
it builds its packets and outbound files on the fly when it scans the netmail
area for outbound traffic...
i've also had to set specific settings for those nodes that i FTN over telnet
with... i think this was done in the modem manager area based on the node's
nodelist flags... i know that if i forget this, stuff still wants to go via
pots instead of telnet or it just sits and waits if i forgot the routing
stuffs... anyway, once i set a system for telnet, the pots side ignores it and
always puts it on hold... if i need to force it to go via pots, then i manually
use one of the pots nodes and force it to go now...
once i got it all set up and working, it works a treat... it is the steps
needing to be done for the nodes that i don't always recall... oh yeah, i also
use environment variables for each of the mailer nodes' numbers for those
remote systems... fd's nodelist compiler then set the nodelist so that each
mail looks to its local environment for the number for a node... in this way, i
have to manually check the nodelist (since the way it was going to be done was
never fully implemented and then others had to go down another road and muck
other stuff up) and ensure that i have the proper IP or domain name for a node
and if they also have pots, that i have the right pots number on the pots nodes
side...
again, i don't know how binkleyterm goes together for a multinode setup or if
you can have it look to different configs for some nodes... i definitely don't
know that it does environment variables for nodelist phone numbers and the like
nor do i have a clue as to how the routing stuff would work because that would
mean that your mail tosser or another tool would need to handle things that my
FD handles internally...
i hope it makes some sense and that you can glean necessary information from
the above... if you have more questions, just ask ;)
