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.

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

directory (missing a path separator). This is a regression added in
rev 1.264 (Sept 8 2015).
Also, if rename() of packet fails, don't continue tossing into that packet.
Increment version to 2.33 (the expected last reivion of the v2 series).

(based on FTS-5005 description) - both detection (won't pack/bundle outgoing
mail for a node that is "busy" with a mailer session) and exclusive-creation
(to inform the mailer not to allow a session for this node while outgoing mail
is being processed).
- Uses strListFind() from updated xpdev.
Debug-level log message for all file deletions.
Some log message update (more detail in some, removal of others).
Bug-fix: outbound FREQ netmail messages would not be deleted after being
converted to BSO *.req files. It appears no one has yet tested this feature?
Cleaned-up sbbsecho.h: use of C99-types, defined SBBSECHO_ARCTYPE_NONE magic
number macro.
Incremented version to 2.32.

- Added a lot more detail for outbound echomail and netmail (msgs, packets,
  and bundles) to help identify the source of problems
- Removed a lot of unnecessary "status" type log output ("Scanning for ...")
  as it was back in 2005.
- Date format in log is more standard (year-month-day)
- Logs error level and import/export statistics when exiting
- Packs bundles *before* writing to FLO files (the only operational change).
- sbbsecho.log should actually be smaller (grow slower) though there is more
  helpful information than before.
- Incremented version to 2.31.

FidoNet netmail in the normal mail base (data/mail.*) will now be exported to
FTS-1 (*.msg) files automatically. One way in which the FTN netmail can end up
in the mail base is by using the (legacy/runemaster) Web UI. You should also
get the updated savemsg.ssjs if you're going to use this feature.
To disable this feature use the (new) '-c' option.
Normally, the exported msgs will be deleted unless the '-d' option is used in
which case the messages are just marked as "sent", so they won't be exported
again. This feature does not yet support file attachments.

This will likely lead to the SMTP server supporting the sending of FTN netmail.
Apparently we have to find a better way to encode FTN addresses within
RFC2822-compliant header fields first.

If you're using a BSO/FLO-style mailer, this feature works with the '-f' option
so the full path of an outbound netmail may be SMB->*.MSG->PKT. Direct
export to PKT is certainly possible in the future.

Incremented SBBSecho version to 2.30.

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

Beautify a lot of the remaining strange closing brace style.
Use FREE_AND_NULL() where appropriate.
Log SMB error strings for most common smblib function failures.
Log debug output in the areas.bbs alter function (help isolate Joe's crash).

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.

sbbsecho.cfg line lengths and addressess all "%compression none" AreaFix
command issues (according to Deuce).

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.

(accidentally bumped 2 versions in previous commit)

memcpy calls and explicit setting of fields to 0) - this code is just bad.
The only functional change should be that the SBBSecho product code (0x12FF)
and major/minor version number is now added to headers of type 2+ packets
generated by SBBSecho. Type 2 and 2.2 packets will have just 0xff for the
product code and the SBBSecho major version number in the product "serial
number" field (as is the common practice). I guess everyone's using type 2+
packets these days? You don't get 5D addresses with 2+, but SBBSecho doesn't
really do anything with 5D addresses anyway. <shrug>

Joe Delahaye.
Increment version to 2.21.

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

1. Scan message areas based on those listed in the areas.bbs, not those listed
in the msgs.cnf file (e.g. configured with SCFG->Message Areas). This allows
the same message base to be scanned more than one for a different set of
uplinks (i.e. gating).
2. Store the message base export pointer (in the data/subs/code.ini file) with
the echotag as part of the key-name. This allows the different upstream
networks to have different export pointers (though after a complete
scan the export pointers should be the same for each msg base).

Increment the version number to 2.20.

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

Convert binary export pointer file (*.sfp) to a field of the <subcode>.ini.
Strip control character (e.g. new-line sequences) from log file output.
Paranoid use of parenthesis around bit-wise operations.
Resolve some 64-bit warnings/problems (e.g. ulong msgptrs).
When exporting a reply to an existing message, do not "generate" a REPLYID
field if the original (replied-to) message did not have a MSGID (bug reported
by Mark Lewis).
Convert CP437 chars used for creating sbbsecho.msg to hex to resolve viewcvs
UTF-8 python error:
UnicodeDecodeError: 'utf8' codec can't decode byte 0xdc in position 147782: invalid continuation byte

pktname() will no longer return a filename of an existing file under any
circumstance (even if there are 200+ *.pkt/pk_ files).
pkt_to_pkt() cleanup using a packet's file stream pointer to indicate it is
open or not.
Added debug log output for packet file open error (for access_d).

(these are not fidonet standard values).

instead of "Notice".

bundle attachment netmail messages.

(used to always do this, but some non-conforming echomail programs apparently
treat sole-carriage returns as soft-CRs and ignore/strip them).