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.

logging in a user. Apparently it's possible to disconnect during an SSH login
and have this function return with useron.number set to a valid user number
even though there was no successful login, leading to undesireable things
happening in logout().

is not "Internet" (e.g. QWKnet or FidoNet).

removed from the ring buffer.  This prevents the session thread from closing
the socket before send() is called with the data.

Fixed issue seen on techdorks.net with the 404.ssjs file (and likely others
where static files were truncated on send).

This ensures that all data that has been send()ed is transmitted.  Timeout
after max_inactivity (max delay is max_inactivity*2).

after a user (has been) disconnected and before the node transitions to waiting
for connection (WFC) status. Usually the duration of this status is very short,
but it can be longer (e.g. for running log-out module and event) and for (new)
msg-scan pointer fix-ups.
Updated logout() to remove some cruft and add some more log/debug output.
Automatic new-scan pointer fix-ups when performing new-message scans (if the
current pointer is greater than the last message number, set it to the last
message number) and when saving message pointers.
Passing user_t* to get/putmsgptrs() instead of message number now (to better
detect Guest account).

Updated the display of kludge lines & header lines so that the label & value will be on one line if they fit that way, to save screen space and reduce the need for scrolling.  Also, added a couple of color configuration options to DefaultTheme.cfg: hdrLineLabelColor and hdrLineValueColor, which lets the sysop specify the colors to use for the header/kludge line labels & values.  Also, updated the readme file & revision history file.  This is still a 'beta' version but is fairly stable.

messages), you can now set the Guest accounts new-msg-scan values. The default
is 0 (no new messages).

messages), you can now set the Guest accounts new-msg-scan values. The default
is 0 (no new messages).
Using a value of 0 for this or the New User Days of Messages value results in a
very fast message pointer initialization (no "Loading Message Pointers..."
delay).

Implemented a workaround with the Frame object when displaying ANSI messages to get the background to refresh/redraw better so that text doesn't get left over when scrolling the message up & down

Sysop can set the number of days-worth of new messages that new users will
see in their first new-message scan (the default is 0, no new messages).
This does lengthen the amount of time that the first "Loading message pointers"
is displayed (it has to go and open all the message bases), but at least new
users are no longer bombarded with thousands of very old messages when they
answer "Yes" to the "Scan for New Messages" prompt. This setting is in
SCFG->System->New User Values->Days of New Messages. Set it to some really
high number (maximum of 9999) if you want the old behavior.