ML> i don't use the perl hooks... AFAIK, the existing nodelist perl thing with
ML> binkd is not for compiling the nodelist into a binkd nodelist but for
ML> performing lookups on the nodelist...
ML> i prefer to use the binkd_nodelister.pl script to build my binkd
ML> compatible nodelist... it can also be used to other nets but you have to
ML> be sure to specify the input, error, and output files for those othernet
ML> nodelists... i think there's one other problem in that it adds "@fidonet"
ML> to the end of all addresses even if they are not fidonet addresses...
ML> that's a small bug that can be fixed...
I am not sure why you need to use the nodelist in binkd since all the nodes can
be included in the Binkd.cfg. The mail tosser should be able to route the
outgoing mail to the correct nodes or to your hub. Syncterm and CNet has a
route-to already included in the mail tosser config. That is the easer way to
do it.
--- CNet/5
* Origin: 1:275/201.0 (1:275/201.30)
|