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.

(paraphrased) encountered when performing a echomail rescan for link(s):
When a packet reaches the configured "maximum packet size", finalize the
packet immediately (terminate the packet and close the file) rather than
waiting until the very end of all SBBSecho operations.

areafix responses to %LIST and %UNLINKED requests. If the same echo tag
was listed in multiple additional echolists, it was possible it would
appear multiple times in the areafix response list.

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.

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

separator (/ or \) before checking for mutex file.
Don't require an exact match [node:x] section in sbbsecho.ini for every link
in the area file (areas.bbs).

but it doesn't look like that's used here...

try to parse the link addresses.
Example invalid line (echo-tag cannot contain spaces):
VADA           Virtual Advanced BBS Support 1:261/38

Display parsed FTN addresss instead of string from AREAS.BBS file. Hopefully
this provides a better clue as to what is happening with his configuration.

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

2016-01-20 06:06:39 ERROR line 1836 renaming c:\fd\outbound\20060640.pk_ to
c:\fd\outbound\20060640.pkt
I think this is because the file 200606040.pkt already existed when the
.pk_ temp file was created and thus the rename will fail (can't rename over
an existing file) and then the packet is sent to the wrong link.
When generating a packet name, keep incrementing until both the .pkt and
.pk_ variants do not already exist. This should fix this scenario.

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

file or creates a netmail message (*.msg) file. This will hopefully help to
provide that evidence that either:
A. there is a bug in SBBSecho with regards to passing mail to downlinks, or:
B. Michiel van der Vlist is just a whimpering ass-hat

area-fix requests or generating any netmail not from the mail base.

Don't add TZUTC kludge lines to exported netmail and echomail messages when
there is already a TZUTC FidoNet control line in the message header (unexpected
but apparently, GoldEd+ does this).
If there are other duplicate FTN control/kludge lines created by SBBSecho
exporting messages added to SMBs by GoldEd+, we should address those too, even
though I believe in most cases, you should configure the editor to *not* add
these header fields in the first place.
Do not convert exisiting Origin Line's to effectively comments (replacing *
with # in " * Origin") if the current sub-board has been configured to not add
network tag/origin-lines.

apparently SCFG wasn't creating this directory and SBBS only created it if you
sent FTN netmail from the terminal server.

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.

1. If the PATH kludge line only contains 1 address, don't use it for circular
path detection.
2. If the last address of the PATH kludge line is the system's address, don't
add the system's address to the PATH.

in the system's areas.bbs file, SBBSecho would terminate prematurely with an
error: "No areas defined in <path/to>areas.bbs". This would prevent SBBSecho
from importing inbound netmail and packing outbound netmail, for example.

Needs a line-ending too, to support multple file requests in a single .req
file.

Psi-Jack.
Move the common outbound directory creation logic into a function.

modifying the 'attr' field).
Also, only set the "SENT" attribute flag if the told not to delete netmail.
This will reduce the risk to those using SBBSecho without the -d option.

Don't pack netmail that has the "SENT" attribute flag set.
Set the "SENT" attribute flag in netmail (.msg) files so if they're not deleted
they won't be repacked/sent again later.

for sbbs_t::loadposts().

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

Access_D's reported problem with re-routed netmail.