Subj : Binkd with Fastecho...
To   : Andrew Leary
From : Oli
Date : Sun Dec 08 2024 05:17 pm

Andrew wrote (2024-12-07):

 AL> 5D BSO support uses the hex zone number extension for all but the primary
 AL> zone in that domain.

In BSO the hex zone number extension is omitted for the default outbound only, which is the default zone in the first domain. Every other outbound directory has a zone extension.

From FTS-5005.003:

  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).

  The outbound holding areas (for Zone 1 FidoNet) would then be as
  follows:

  c:\bink\outbound        (Default Outbound)
  c:\bink\outbound.002    (FidoNet Zone 2)
  c:\bink\outbound.003    (FidoNet Zone 3)
  c:\bink\outbound.004    (FidoNet Zone 4)
  c:\bink\amiganet.027    (Amiganet Zone 39)
  c:\bink\agoranet.02e    (Agoranet Zone 46)
  c:\bink\dbnet.0c9       (Dbnet Zone 201)

 AL> binkd is actually flexible enough to work around
 AL> many mail packages that do it wrong.  FastEcho, for example, always uses
 AL> the hex zone number extension for domain directories.

binkd never implemented it correctly. What you call a workaround is a workaround for a binkd bug. The narrative that all the other mailers do it wrong and binkd is the one software that does it right is just an alternative fact. BSO 5D was used before binkd even existed. BinkleyTerm had no problems with 5D outbound from Fastecho, Squish, Crashmail and other mailers .

---
 * Origin: No REPLY kludge - no reply (2:280/464.47)

.