Hello Joacim!

08 Dec 17 19:35, you wrote to mark lewis:

 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
 ml>>>> question is, as you asked, if crashmail came up with that or if
 ml>>>> the operator configured it in (a separate?) crashmail config...

 WV>>> Yes, but (unless crashmail only understands 5D) I thought we
 WV>>> should keep it as simple as possible and stick with 4D. That
 WV>>> works most of the time. And not confuse Joacim with 2 different
 WV>>> standards of doing things. But since crashmail seems to be doing
 WV>>> 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
 ml>> correct that one statement... i think you are on the right
 ml>> track... get CM and binkd both configured for 4D ops and it
 ml>> should work... if CM is only 3D, the question then is if it is 3D
 ml>> using zones or 3D using points... most folks understand that CM
 ml>> needs some love to bring it up to today's standards, anyway...



 JM> So. My binkd.cfg:

 JM> domain fidonet /fido/outbound 2
 JM> domain amiganet /fido/outbound 39
 JM> # domain retronet /fido/outbound 2

 JM> #
 JM> #  Aliases to support known wrong 5D configurations domain fido
 JM> alias-for fidonet

 JM> #
 JM> #  Aliases to support known DNS domain zones
 JM> #  (some people is mix up the terms "FTN domain" and "DNS internet
 JM> domain") domain fidonet.org alias-for fidonet domain fidonet.net
 JM> alias-for fidonet


 JM> #
 JM> # Your addresses, 5D or 4D or 3D:
 JM> #   address  ...
 JM> # If first address specified as 3D/4D then domain for it sets from
 JM> domain # defined in the first "domain" token. If second and more
 JM> addresses specified # as 3D/4D then domain sets from first address. #
 JM> address 2:201/120@fidonet address 39:160/242@amiganet

 JM> The nodenames are setup like this:

 JM> node address@fidonet/amiganet and then hostname, port and password.

 JM> Crashmail.prefs:


 JM> AKA 2:201/120.0
 JM> DOMAIN "fidonet"

 JM> AKA 39:160/242.0
 JM> DOMAIN "amiganet"

 JM> ; Nodes

 JM> NODE 2:201/0.0 "" "" AUTOADD PACKNETMAIL CRASH
 JM> NODE 39:150/200.0 "" "" AUTOADD PACKNETMAIL CRASH

 JM> ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
 JM> ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
 JM> ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
 JM> ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
 JM> ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
 JM> ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
 JM> ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

 JM> Did I forget anything?

It appears that CrashMail is supporting 5D, based on the fact that you defined 
a domain for amiganet and it is creating /fido/amiganet.027 to store outbound 
amiganet packets.  (027 hex = 39 decimal)

To make it work for your system, change the domain amiganet line in binkd.cfg 
to:

domain amiganet /fido/amiganet 2

The number after the directory name is your default zone in that domain. 
Normally the zone extension is not used for the default zone.  Since your 
tosser is creating it with the zone extension, we just lie to binkd slightly.

Andrew

--- GoldED+/LNX 1.1.5-b20170303