SBBS echo is placing netmail to any adress not in zone1 in a directory named out.(hex of zone) Since BinkD throws an error if you try to specify an extention on a directory, is there any way to get SBBSecho to NOT do this and just put everything in the specified out directory?
---------------
Kostie Muirhead
AKA Underminer
The Undermine - undermine.ddns.net
Fido: 1:342/17

--- SBBSecho 2.12-Win32
* Origin: The Undermine - Telnet:undermine.ddns.net 1:342/17 (1:342/17)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSecho and BinkD
By: Underminer to All on Thu Apr 09 2015 04:48 pm

SBBS echo is placing netmail to any adress not in zone1 in a directory named out.(hex of zone) Since BinkD throws an error if you try to specify an extention on a directory, is there any way to get SBBSecho to NOT do this and just put everything in the specified out directory?

If "everything" went into a single outbound directory, you would have potential
filename conflicts where the same net and node number are used in different zones. A separate outbound directory for foriegn zones is the Binkely-Style-Outbound (BSO) "standard". See http://wiki.synchro.net/ref:fidonet_files for details.

Perhaps if you gave us the BinkD error message you're referring to, we could help you to resolve that.

digital man

Synchronet "Real Fact" #64:
Synchronet can dynamically compress and uncompress message bases (using LZH). Norco, CA WX: 72.0øF, 38.0% humidity, 9 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSecho and BinkD
By: Underminer to All on Thu Apr 09 2015 16:48:55

SBBS echo is placing netmail to any adress not in zone1 in a directory named out.(hex of zone) Since BinkD throws an error if you try to specify an extention on a directory, is there any way to get SBBSecho to NOT do this and just put everything in the specified out directory? ---------------
Kostie Muirhead
AKA Underminer

Disregard. I found a help file on BinkD with 4D tossers and figured it out. ---------------
Kostie Muirhead
AKA Underminer
The Undermine - undermine.ddns.net
Fido: 1:342/17

--- SBBSecho 2.12-Win32
* Origin: The Undermine - Telnet:undermine.ddns.net 1:342/17 (1:342/17)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Hello Underminer,

On 09 Apr 15 16:48, Underminer wrote to All:

SBBS echo is placing netmail to any adress not in zone1 in a directory named out.(hex of zone) Since BinkD throws an error if you try to
specify an extention on a directory, is there any way to get SBBSecho
to NOT do this and just put everything in the specified out directory?

The configuration error may be in binkd itself. What does your domain line(s) look like?

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: Re: SBBSecho and BinkD
By: Nicholas Boel to Underminer on Thu Apr 09 2015 18:02:06

The configuration error may be in binkd itself. What does your domain line(s) look like?
Regards,
Nick

It was with BinkD.
The issue was that I was confused when setting up the domain, and didn't know that the zone number you place after the outbound directory has to be the one that the tosser doesn't append to the directory name rather than the zone you are in. All good now. In fact, you should see agoranet netmail from me :)
---
Kostie Muirhead
AKA Underminer
The Undermine - undermine.ddns.net
Fido: 1:342/17



---
þ Synchronet þ The Undermine - undermine.ddns.net

Re: SBBSecho and BinkD
By: Digital Man to Underminer on Thu Apr 09 2015 16:42:15

If "everything" went into a single outbound directory, you would have potential
filename conflicts where the same net and node number are used in different zones. A separate outbound directory for foriegn zones is the Binkely-Style-Outbound (BSO) "standard". See http://wiki.synchro.net/ref:fidonet_files for details.

Yeah, I didn't realize that the hex addressing of the files didn't include zone until just reading another post about that. I can see how that would cause issues. Anyways, I found that my issue was with BinkD configuration. It's somewhat counterintuitive that the zone # you place after your outbound directory in the domain configuration string isn't neccessarily YOUR zone for the domain, but the zone the tosser doesn't append.
---
Kostie Muirhead
AKA Underminer
The Undermine - undermine.ddns.net
Fido: 1:342/17



--- SBBSecho 2.12-Win32
* Origin: The Undermine-undermine.ddns.net-Calgary-1:342/17 (1:342/17)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net