Subj : Re: Binkd nondinnding to certain networks
To : mark lewis
From : Joacim Melin
Date : Fri Dec 08 2017 07:35 pm
ml> On 2017 Dec 08 14:12:22, you wrote to me:
JM>>>>> Thanks for your input! I noticed now that there are a folder named
JM>>>>> /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
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...
#
# Aliases to support known wrong 5D configurations domain fido
alias-for fidonet
#
# Aliases to support known DNS domain zones
# (some people is mix up the terms "FTN domain" and "DNS internet domain")
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
#
# Your addresses, 5D or 4D or 3D:
# address <addr1> ...
# If first address specified as 3D/4D then domain for it sets from domain #
defined in the first "domain" token. If second and more addresses specified
# as 3D/4D then domain sets from first address.
#
address 2:201/120@fidonet
address 39:160/242@amiganet
The nodenames are setup like this:
node address@fidonet/amiganet and then hostname, port and password.