- KillEmptyNetmail
- DeleteNetmail
- DeletePackets

If a linked-node's inbox is the same absolute path as the inbound or
secure-inbound directories, clear the inbox (don't use it).
If a linked-node's outbox is the same absolute path as the outbound directory,
clear the outbox (don't use it).

that contains wildcards ("ALL") - prevents misconfiguration. Fileboxes are not
for multiple-nodes (one node per in/outbox only).

- SBBSecho will now maintain a file called the Bad Area File
  (default name is data/badarea.lst), in BACKBONE.NA format
- This file is suitable for importing in SCFG->Message Areas now, but expect
  some automation in the near future
- To get area descriptions (not just echo tags) in the Bad Area File, be sure
  to configure at least one "Additional EchoList" to point a comprehensive echo
  list (e.g. BACKBONE.NA or similar)
- SBBSecho will automatically add new areas (when new messages are received for
  msg areas you don't carry) or remove areas that you start to carry - no sysop
  maintenance of this file should be needed. And the file does not have to be
  deleted after being imported (e.g. with SCFG).
- SBBSecho does not (and may never) actually modify your Synchronet Message
  Areas configuration directly, that is yet to be determined

Another new feature: Area File (areas.bbs) backups:
- Whenever the Area File is modified via AreaFix, the current file is backed
  up  (e.g. areas.0.bbs, etc.)
- This feature can be tweaked or disabled via the AreaFileBackups key in
  sbbsecho.ini (not yet in echocfg), default backup level is 100

* Numerous EchoCfg help text updates.
* Some minor terminology updates (e.g. AREAS.BBS->areas.bbs, Areafix->AreaFix).
* Incremented SBBSecho version from 3.00 to 3.01.

name(s) are zero-length strings.

attribute for netmail (both *.msg and in the mail base). This option should
*not* be used when the DeleteNetmail option is enabled (set to 'Yes').
A warning will be logged in this configuration as dupe netmail msgs may be
sent in that case.

For packet creation, the only difference (from Type-2+) is with packets created
from point nodes: the origNet field won't be set to 0xffff (as is the case with
FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
net (ala Squish) when configured for Type-2+ packet generation.
When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
reported as "2e" for valid "2+" packets. This is normal and expected when the
originating node is not a point and the auxNet field is 0.
The second set of orig/dest zone fields in a type 2e/2+ pkt header will
now be used when importing if the old/QM orig/dest zone fields are 0.
Also, the originating point field may now be imported even if the auxNet field
is not used (origNet != 0xffff).

New umask sbbsecho.ini configuration option (global), maybe used to over-ride
the default *nix file creation mode mask (077), similar to sbbs.ini.

Filtered messages include messages not imported due to age, twitlist, dupes,
etc. To change this behavior, set RelayFilteredMsgs=true in your sbbsecho.ini.

the LogTimeFormat key in sbbsecho.ini. The default is "%Y-%m-%d %H:%M:%S".
If you want the old (v2) time-stamp format, set this value to
"%m/%d/%y %H:%M:%S". Any/all valid strftime() specifiers may be used.

StrictPacketPasswords (default is "true").
If you want SBBSecho v3 to behave like SBBSecho v2 with regards to packet
passwords for linked-nodes with *no* configured packet password, set this value
to "true" in your sbbsecho.ini file. I don't recommend doing this if you care
about the "security" of your echomail, but some sysops have been bitten by the
strict enforcement of the configured password in SBBSecho v3.

I also fixed some (but not all) of the signed/unsigned value comparison
warnings reported by msvc2013. Hopefully this didn't introduce any stupid bugs.

value (of "SYSOP") for the DefaultRecipient key. If it's blank (nobody)
just leave it blank.

Don't free undefined variables.

Recipient using echocfg.

non-zero-length string, will touch/create that file if outgoing data has
been processed.

Intended to allow the mailer to scan as soon as outgoing data is available
rather than having it wait for the next normally scheduled scan.

Note, if using this feature as the *only* way to trigger a scan (not
reccomended), any other sources of outgoing data (such as hatching files,
interBBS doors, etc) will also need to touch this semaphore or they will
not be sent until sbbsecho processes outgoing data.

We can't pass a const char * to FREE_AND_NULL, so remove const qualifier
rather than not use FREE_AND_NULL() here.

Back out echocfg.c changes.

With this option enabled, zone/domain mappings from ctrl/ftn_domains.ini are
used to get the outbound directory name, and the orig/dest domains for type
2.2 packets.

This allows supporting 5D addressing in sbbsecho when zones do no overlap
between domains (the normal case).

If one of the link addresses had a point specified (e.g. ".1") then all the
addresses would get that point appended to them.
Fixed atofaddr(): stop parsing the address at the *first* whitespace char.

- If you are upgrading from SBBSecho v2.x, run "jsexec sbbsecho_upgrade.js"
  to convert your ctrl/sbbsecho.cfg to the new ctrl/sbbsecho.ini.
- Major code overhaul/re-write/modernization
- ArcMail/Attach/FD mode NOT TESTED: beware if you're using this style mailer!
- New features:
+ Easier to manage configuration file (sbbsecho.ini)
+ Multiple sysop aliases supported (for receiving netmail)
+ Mutual-exclusion-lock file (ctrl/sbbsecho.bsy) to prevent accidental
   concurrent invocations of SBBSecho
+ FileBoxes (optional inbox and outbox per node, only in BSO mode)
+ EchoList 4-char "flags" are now 25-char "keys" and much easier to deal with
+ Maximum msg age configurable for NetMail and EchoMail (separately)
+ Configurable "Area Manager" user name (default: SYSOP)
+ Configurable "Default Recipient" for netmail (default: SYSOP)
+ Far fewer command-line options, more settings in EchoCfg
+ Old command-lines will still work, but most of the legacy options are just
   ignored now. Run "sbbsecho -?" for command-line syntax and options.
Other improvements:
+ All Fido kludes, including PATH and SEEN-BY lines are stored in the
   Synchronet Message Base, always (can't be disabled)
+ Better security for inbound EchoMail (passwords are always enforced)
+ More comprehensive log output (the log output is more of a priority than the
  console output now)
+ Increased accuracy for recipient user name/alias matching
+ Higher-level of uniqueness to generated packet filenames
+ All temporary files (e.g. packets in process) are created in an
   SBBSecho-specific temporary file directory
+ No longer auto-terminates when any local key is pressed: use Ctrl-C/Break
   instead to initiate a graceful premature termination
+ Much more help text in echocfg
+ Better organization of settings in echocfg
+ Optional per-node "comments" for use in echocfg->Linked Nodes

When parsing the SBBSecho configuration file (for the USEPACKER, AREAFIX, or
ECHOLIST items), flags or packer names would be ignored if they began with the
same sequence of characters which made up a previous configuration item
(flag or packer name). This appears to be a *very* long standing bug going back
to the origination of this program by Allen Christiansen (King Drafus).
Also, long overdue brace style update. Steve Deppe's influence is diminishing.
-(

(or by adding NOCIRCULARFWD to your sbbsecho.cfg):
When "Circular Path Detection" is enabled (the default), the old behavior was
to still forward the message to any links (if there are any), but not import
the circular/looped message (likely a dupe). Now, if you set this new option
to no (or add "NOCIRCULARFWD" to your sbbsecho.cfg), the message will be
completely ignored and not fowarded to any links (if there are any).
If you have no downlinks or you have circular path detection disabled, this
new option does nothing. The default is the old behavior (forward circular
messages).
Also updated the Toggle Options help text in echocfg (many options weren't
documented.

If the ZONE_BLIND option is specified in the sbbsecho.cfg file and it is
followed by a decimal number (e.g. "ZONE_BLIND 4"), then all zones less
than or equal to that number (the threshold) will be treated as a single zone
and all zones greater than that number (the threshold) will be treated as
separate zones (normal FTN behavior). The default zone blind threshold is
0xffff (all possible zones), when zone blind is used.

lengths.  SAFECOPY() isn't anymore so don't.

Thanks Access Denied for sticking with it.  This one should be more workyer.

This does not mean you can actually *USE* lines longer than 256 characters
though because the areafix stuff will still take a dump on your config if you
do.

requested by Joe (1:249/303), Wilfred (2:280/464) and Michiel (2:280/5555) for
their little 3-node inter-zonal FTN:
"Zone Blind" option (enabled in echofg->Toggle Options or by adding a line
containing the string "ZONE_BLIND" to the sbbsecho.cfg file). This option
causes zones to be ignored (back to the 2D addresses of the 80s) when parsing
and generating SEEN-BY and PATH kludge lines in echomail messages.
Incremented version to 2.23.

the "SYSOP_ALIAS" keyword in the sbbsecho.cfg file. e.g. can be set to
"Net Coordinator" with the line "SYSOP_ALIAS Net Coordinator". The default
value is "SYSOP" (case insensitive).

I've likely broken something though, so if you see weird behaviour with
extended ASCII, let me know please.

instead of "Notice".

Consider doing the same for all .h files.
Consider the meaning of sanity.