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

Hi mark,

On 2017-12-08 10:13:00, you wrote to me:

 JM>>>>> Thanks for your input!  I noticed now that there are a folder
 JM>>>>> named /fido/AmigaNet.027.

 WV>>>> That's not correct, binkd won't look in there.

 ml>>> ummm... yes it will IF it is configured in 5D form... the question
 ml>>> is, as you asked, if crashmail came up with that or if the operator
 ml>>> configured it in (a separate?) crashmail config...

 WV>> Yes, but (unless crashmail only understands 5D) I thought we should
 WV>> keep it as simple as possible and stick with 4D. That works most of
 WV>> the time. And not confuse Joacim with 2 different standards of doing
 WV>> things. But since crashmail seems to be doing 5D by default...

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

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

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)

.