Subj : Binkd nondinnding to certain networks
To   : Wilfred van Velzen
From : mark lewis
Date : Fri Dec 08 2017 01:15 pm


 On 2017 Dec 08 16:44:42, you wrote to me:

 ml>> i do not think it does... i think crashmail is 4D at best... i'm
 ml>> certainly not disagreeing with your flow... i only wanted to correct
 ml>> that one statement... i think you are on the right track... get CM
 ml>> and binkd both configured for 4D ops and it should work... if CM is
 ml>> only 3D, the question then is if it is 3D using zones or 3D using
 ml>> points... most folks understand that CM needs some love to bring it
 ml>> up to today's standards, anyway...

 WV> I suspect CM is doing 5D because it created the /fido/AmigaNet.027,
 WV> while in it's configuration just /fido/outbound is specified,
 WV> according to Joacim. But we'll see...

i think we're missing a lot of information... we don't know what fumbling 
around has been done and we don't know when that directory was created or what 
the CM config was set to at that time...

the reason i do not think that CM is doing 5D is because of the question "where 
did it get the amiganet name for the directory when it is capable of only one 
outbound directory entry?"... if it has only one outbound directory entry, the 
/best/ it can do is 4D and that only if it handles zones and points properly... 
if it cannot handle one of those (most likely points), then it is 3D...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... I'll do whatever she tells me. And I really really mean that.
---
 * Origin:  (1:3634/12.73)

.