Accession wrote to Bill McGarrity <=-
Also points. I have someone who sends me netmail from a point but
when I answer it, sbbsecho creates a .pnt folder under the correct outbound directory and it seems binkd never picks it up. I'm sure
this also has an answer in ROUTING as well.
You would need a specific binkd node entry for that point system, otherwise binkd wouldn't know where to send it, unless you had sbbsecho setup to route through their boss node, in which case it would go there first, and be delivered to the point afterwards.
Digital Man wrote to Bill McGarrity <=-
By: Bill McGarrity to Digital Man on Sat Feb 20 2016 08:02 pm
I've had this question forever. Being I'm the ZC for Sportnet (z24), I've always wondered which statements would I use in the sbbsecho.cfgfor, say when someone in Sportnet wants to route netmail through me to another node in
z24. I've always thought it was:
ROUTE_TO 24:24/0 24:ALL
Is this correct?
Yes, that looks correct.
Also points. I have someone who sends me netmail from a point but when I answer it, sbbsecho creates a .pnt folder under the correct outbound directory and it seems binkd never picks it up. I'm sure this also has an answer in ROUTING as well.
BinkD will send the files in the .PNT folder to the point node if it
ever connects to your host using BinkP. If not, then you'll need to
force a poll to that node (e.g. using BinkD) or route it (using
SBBSecho). But once it's in the .PNT folder it's too late for SBBSecho
to route it. But if the point node is connecting directly to you to send/receive mail, you don't want to route it anyway.
mark lewis wrote to Bill McGarrity <=-
22 Feb 16 14:49, Accession wrote to you:
OK... so in sbbsecho.cfg I can just have a ROUTE_TO 1:xxxx/xxx
1:xxxx/xx.* with no need to play with binkd.... :)
Correct. As long as you have the .0 (boss node) address in your
yes, and as mentioned later, if you are using the distributed binkd.txt
or are creating your own, that .0 boss node should be available...
If I'm using sbbsecho to route it to the boss node, why would I need
the boss node's address in the binkd.cfg? Wouldn't sbbsecho create a
.cut using the boss nodes address which binkd will understand?
If you're using BINKD.TXT I don't suppose it would be an issue, since
you would basically have an unsecure (passwordless) session defined in binkd's config anyways.
right... the main thing is to make sure that you have sbbsecho
configured to route a message to a point to its boss node /unless/ that point has a connection with your system... in that case, you will have
an entry for that point already set up...
Either way, some kind of link for that bossnode would have to be
somewhere in binkd or you would have to be using binkd.net for
lookups, otherwise it would have no idea who or where to poll.
depending on the operator's routing configuration, it may go routed to their echomail feed... that is if sbbsecho's 1:ALL format also covers points or if one has to specify 1:ALL/ALL.ALL... this also in
conjunction with the message's own FTN control attributes which may specify (eg) DIRect which then overrides any routing and requires that
the point either poll for the waiting mail OR there is an entry in a binkd.txt type of list with connection details for the destination
once the mail is packed, the destination is set in BSO type mailer systems... external tools like bonk and son-of-bonk were created to
handle the rerouting of mail in BSO environments...
this is where dynamic mailers shine compared to BSO type "blackhole" mailers ;)
|Location:||Riverside County, California|
|Nodes:||15 (0 / 15)|