Broken in rev 1.561 by Deuce:
"Remove *_TO_STRING() and remove some uselss code to return a string value from
the log() JS command." - the "useless code" enabled behavior which the
listserver.js (and possible other JS scripts) depend on.

clients, timeouts, etc.) into the various *srvr.h files and use them instead of
hard-coded constants sprinkled through-out the .c files.
If the web server "max_clients" key isn't specified in the sbbs.ini file,
use 0 (unlimited) for the max_clients value.

  obvious)

(sans angle brackets), before any "name alias" conversion - in addition to the
current matching (against just the name portion of the recipient address or the
aliased target). This allows external mail processor selection/filtering based
on 'to' address even when using an alias to go to a common user (e.g. user #1).

Now using a local-scope variable for temporary mailproc pointer.
Log a warning when external mail processor creates an error drop file.

has been configured to 0 (unlimited).

sendmail thread was running.

We don't really need to check active_clients (redundant with thread_count)
before allowing recycle.

related crashes (mainly due to null pointer dereferences of scfg_t members
freed in cleanup()).
Use of new protected_int_value()  for extra paranoia (but can't use it on
destroyed protected-int's).

as spammers are now hijacking common/valid mail subjects (e.g.
"Google Email Verification") for their spam messages and blocking all msgs with
such subjects is too heavy-handed an approach. :-(

if a received messages is for local or relay. This comparison predates the
domains.cfg file which makes it obsolete. And it really bugged Deuce and
apparently was a problem for his new IPv6-happy version of resolve_ip(). :-P

the log() JS command.

I've likely broken something though, so if you see weird behaviour with
extended ASCII, let me know please.

similar to the FTP server (wait forever for all child threads to terminate).

Wait double the inactivity timeout value for the acknowledgement (250 response)
when sending messages to avoid sending duplicates (an observed problem
with very large messages/attachments).

external mail processors.

empty *IF* the message was redirected to a sub-board.
If not (recipient list empty, but not to a sub), return OK response.

list file (without actually deleting the file), don't bother saving the message
to the message base.

This is *likely* to break the Win32 build and even when the macros are
specified in xpdev, I doubt Microsoft has added support for the 'z' size
specifier used in smblib/smbadd.c we'll likely need a SIZE_T_SIZE macro
that is "z" on C99 systems and "ll" or "64" or whatever it is on Win32.

Or maybe a whole slew of complete SIZE_T macros since the 32/64 but thing
and the max file size thing may actually need the full format specification
to be in the macro... "zu" on C99 platforms and whatever magic Microsoft
needs there.

and leave it rooted until the script is done or the context is destroyed.

This should clean up crashes before a script starts (ie: While creating
common objects)

has its own functional "too much recursion" detection.
Replaced "branch callback" stuff with "operational callback".
JavaScriptBranchLimit has been replaced with JavaScriptTimeLimit
(default value: 24 hours)

Currently, the return value and result of js_mailproc() isn't used anywhere
anyway. <shrug> Not compiled/tested.

functions when an excpetion is pending.

Some work still needs to be done on js_msgbase.c,  js_user.c, and mailsrvr.c

all exported functions and data types using a 32-bit time_t (time32_t).
(part 2 of 2)

Only js_ValueToStringBytes() still leaks.

      on the floor of Deuce's computer room
Cyan: Rob's on his way
* Deuce throws his coffee on it.

variables.
Log socket descriptor number (when available) with bounce log messages
(and prefix "SEND" like all other sendmail thread log messages).

The connect timeout is now configurable in sbbs.ini [Mail] ConnectTimeout
(default = 30 seconds), set to 0 for blocking connections (and OS-default
timeout).

- if configured max recipients = 0 means unlimited (for all users)
- max recipients limit is applied to pending send emails (non-M-exempt users)
- M-restricted users can not receive unauthenticated SMTP mail messages
- Introduced inbox msg limit (for non-M-exempt users) with sbbs.ini [Mail]
  MaxMsgsWaiting value (default: 100), 0 = unlimited

destination server: if an MX server connection fails, "negative cache"
the failure for that iteration of the sending loop so we don't attempt to
reconnect to the same server(s) repeatedly for the same iteration (and let
other mail get out more quickly).

user that supplies a > 9 char password which happens to match a user's password
when truncated to 8 chars.