Added "can_access" property to message areas and file areas for a quick/easy way for a script to check if the current user has access or not.

the JS User.downloaded_file() method (used by ecWeb's file download stuff).
Thanks Coz.

Try that, Nelgin.

expands to "ld"/"lu", respectively since off_t is a long (not an int):
examples:
ftpsrvr.c:1374:77: warning: format '%d' expects argument of type 'int', but argument 6 has type 'off_t {aka long int}' [-Wformat=]
   lprintf(LOG_WARNING, "%04d <%s> !DATA cannot send file (%s) with size of %"PRIdOFF" bytes"
websrvr.c:6063:45: warning: format '%u' expects argument of type 'unsigned int', but argument 5 has type 'off_t {aka long int}' [-Wformat=]
   lprintf(LOG_INFO,"%04d Sending file: %s (%"PRIuOFF" bytes)"

More file existence/length checks, with only a WARNING log level (not error) since some QWKnet nodes apparently like to start concurrent QWK packet downloads and inevitably one finishes first, deleting the file, and the second transfer logs and error. Examples:
  8/14  08:10:06p  2296 <EPHRAM> downloading QWK packet (1320 bytes) in passive mode
  8/14  08:10:06p  3792 <EPHRAM> downloading QWK packet (1320 bytes) in passive mode
  8/14  08:10:06p  2296 <EPHRAM> DATA Transfer successful: 1320 bytes sent in 0 seconds (2640 cps)
  8/14  08:10:06p  3792 <EPHRAM> !DATA ERROR 2 (No such file or directory) line 1376 opening s:\sbbs\data\file/0888.qwk
  8/14  11:28:55p  2576 <POTOGOLD> downloading QWK packet (27129 bytes) in passive mode
  8/14  11:28:55p  2576 <POTOGOLD> DATA Transfer successful: 27129 bytes sent in 0 seconds (54258 cps)
  8/14  11:28:55p  1924 <POTOGOLD> downloading QWK packet (4294967295 bytes) in passive mode
  8/14  11:28:56p  1924 <POTOGOLD> !DATA ERROR 2 (No such file or directory) line 1376 opening s:\sbbs\data\file/0168.qwk

Also some more 64-bit file length support (flength returns an off_t now, not a ulong).
And ftell() returns a long (not a ulong).

the Amstrad NC100. Someone make a YouTube video, using one of these as a BBS
client to logon and use a Synchronet BBS! That'd be awesome.

cfg.is_operator property:
msglist.js line 339: TypeError: msgbase.cfg is undefined

to non-operators). There's likely still information leaks here, like replying
via email. But could use some testers to help identify those. :-)
For nolageek (CAPSHRIL).

when using iOS (iPad) mail client.

property with bit 31 set would result in a user.setting value of 0xffffffff which means the user is both deleted and inactive (all bits are set).
JS_ValueToInt32() does "bad things" when bit-31 is set in the value being converted, use JS_ValueToECMAInt32 or JS_ValueToECMAUint32 instead.

that don't have strerror_s:
Error: Unresolved external '_strerror_s' referenced from genwrap

filter incoming messages, including vote/poll messages. This should address Nightfox's bug report that polls posted by twit-listed users were still imported/posted on his BBS.

Insure Socket.connect() sets the "error" property to a representative error value when the connection fails.
Previously (on Windows), the "error" property would be set to 0 upon a connection failure.

  text description of last socket error that occurred

Define a thread-safe/re-entrant version of strerror(): safe_strerror() which is just thin wrapper around strerror_s on Windows and strerror_r elsewhere.

Some other timed event related configuration text/help fixes/beautification too.

The problem: the sysop (me) is not notified of critical errors (e.g. synchro.net zone file problems) in a timely manner.
Part of the solution: notify a configured user (e.g. user #1) via short-message/telegram and email/netmail logged-errors when messages of a configured severity (e.g. "Critical") are logged.
The second part of the solution (coming next) will be allowing timed events to log a message of a configurable severity logged when the event fails (returns a non-zero error level to sbbs).

I'm saving the error-notification-user-number and log-severity as part of the node.cnf file because:
- that's where the validation user number is already set
- I can conceive of a large system were certain node ranges (different instances of sbbs) might want different operators to be notified of logged-errors

The problem: the sysop (me) is not notified of critical errors (e.g. synchro.net zone file problems) in a timely manner.
Part of the solution: notify a configured user (e.g. user #1) via short-message/telegram and email/netmail logged-errors when messages of a configured severity (e.g. "Critical") are logged.
The second part of the solution (coming next) will be allowing timed events to log a message of a configurable severity logged when the event fails (returns a non-zero error level to sbbs).

I'm saving the error-notification-user-number and log-severity as part of the node.cnf file because:
- that's where the validation user number is already set
- I can conceive of a large system were certain node ranges (different instances of sbbs) might want different operators to be notified of logged-errors

This also means I eliminated all the legacy com port/modem stuff from the end of the node.cnf file. None of that is used in sbbs v3.

Also included in this commit are improvements around logging:
- reduce the severity of UDP recvfrom failures in services
- a more detailed log message when the mail server successfully delivers an email (via SMTP) - easier to answer the question: was that email you/they sent delivered successfully?

Use Microsoft magic to "ignore regular line breaks in the message definition text." of socket error strings on Windows:
strips the embedded line-feeds from the socket error description.

(and their terminal supports) mouse reporting.

Allow set_mouse() to disable mouse-reporting in the terminal (if it was previously enabled), even when mouse support has been turned off by the user.

for the (newly-added) TerminalMouse string.
Also added MouseTerminalQ string.