and no actual observed problem.

malloc'd strings.

elements (member variables) would be changed to point to a string constant.
Don't do that - instead just use local stack variables for those style
element default values. This leads the way to constifying the style arguments
in the future and allows the caller to use non-NULL style elements as indicator
of something that should be freed if the caller allocated some memory for it.

(.ini) file in a single call.

Active Users/SYSTAT protocol query.

front of the list/array, even if it was already in the list.

it should fix the issue of tic files being generated with @domain added to
the From: line and putting tickit into an endless loop.

I have a new use for it in the v3 Terminal Server, it now follows the
"NO_DOS" option in the [bbs] section of the sbbs.ini file. So if you have
multiple Win32 instances of sbbs (like I do), but only some of them
support DOS programs, you can now use this ARS keyword to enable/disable
access to a program based on the existance of DOS support. For example,
I have some 16-bit DOS message editors where I had the ARS set to
"WIN32", but on my 64-bit Windows instance of sbbs (vert.synchro.net),
16-bit DOS programs aren't supported while on my 32-bit Windows instance
(bbs.synchro.net) they are. So I needed a good run-time check for whether
DOS programs were supported or not and this old ARS keyword seemed the
right fit. For Linux builds, this keyword will only evaluate to true if
built with the USE_DOSEMU option.
This is only true of the Terminal Server - use of "DOS" ARS keyword in
other servers and services will still just evaluate to "false".

Cyan's suggested fix for nelgin's mIRC problem.

If a tickit.ini area section has "ForceReplace=true", then it'll treat
all the incoming .tic files for that area as though they have a "Replaces"
keyword.

The modifications are all near the bottom, just to check whether to display
header, leftnav, rightnav etc.

false if the .ini file can't be opened (e.g. doesn't exist).
set() will now return the result of File.iniSetValue() rather than the
result of File.close().

"short name" (e.g. derived from the "AREA tag" from FILEGATE.ZXX) is the same
as a pre-existing dir, just over-write that dir - don't create a new one.

previous commit: don't clear the line counter or call pause() - which will
do nothing - if the console abort flag is set.

would not always auto-redisplay menu files when the user hits 'Q' (or 'N'
or Ctrl-C) at auto-pause prompts:

When displaying a "message" (e.g. file), if the console abort flag is set
before a single line has been displayed, clear the abort flag. This most
likely means a pause (hit a key) prompt was automatically displayed due to
a clear screen code in the message/file and the user hit 'Q' or 'N' or
Ctrl-C at the prompt. In this special case, don't treat that as an
"abort message" command and keep displaying the message/file.

Once one or more lines in the message/file have been displayed, then the
behavior is the same as before: a console abort (even as a result of an
auto-pause prompt key) will stop the display of the current message/file.

In External programs after running Sycnrhonet BBS List you get
"Returning to <BBS> - hit a key". If you presss Q you get a blank external
menu menu rather than the full menu.
The main problem was the line counter, so clearing after returning from
executing an external program (unless the forced pause thing is on).

Throttle bogus command sending clients (one second per bogus command, accumulating).

 term 0087 TLS ERROR 'Unexpected <Unknown type> (24) packet, expected application_data (23)' (-1) popping data
 message repeated 492 times: [ term 0087 TLS ERROR 'Unexpected <Unknown type> (24) packet, expected application_data (23)' (-1) popping data]

When using TLS with a JS Socket object, if there was any kind of data error,
the recvline() method would return a blank string rather than null/undefined.
nntpservice.js just loops when it receives a blank string, so this caused an
infinite loop (with disk-filling error log messages).

First change: if no data has been received (i == 0) and there's any kind of
receive error or timeout or disconnection, just return null. And not undefined,
but null (!) like in v3.15 (before the great JS engine update of 2000-mumble).
Also, there appeared to be a JS_RESUMEREQUEST call missing in the TLS error
return case - so that's another bug fixed.
Commented on the magic return values for js_sock_read_check()
and js_socket_recv().
Simplified js_sock_read_check() return value a tad: let the caller decide if
they want to do something special based on the value of 'i'.
Added some comments to make this code more readable.

We are now no longer treating the different error return values (0 and -1) from
js_socket_recv() special in this function, but we dont' treat them special in
any of the other calls in this file/object either, so that seems to be the
norm.

Deuce really wanted to pass 1000 as a value here (use 1 instead). I don't
know if this was an observable problem or not, but it certainly *looks*
like a bug.

This may resolve Dumas Walker's issue with cross-domain TIC forwarding.
This should really use the value from BinkpSourceAddress, but that would
mean renaming that key and including it in the TicITCfg object, or
creating a new SBBSEchoCfg object method or something, and I don't want
to mess with the sbbsecho.ini format.

first white-space character encountered.

'content-disposition' filename parameter is not terminated with a double-
quote or semi-colon character.

Added version for Bill McGarrity: for each linked-node, a preferred
local address (AKA) can be specified to be used as the source address
when creating packets destined for that linked-node. If no local address
is specified, the previous (best match) logic is used: find an AKA that
has the same zone and net as the destination address, if none found, use
the first address with the same zone.

of the user record is going to fail anyway. *this* explains a lot of
instances of the user.dat file being open concurrently, at least one per
active thread with a JS context.

user data is thusly cached - set the 'cached' property member to TRUE. This
prevents an unnecessary re-read of the user file and the leaving the user file
(user.dat) open, at least for JS contexts that contain a "user" object. I don't
think this explains the "too many open files" errors, but it explains at least
*some* number of the user.dat open file descriptors.

to .msg file doesn't mean you should delete the file attachment! The .msg
file will still be pointing to that file and it needs to be there.
SBBSecho was silently failing to delete file attachments on my system, so
I didn't see this problem. Oops. Anyway, this explains Al's problem with
netmail attachments.

server log output/window.
Also added comment about an observed exception upon shutdown with regards to
the node_threads_running counter (protected int) being accessed after
destruction.

removed.

sbbs::lputs() will log the current user alias already, logline()->lputs() would
create log messages with the user alias twice.

attempted.

with email_sec.js:
line 65: TypeError: addr_list.indexOf is not a function

If yy <= current 2-digit year, yy is assumed to be from this century,
else it is assumed to refer to the previous century.

In the case of a two-digit year, run it through parseInt with radix 10.  On the off chance we look at a message area created from 2000-2009 this will help, I guess.
Go back to putting month and day through parseInt, but specify radix 10.  In some *cough* older JS interpreters, parseInt likes to treat any string beginning with 0 as octal.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt#Octal_interpretations_with_no_radix