Text 1959, 42 rader
Skriven 2004-06-26 13:18:52 av David Drummond (3:640/305)
   Kommentar till text 1955 av Matt Bedynek (1:106/1)
Ärende: Proposal for ICM flag
=============================
G'day Matt

25 Jun 04 05:29, Matt Bedynek wrote to David Drummond:

 MB>>> BinkD does not access a nodelist compiled or not.

 DD>> Yours may not, mine certainly does. I feed the weekly updated SLF
 DD>> nodelist through a processor, and BinkD reads the resultant file to
 DD>> determine Fidonet addresses and FQDN/IP quads for other IBN capable
 DD>> nodes.

 MB> BinkD does not, but qico and binkleyforce do.  Perhaps you should 
 MB> take a look at them to compare and get an idea of what I am talking 
 MB> about.

If I do NOT have a list of nodes and their FQDN/IP information, then BinkD does
NOT attempt to contact them direct. That information is gleaned from a file
processed from the nodelist.

 DD>> Sufficient data is there for successful IBN connects. Even the V7
 DD>> nodelist does not include ALL of the data found in the SLF nodelist.

 MB> Using a kludge to add node entries to your binkd does not count.  

A kludge? It is standard documented setup for BinkD. It may not count to you,
but it sure makes my BinkD useful.

 MB> The only way binkd can reach nodes not preconfigured via a node entry is 
 MB> the fidonet.net.

The only way to make any mailer reach nodes "not preconfigured" is... ah, it
doesn't happen. They all have to be "preconfigured" in a nodelist derivative.

Not all IP nodes list with the fidonet.net DNS - that's why my binkd uses info
from the nodelist, so it can glean the FQDN or IP. The only fidonet.net nodes
it will try are those listed that way in the nodelist.

Regards,
David

--- Msged/LNX TE 06 (pre)
 * Origin: Blessed are the geek for they shall inherit the earth. (3:640/305)