configurable command-lines.

string (just like we do for other search-types).

command-line option.

calls to uifc.input() - don't default to overwrite mode for every call.
This also allows external/app control of the insert/over-write mode via new
uifcapi_t element: insert_mode (default is FALSE).

(change for *nix).

brackets to make it more clear that it's an implied (not real) value.

on *nix.

When packetizing netmail, the "origin" address in the created packet header
was copied from the netmail (*.msg) message file. This is fine for locally
created netmail, but nof for forwarded netmail (!). This would end up creating
outbound packets with a foreign source/origin address which may or may not
be deliverable.

Sort of related, if there are stray packets in the outbound directory with a
foreign source/origin address - don't packetize them! Just log a msg and ignore
these foreign outbound packets.

This explains at least part of the problem Nelgin reported where a routed
netmail was delivered to him (on Vert) from a hop running SBBSecho v3.01 and
I saw this packet header oddity. Now, why the actual netmail message itself
had the wrong origin address has not been identified.

If your system routes netmail messages (e.g. your hub), you'll want his update!

"Hold" attribute set, don't route to the configured uplink. Just like the last
commit, but now we actually create the proper cut/hut/out filename based on the
status as well.
Turns out, Crash and Hold NetMail was handled correctly in v2.x and was an
un-reported regression (new bug) in v3.0.

"Crash" attribute set, don't route to the configured uplink.
We really should do something similar for the "DIR" FLAGS kludge line, but
that's more work (and isn't easily set on a per-msg basis, like crash is), so
I'll revisit that later.

'SBBSecho'. Since SBBSecho sends mail *from* 'SBBSecho', it's too easy to
create a message-loop with two SBBSecho-bots talking to each other
(e.g. when forwarding AreaFix requests for areas added from EchoLists).

ping, areafix, sbbsecho, and sbbs

- Don't search for the section (echo) for each key/value

Added a debug-level log entry about the number of echostats read/parsed.

numbers displayed could be wrong since the poll-messages were not loaded
(or counted).

to message sub-boards - a preferred alternative to using "smbutil i".
The script closely mimics smbutil with an important distinction: To import a
file for the message body text, use the '-i<filename>' option. Otherwise, stdin
will be read for the message body.
Like smbutil, if the -t, -f, -s, or -d options aren't specified, one or more
required header values (to, from, subject) may be prompted for.

The main advantage here is that JSexec knows enough detail about the system
configuration to generate valid/unique Message-IDs for the newly created
messages (unlike smbutil). Message-IDs are critical for message tracing and
dupe-detection on networked message subs. Please use this script to post
(in lieu of smbutil) automated messages to networked subs.

- If SBBSecho is run in a mode to both import and export (e.g. no command-line
  options), the SMB pointer used when exporting would be crossed-up with the
  last sub-board imported into. This was the cause of the mass dupe flood from
  1:154/30  (mostly announcements from "New Files At War Ensemble BBS").

Added a bit more log output with regards to bad echo area configuration and
re-tossing (this was not related to the bug/fix above).

to cause a "valid" (default) FTN address to be parsed (e.g. 1:1/0).

2011.

Most of the changes are in EchoCfg:
- SBBSecho and EchoCfg will now maintain auto-backups of the sbbsecho.ini file
- AutoAddSubs now defaults to true/enabled: this setting is harmless without
  further configuring linked nodes (Uplink for Groups / GroupHub)
- Global Settings are now a separate sub-menu in EchoCfg
- EchoCfg remembers current selection on (more) sub-menus
- Sub-menus have been rearranged and resized
- Numerous Online Help text updates in EchoCfg
- Adding missing/new settings to EchoCfg:
  Log Timestamp Format
  Strict Packet Passwords
  Use FTN Domain/Zone Map
  BSY Mutex File Timeout
  BSO Lock Attempt Delay
  BSO Lock Attempt Limit
  Config File Backups
  Linked Nodes->Uplink for Message Groups
  Echo Statistics File
  Outgoing Semaphore File
  Automatically Add New Subs to Area File
  Maximum Backups to Maintain of Area File
  Relay Filtered Messages
  (everything you can set in sbbsecho.ini should now be editable via EchoCfg)

can be more easily used by more utilities (e.g. echocfg).

- Update bottom-line/status bar with applicable control keys (Ctrl-C/X/V)
- Ctrl-X now cuts the text to the Clipboard, rather than just deletes
- Ctrl-C now copies the text to the Clipboard, rather than aborts
- Ctrl-V now pastes from the Clipboard into the text field, not toggles insert
The old CUA keyboard equivalents for Copy/Cut/Paste are supported too
(Ctrl-Ins, Shift-Del, Shift-Ins)
The system Clipboard is used, just like with the mouse methods of copy/paste.

ufic.showbuf() changes (used for displaying help text):
- Fixed the "End" key behavior (actually goes to the bottom of the text)
- Display up and down arrow glyphs in the lower-right corner/border to indicate
  if the text can be scrolled up or down (e.g. with the arrow keys/etc.).
  If the arrows are mouse-clicked, that simulates the arrow keys being hit.

sbbsecho.cfg files), using trimLeft().
Added more debugging output (when debug is set to true) and display the number of
nodes, echolist, and packers converted at the end.
Don't rename converted files unless the extension is ".cfg".

then a clarifying or modifying word (year[s], month[s], day[s], etc.).
parse_byte_count() and parse_duration() now support a space between the
numeric value (decimal digits) and the modifier. Hopefully this doesn't break
anything, but it makes parse_duration() compatible with the strings generated
with duration_to_vstr(). We might want a verbose version of byte_count_to_str()
in the future, so I figured it made sense to go ahead and add the white-space
skipping/parsing to prase_byte_count() now.

the same as the Delete key. Apparently this change was introduced in the uifc.c
->uifcc.c/uifc32.c port and never noticed (by me). Pointed out by Nelgin.