SFToss32 v1.07 Beta 1 - Testing and Bug Reports
================================================

This is a public beta. Preserve the current working version until supervised
inbound and outbound tests pass on your system.

RECOMMENDED TEST
----------------

1. Back up SFTOSS32.EXE, SFTOSS32.CFG, every SFMCONF.DAT, and the shared MESSAGE
   directory.
2. Disable normal SFToss32 and mailer automation.
3. Run SFTOSS32.EXE and confirm it reports v1.07 Beta 1.
4. Run SFTOSS32.EXE -check.
5. Confirm every link name, address, hub, OUTDIR, AREA count, NetMail zone, and
   password state.
6. Run one supervised -toss and review TOSSER.LOG.
7. Pause mailer pickup, run one supervised -scan, and inspect the new bundle.
8. Run -check again.
9. Restore automation only after the results are clean.

MULTI-LINK PASS CRITERIA
------------------------

* Each AREA belongs to exactly one named link.
* Inbound packets select the link by exact destination AKA.
* Echomail routes by SFMCONF.DAT Net ID/AREA tag.
* NetMail routes by destination zone.
* Each link writes only to its own OUTDIR.
* No-password links omit PKTPW.
* Missing or ambiguous routes fail closed.
* Foreign-address packets remain untouched.
* A caller or an existing SFTOSS.BSY prevents unsafe concurrent access.

PLEASE INCLUDE IN A REPORT
--------------------------

* Windows version and whether it is 32-bit.
* Legacy or multi-link CFG format.
* Configured link names.
* Results of -check, -toss, and -scan.
* The relevant TOSSER.LOG section.
* Whether inbound, outbound, NetMail, AreaFix, UNKNOWN retry, and node locking
  worked.
* Any loader error, crash, stale lock, routing surprise, packet rejection, or
  message-base warning.

Never publish a live CFG or packet containing an actual packet password.
