01 Jul 15 15:12, you wrote to All:
When i try to send something with fidonet to another zone then my own
zone (lets say zone 1) SBBSECHO / Synchronet creates a directory
called outbound.001.
this is correct...
My BinkD ony picks up the directory called outbound.
it should see the outbound.001 with no problems... what OS are you running on? if linux, there may be a ownership or permissions problem...
in any case, you should have something similar to this in your binkd.cfg file... i'm going to post this as if you're just starting out so it may seem extremely basic...
==== Begin "binkd.conf" ====
domain fidonet /home/myuser/fido/outbound 1 binkp.net
domain zone33 /home/myuser/fido/outbound 1 zone33.net
domain zone46 /home/myuser/fido/outbound 1 zone46.net
domain fido alias-for fidonet
domain fido.net alias-for fidonet
domain fidorus alias-for fidonet
domain fido7 alias-for fidonet
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
address 1:3634/12@fidonet 33:99/99@zone33 46:99/99@zone46
==== End "binkd.conf" ====
i've made up the entries above for zone33 and zone46 just to show how other FTN
networks would appear... the very last entry on the first three domain lines is
the domain where DNS lookups for addresses in those FTN networks is to be done if there's no FQDN specified on a node line for the destination system... for now, just know that binkp.net is where fidonet lookups are done since the original fidonet domain was lost to a squatter... binkp.net was set up specifically for this purpose and is updated from the fidonet nodelist on a regular basis... when using this better format of the domain line, the "root-domain" keyword should not be used... it was allowed to be used only once
and led to problems for those in multiple FTN networks/domains...
back to your original problem, though...
in the first line above, the number '1' tells binkd that the plain outbound directory is for your primary zone... in your specific case, that '1' would be '2' and the first address listed in the address line would be your primary zone2 address... secondary addresses (known as AKAs) will follow the primary on
the address line... in the above, all other zones use the same outbound directory tree as your base outbound but their directories have their zone number in HEX tacked on...
eg: using Z2 as the base local zone
outbound Z2
outbound.001 Z1
outbound.003 Z3
outbound.004 Z4
outbound.021 Z33
outbound.02e Z46
they may all appear to be in fidonet but they are not... if your software could
do 5D BSO, then the name of those other zones' outbound directory would be different... but since sbbsecho can only to 4D at best, the above is how it has
to be handled...
if you have only one zone, then you only need the very first line from the config above as well as the alias-for lines and the address line... it is actually very simple with only one network...
Is there any way to fix this in SBBSECHO / Synchronet?
no, this is something that you have to have configured in binkd correctly...
)\/(ark
... Too bad the fine line between courage and foolishness isn't a fence.
---
* Origin