hashing all source types).

free the results of smb_msghashes().

files in "delete" prompt, also fixes "sub-board" copy/paste typo.

then would return FALSE (even if there was a matching file that would be found
next).

When deleting sub-board data from groups >= 2 (not the first msg group),
the wrong sub-board data would be deleted.
Display the path/filenames to be deleted in prompt for deletion.

yes/no to a selection between QuickBBS MSGINF/MSGTMP and
WWIV EDITOR.INF/RESULT.ED.

in the database, doesn't give credits, etc. So it only supports "free" download
directories that guest/everyone has access to.

Thanks derek!

ars.c:1282:7: warning: no newline at end of file

to execute anything (just return -1).

once the current user had the 'G' restriction.

(and not the RFC882REPLYTO header field), send the Reply-To header as
Reply-To: "name" <addr>

instance (e.g. sbbs->useron) - this should solve the problem with an online
Guest user not getting account changes made via JS scripts (e.g. logon.js).
This may create other unforeseen problems. :-)

Fixed script exit evaluation to remove user file properly. Reworked Init() function to be more simplified

name.

made during the script to be loaded into the BBS.

with the ARS HOST and IP keywords (and the AccessRequirements key).

This should prevent stale messages from entering QWK networks.
Updated QWK log output messages to include "QWK" in them.

DIR <code>) are now handled correctly. The PROT (protocol) keyword never worked
correctly.
Some ambiguities (e.g. "PROT NOTIFY" and "PROT NOT IFY") are now handled more
gracefully. White-space is now required after AND/OR/EQUAL/NOT if the next char
is a letter. All the examples in http://synchro.net/docs/security.html
still work as documented.

Added HOST and IP keywords to allow restricted access/privileges to/for
specific remote hostnames or IP addresses (wildcards allowed).
All string-argument type ARS keywords (e.g. SHELL, PROT, etc.) now support .can
style wildcards.
The current remote client is now used for protocol, host, and IP ARS checking,
when available, so this requires passing the client pointer around (which
explains why so many files are touched by this change) and takes care of a
long standing to-do item (the user's 'modem' value was used for the PROT
value checking, which was not always correct).

Style update.
No functional changes.

IP addresses (with wildcards) that the associated mailproc will run for.
Bug-fix: the SMB REPLYTONETADDR header field value would be created
invalid if the sender's Reply-To header field value contained a name, like:
"Rob Swindell" <rob@someserver.com>
Raise the log level of the SMTP ALIAS log lines from info to debug.
Generate an info-level log entry when receiving message text.

is a negative search (i.e. begins with '!'), then every string must match
for the function to return TRUE.

from sender's claiming to be <anyone>@<yourdomains> are SMTP-authenticated
using a non-Guest user account

Configured in ctrl/mailproc.ini (as the first processor):
[MailAuth]
        Command=mailauth.js
        AccessRequirements=user equal 0 or guest
        Disabled=false