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

Includes an early stab at reporting the client's real ipv4 address via telnet TTYLOC command.  You know, for weather forecasts and shit.
Largely a rip and rearrangement of Ree's websocket_proxy_service.js, as is load/websocket-proxy.js.

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

Alter calls to setStr() accordingly.
Previously, the 'str' argument may have been left undefined, leading to Bad Things.

Removed the "beta" tag - now it's officially version 1.07.  Also updated the documentation and revision history notes.

Minor bug fix for refreshing the 'message selected' check marks in the lightbar message list when other messages have been marked for deletion

Version 1.07 beta 2 - Added a way to select multiple messages in the message list and batch-delete selected messages (only if permissions allow deleting all messages).  This is most useful for personal mail when a user gets a lot of spam messages.  In the lightbar message list, the spacebar selects individual messages and CTRL-A is used to select/de-select all messages.  In the traditional UI message list, the S key is used for message selection.  CTRL-D then does a batch delete of selected messages in the message list.  The spacebar can also be used to select a message when reading it.

This is marked as 'beta', but I have tested the new features and they appear to be working as intended.  I will likely release a non-beta soon.

PKTPWD line.

typehtml.src, "NORMAL" has included high intensity.

THIS STOPS NOW!

gets smart quotes and such.

old line length was.  Some usage specifies a huge old line length (such as
1<<30) to indicate that it's already one line perparagraph.  In thise case,
word_unwrap() would allocate oldlen+1 bytes to store the paragraph data in
regardless of it never really being that long.

Also, check the return value of word_unwrap().  Not checking it caused a `
crash with triggered finding the above mentioned bug.

The JS-modeled user object's ip_address and host_name property values did not
reflect the current connection during logon events (JS modules executed during
logon, e.g. logon.js). Moved the initialization of the current user
(sbbs_t::useron) ipaddr and comp field to sbbs_t::logon() rather than when
control returns to sbbs_t::answer(). Removed the (now) redundant saves of these
user fields from answer().

The "Start with message number" prompt for the [F]ind text command would
always start searching at message #64 due to typo (i=64 rather than i=i64).
Maybe 'i64' isn't a good variable name.

function for a very very long time now, we don't need to duplicate this
functionality.

(Unless I misunderstand what the announce message is for?)

with ALL.

http://www.dusbabek.org/~garyd/bayes/bayes.js

File.crc32 contained the bit-inverted result of the CRC-32 calculation.

Currently just parses the TIC files, doesn't actually do anything.

Added a new configuration option, pauseAfterNewMsgScan, which specifies whether or not to pause (i.e., with a "finished" message) after doing a new message scan.

- Updated so that a sub-board new-message-scan (with the -new_msg_scan_cur_sub command-line parameter) can make use of the -subBoard command-line option to scan a specific sub-board, which may be different than the user's current sub-board.
- Bug fix: Doing a new-message-scan should now always display the correct sub-board @-code information in the header above the message.

This is currently marked as a "beta" version (version 1.06 beta).

Minor bug fix: The configFilename command-line parameter wasn't being referenced correctly, causing the script to abort if that command-line parameter was used.

- it actually *is* an expected condition that a to_net.addr or from_net.addr
msg header field is populated with a valid address (string) even though the
to_net.type or from_net.type value is NET_NONE.

The nntpservice.js and newslink.js modules rely on this behavior to display
and export local NNTP-posters' email addresses in message headers, but still be
able to identify newslink-imported messages as *not* local (the from_net.type =
NET_INTERNET) and thus not export them back to the network.

This was not the original intention behind these header fields in SMB, but it
was retrofitted to support this condition 10+ years ago and I forgot.

In smb_hfield_add_netaddr(), if the net_type is specifically set to NET_NONE
and passed to this function, do not return SMB_ERR_NOT_FOUND (-110). This
allows the nntpservice.js, for example, to create a message that is technically
"local", but with a from_net_addr (the NNTP-posters email address).

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