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.

When using the SBBSCTRL:User->List menu option, it would take minutes for the
form to fully populate and display (1457 users). It turned out this was due to
a 200ms delay for each open of the data/user.dat file.

I never noticed this problem before, but I went ahead and optimized for this
situation since it was a bit silly to be opening
and closing the user.dat almost 1500 times to get a list of users. This made a
huge difference and the user list appears in about 4 seconds now.

Oddly, this problem does not happen when listing users in the terminal server
or when iterating through them in JavaSciprt (e.g. userlist.js).

- openuserdat()
- readuserdat()
- parseuserdat()

getuserdat() still exists and just calls those 3 functions. This allows other
code (e.g. the control panel) to optimize iterative calls to getuserdat() by
opening the file just once or even reading the entire contents at once and then
parsing each user record from memory.

Updated style of arguments in userdat.h (i.e. remove argument name if obvious
from the type).

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.

Bug-fix: MSG_TO_NET would not expand properly (to a blank string) when the
to_net.type header value was NET_NONE.

Display translated to/from/reply net-type (from numeric to string).

Don't include the to/from network-arddress in the displayed header if the
net-type value is NET_NONE (not a normal/expected combination).

Include name of to/from/reply net-type.
Include to-extension value last on the "To" line.

switch" by  creating a default case.

Version 1.05 official release update (removed the "beta" from the version number & updated the release dat,e and updated the documentation)