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

addresses (e.g. FidoNet and QWK) using the new smblib feature.

and RECIPIENTNETADDR fields in messages posted to sub-boards. Apparently
GoldEd+ does this and it triggered a chain of bugs (mostly cosmetic), but bugs
that bugged me, so I'm squashing them. Now messages being export to QWK will
not include the RECIPIENTNETTYPE/ADDR information unless it's netmail.
Ditto for importing. Also, the net_type is more accurately determined (i.e. if
there's no '@' in the address, as there not be any expected for QWK and Fido
net addresses).

All other command options remain case insensitive.

If the specified or detected net_type is not Internet, only store the address
portion of the email address in the *NETADDR hfield.
If the net_type argument is a NULL pointer, automatically add the *NETTYPE
hfield too.
New functions:
- smb_netaddr_type() - returns the string/name of a specified net_type.
- smb_get_net_type_by_addr() - parses just the network address field.
Change short/ushort's to int16_t/uint16_t's.
Remove date from copyright.

Made some fixes for the header/kludge line label capitalization, etc.  Also updated to display the message attributes properly (using a text description rather than just displaying the numeric value) when displaying the message headers.  Also changed the default header label & value colors to cyan and bright blue.

Fixed the display of the "when imported zone" and "when written zone" header fields.  Also, removed a line of temporary debug code.

to stdout).

Previous behaviour was:
1) By default, send error messages to errfp (stderr), and other log messages to
   confp (stdout).
2) If -e and one of -o or -q are specified, also send a copy of error messages
   to statfp (defaults to stderr, changed to /dev/null by -n)
3) If -e is specified, also send a copy of error messages to confp (defaults to stdout)

If -e, -o, were both specified, this resulted in an error log entry going into the file
specified by -e, the file specified by -o, and confp (stdout by default).

New behaviour:
1) By default, send error messages to errfp (stderr), and other log messages to statfp
   (stderr).
2) If -e is specified, send error messages to the specified file and statfp (stderr).
3) Always send status messages to statfp (stderr).

Set up some more stuff for jsdoor...

Call gethostname() since there is no "SCFG value" for it.

Send "status messages" (log messages that aren't errors, and the banner) to
/dev/null by default (ie: force the "-n" argument)

Send "error messages" (log messages that are error according to log level) to
"error.log" by default (ie: force the "-eerror.log" argument)

Don't report a JavaScript warning ("Disconnected") until the OperationCallback
has been executed 10 times with the user offline. This gives the executing
script ample time to recognize the disconnected state and exit gracefully.
Script that do not check/notice that the user has disconnected will still be
auto-terminated (by default) and this warning will still be logged in those
cases. The value 10 was picked at random and appears to work fine.

version of configured time zone, e.g. "PST").

to errorlog() so the data/error.log is less ambiguous about where an error
occurred.

*after* the to-net-addr value (if there is one), so the header display makes
more logical sense when viewing QWK netmail sent to a QWKnet node on the
QWKnet hub system.
Update the msgtotxt() prototype to follow the norm (e.g. passing through the
mode argument to smb_getmsgtxt())

Content-Type boundary values not enclosed in quotes (e.g. like those inserted
by "Apple-Mail").

paragraph"... track the length instead.

Speeds up word_wrap() with huge messages that don't have many paragraphs.

menu.
Changed NodeStatusLogon to from "At logon prompt" to "At login prompt" to be
more consistent in the use of the term login vs. logon (in Synchronet).
Added new text.dat line: NodeStatusLogout

*after* the to-net-addr value (if there is one), so the header display makes
more logical sense when viewing QWK netmail sent to a QWKnet node on the
QWKnet hub system.

menu.

a QWK packet downloaded from a QWKnet hub.

Omit :[WebIni.HTTPPort].  This will solve the problem for Deepend, but isn't really the best solution.  The best solution would be to shoot ecWeb v3 in the face and call it a day.

MsgBase.save_msg() method. The bug was that it was forcing the idx.to value to
0 which would only work (in theory) for mail going to a QWKnet hub.
Now, save_msg() will check the 'to_net_addr' property of the header object
(or recipient objects) and actually verify that it/they are routeable QWKnet
address(es) and throw an exception if not.
If the first hop is a QWKnet node, sets the to_ext (and thus, idx.to value) to
the account number of the node. This also looks up full-routes via the
route.dat and replaces the to_net_addr value with the full route if necessary.
I guess nobody (including me) tried sending QWKnet netmail via JS before.