Subj : Issue with BinkD and outbound attempts.
To   : Oli
From : mark lewis
Date : Sun Mar 29 2020 08:15 am

  Re: Issue with BinkD and outbound attempts.
  By: Oli to Tony Langdon on Sun Mar 29 2020 11:57:21

 > I don't see the ambiguity. The FTS-5005 is very clear about it:
 >
 >   How should Outbound Areas be named when domains are used?
 >   As always, the outbound area for your primary address (including
 >   domain) is the default outbound.
 >
 >   Separate Outbound Areas are needed for each Zone in each Domain.
 >   These take an identical stem path to the primary outbound, except
 >   that the name of the last sub-directory is changed to the
 >   <abbreviation> parameter, plus the zone extension.
 >
 >   For example, if your default outbound is C:\BINK\OUTBOUND
 >   for the outbound holding area (and you are in FidoNet), Amiganet
 >   (zone 39) outbound mail would be held in the C:\BINK\AMIGANET.027
 >   directory instead. Note that outbound areas for domains other than
 >   your primary will ALWAYS have a zone extension, and that zone
 >   extensions are always specified in Hexadecimal, up to .FFF (4095).

this last paragraph is wrong for full and proper 5D BSO... what is described 
here is what i've been calling 4.5D (meaning four and a half dimension)...

i've already posted a binkd FAQ Q&A about this as well as one of the binkd 
developers' comments on how proper 5D is done in binkd...


)\/(ark
--- SBBSecho 3.10-Linux
 * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

.