rather than the "from" address. This is necessary for the listserver.js to
properly recognize and process/delete bounce messages (e.g. posted to a sub
by a local user aand exported to the list).

DNSBL).

are now configurable via the following news keys in the [Mail] section of the
sbbs.ini file:
	NewMailNotice
	ForwardNotice

Using the newly updated string literal support to allow for Ctrl-A codes using
C charater literal notation (\1) for control-A codes and standard C-escaping
of carriage-return (\r), line-feed (\n), etc.
Beginning and trailing space characters are also preserved (if specified) in
the key values.

The default strings are updated/different from what was previously hard-coded
in mailsrvr.c. If you want the local timestamp (back) in the notice, change
the '%.0s' in the default string to just '%s'.

globally (using a new macro in sbbbsdefs.h: STR_UNKNOWN_USER). "<unknown>"
in some contexts was too vague (e.g. the 'c' command output from the sbbs
console).

incoming mail): it turns out, stripping tabs (ctrl-i) is breaks many folded
header fields (e.g. MIME-encoded messages).
So, just strip bare carriage returns instead, as that was the original problem.

SPAMMERS insert these either intentionally or mistakenly and they can defeat
security checks (like mailauth.js).

Don't repeat the full email address if no name was provided.
Highlight the word "e-mail" (sorry, I know this should be in the text.dat).

temp-ban (was logging the total number of login attempts, including dupes).

so use shorter thread names.

How did startup->sem_chk_freq get set (back) to 0 in the first place?
The reason: the startup struct sanitization only occured when the various
server threads were first started. When recycled, the server would call back to
the original caller (e.g. sbbscon) which may (and did) re-read the sbbs.ini
file, which could have SemCheckFrequency set to 0 (or missing) and the
sanitization did not happen again (so a 0 value was used in select() calls,
resuilting in high CPU utilization for several threads).

So now, all startup struct sanitization occurs inside the init/recycle loop
and sem_chk_freq should never revert to 0 again. This was the main bug.

value is missing or set to 0 in the sbbs.ini file, the sanity checking this
value (setting it to 2 seconds) will not occur after a server recycle and the
sbbs.ini is re-parsed. So if for any reason, the sem_chk_freq value becomes
0, these server threads won't hog the CPU because they all YIELD at the
top of thier main loops.

Also, changed all the thread names (e.g. adding "sbbs/" prefix), so they're
more sensible in the Linux 'top' output.

Also, started adding 'vi' modelines to auto-set tabstops when using vi/vim.

- Closures (polls can be closed for new voting by the pollster)
- Results can have configurable visibility:
  a. Only to voters (and the pollster) - the default
  b. Everyone
  c. Everyone once the poll has closed
  d. Only the pollster

Changes to smb_getmsgtxt():
Main change: poll questions can now be quoted when replying to a posted poll
(the results cannot be quoted).
Also: there's now automatically a blank line inserted between comment header
fields and poll answers or the msg body text.
Also: upon any malloc failure, the function now returns NULL.
New functions: smb_msg_is_from() and smb_addpollclosure().

loginFailure() now handles a NULL password argument correctly.

file (in .can file format) which lists IP addresses or hostnames which will
be exempt from temporary bans or permanent filters.

this is not a totally unexpected occurrance. No need to fill up the error.log.

- Never ban the server's own address
- Log the login attempt and last name attempted
- Use a compressed version of the HH:MM:SS "time remaining" portion of the log
  message

By default, after 20 consecutive (unique) failed login attempts, *or*
a failed login attempt wtih a name from the name.can filter file.
The default temporary ban duration is 10 minutes.
The temporary ban thershold is configurable via LoginAttemptTempBanThreshold
in sbbs.ini and the ban duration is configurable via LoginAttemptTempBanDuration
(in seconds).

the constructor things.  This allows TLS-enabled services to work correctly,
and removes an ugly hack from the web server.

There's still an odd issue with the NNTP service when using TLS though.

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

FidoNet NetMail can now be gated to an SMTP client (as before), but replies are
now successfully gated back to FTN NetMail. This uses a new more RFC-compliant
To/From address header field format, so older messages (previously gated to
an SMTP client) cannot be successfully replied-to. Tested with Microsoft
"Windows Live Mail 2012" (previously known as Outlook Express).
Test reports/results with other SMTP mail clients would be welcome.

Requires SBBSecho v2.30 or later. File attachments are not yet supported.

those OSs which require it to be correct (ie: FreeBSD).

(needed for ircmsg.js send-failure handling).

Also set the web server status to "Listening" once initializating is complete.
I'm not sure what the newly-introduced "terminated" flag is supposed to
indicate, but it's beign set to TRUE during recycle, so it's probably not
working as intended. Something cleaner probably should be done, but I don't
know exactly what Deuce was trying to accomlish with this variable.

log entries.

addresses specified in the Interface line of sbbs.ini for the server.

before re-reading them.

xpms_add_chararray_list instead.  Prevents having to free string lists
in the sbbs.ini parsing code.

New Features:
- Multiple bindings for each service
  Use comma-separated interfaces on Interface= lines in the ini file.
  Default is now "0.0.0.0,::"
- IPv6 support
- TLS support for the webserver and (non-static) services
  New TLS option in services.ini (ie: Options=TLS)
- Decrease LEN_SCAN_CMD to 35 chars, increase the CID field to 45 chars,
  and rename the MAIL_CMD string to IPADDR.  I think this frees up the
  note field for SysOp use.

scripts global scope (as opposed to js.global which is the instance global
scope), and having exit() define exit_code in js.scope instead of js.global.

This also sets exit_code in js.scope to null when preparing to execute a new
script.  If a new script starts in the same scope as an old one, the old
exit_code value will be destroyed.

This should only impact scripts where js.global != js.scope (bbs.exec()ed,
and mailsrvr)

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)