Add support for OPTS MLST command.
Fix MLST FEAT response.

in the other stuff too.  The local mounts may not be at 100% either, but
the appear to work.

to be for TLS sessions.

throttling, temp-banning, and filtering.

here in write_file_cfg() where the directories are created.

must be a letter if the second char is a colon.

auto-generated file transfer path (no transfer path specified), in
square brackets.

If the sysop does not specify a file transfer path for a directory, but
did specify a custom data directory, use the custom data directory as the
parent of the auto-generated sub-directory to use for the file storage
path. If this breaks existing configs (are you files are offline?), sorry.

(e.g. "SUBMISSIONS Server" becomes "SMTPS Submission Agent", etc.).
Removed the redundent "<protocol> Server listening" log lines.

the one in RFC3977.  Technically, you could have those groups, you just
couldn't have any netnews articles in them.  :-)

If there's a problem, bounce() will re-log them as LOG_WARNING later.

and fix all the things.

Hopefully this allows fallback to plaintext after a TLS failure now.

setting the session active.

user name (once authenticated).
Lower the log level of the POP3S "Unable to set session active" messages,
apparently these are normal occurence with drive-by bots and not error.log
worthy.
Fixed the !Cryptlib error in sock_recvbyte log output (sock, not socket).

failure... do that.

not everyone is that inept.

entry - if there's an actual compile error, it should already be logged
via the exception/error-reporter callback. This should eliminate a lot of
the dokuwiki-related error chatter in my error.log.

"Enable to" (TLS-related) error messages. This might help a little to
understand why these errors are happening and allow us to consider
lowering the log level(s) of commonly-occuring cases from LOG_ERR.

support though.

ESMTPS and ESMTPSA coming soon!

newsgroup property.

Note that any exascii is also illegal, but I don't feel like doing the
UTF-8 conversion thing today.  Also, you can manually stick in illegal
characters if you like... but then it's a feature, not a bug.

Should fix possible issue with certificate being owned by root when
_THREAD_SUID_BROKEN is true (ie: Linux).

port number. This resolves the confusion that arises from multiple
identical "closing x Server socket on port n" lines in the log output.

(for subs and "all mail") and 4-digit message numbers. Subs with >9999 msgs
are not unheard of and its easy to accumulate that much mail in the mail base
these days. Just eliminated the ':' from the format line(s) to make room.

These waits could cause "bad" traffic (blocked, max client exceeded, etc)
to prevent/delay accept()ing "good" traffic on other services.