Update JSDOCS descriptions of user props.

illegal (e.g. begins with a space, is in the name.can, alias.cfg, etc.)
This was Cyan's intention, but I guess he never got around to it.
Fixed the default new user editor default selection (lower case internal code)
Does no one test this stuff?

changed FileNotThere text.dat entry to FileDoesNotExist which displays the file
path.

changed FileNotThere text.dat entry to FileDoesNotExist which displays the file
path.
Now check if the directory exists before checking the available disk space
before allowing file uploads and report the correct error (using
DirectoryDoesNotExist) if the directory is missing (a common mistake).
Overhaul viewfilecontents() - wow, I can't wait to re-write all of this moldy
filebase code!

can crash SpiderMonkey as it tries to report the error.

response line, "Timelord" reported a problem with some news server sending
> 512-byte response lines for the XOVER command

conversion from string.  This allows dates from the last couple years to work

*cough*

Enfore integer limits when writing.
Add local variable declarations where needed to avoid clobbering globals.

of recipient mail addresses (for Deuce).

of recipient mail addresses (for Deuce).

of recipient mail addresses (for Deuce).

not have the default entry (*.synchro.net) allow SPAM from DNSBL-listed servers
sending MAIL FROM <spammer@yourbbs.synchro.net> to sysop@yourbbs.synchro.net
A dnsbl_exempt.cfg entry of "*.synchro.net>" would be required to match
<spammer@yourbbs.synchro.net>

address (reverse path) is listed in the dnsbl_exempt.cfg (without the <>), any
positive DNSBL result on the sender's IP address will be ignored.
* Automatically adds ("white-lists") recipients of mail that was successfully
delivered by the sendmail thread to the dnsbl_exempt.cfg file if they're not
already listed.
* Local submit performance improvements: don't perform ip.can, host.can or
spamblock.cfg searches or DNSBL server queries for local connections (from
localhost or the same IP as the server is listening).

in the protocol document and are handled elsewhere.

Apparently if you assign a double to an unsigned char, some loss of precision
may occur (gasp!)

Restore original hold status for local input.
Ensure hold update is FALSE while starting transfers.