SFToss32 v1.07 Beta 1 - Multi-Link CFG Notes
=============================================

SUPPORTED FORMATS
-----------------

Legacy single-link:

  Flat ADDRESS, HUB, OUTDIR, and optional PKTPW directives. AREA and
  NETMAILZONE are not used.

Named multi-link:

  Global paths appear first. Each [LINK name] section contains its own routing.

Example:

  INBOUND C:\MAILER\IN
  CONFDIR C:\SF
  WORKDIR C:\SF\WORK
  MSGDIR C:\SF\MESSAGE
  SYSTEM Example BBS

  [LINK FIDONET]
  ADDRESS 1:100/10
  HUB 1:100/1
  OUTDIR C:\MAILER\FIDO
  PKTPW PASSWORD
  NETMAILZONE 1-6
  AREA LOCAL_CHAT

  [LINK ZERONET]
  ADDRESS 911:1503/3
  HUB 911:1423/0
  OUTDIR C:\MAILER\ZERO
  NETMAILZONE 911
  AREA 0N-CHAT

PASSWORD RULE
-------------

A populated PKTPW sets a packet password. A link with no packet password omits
the directive completely. This is invalid:

  PKTPW

ROUTING
-------

* Inbound link: exact packet destination AKA.
* Outbound Echomail link: exact SFMCONF.DAT Net ID/AREA tag.
* Outbound NetMail link: destination zone through NETMAILZONE.
* Every AREA belongs to exactly one link.
* Zone ranges may not overlap.
* Link names and AREA comparisons are case-insensitive.
* Duplicate names, addresses, hubs, OUTDIR paths, AREA ownership, or zone claims
  are rejected.
* There is no fallback link in multi-link mode.

OUTPUT
------

Each link publishes its own packet/bundle into its own OUTDIR. Two links may
legitimately produce the same bundle filename because they use different
directories.

UNKNOWN AREAS
-------------

Unmapped Echomail is preserved under UNKNOWN beside SFTOSS32.EXE. Before each
toss, saved messages are retried. A saved message imports only after its AREA is
present in SFMCONF.DAT and owned by exactly one CFG link.
