about undeclared functions (vasprintf and pthread_setname_np) when building
sbbs3.

(PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP) - when we defined _GNU_SOURCE,
assigning that macro value to list->mutex triggers a GCC compiler error.

is defined - resolves gcc warning in ftpsrvr.c.

This has apparently never been implemented for non-TLS sockets, but it
is used by some.

Call FULLPATH() on local directories after changing
Add cdir to MLSD in the bbs: mount
Return full path in MLST

(dirs and files).  Include the unique fact in aliases as well.  Clients can
now tell that aliases are the same entry.

For MLST <dir>, always return the full path of the dir instead of the
specified or relative path.

Likely some other minor fixes as well.

free() the mailproc causes a double-free crash.

like symlinks... note that they aren't shown as symlinks in the directory
output, so it may be a bit of a surprise when relative paths are relative
to the target rather than the alias.

tasks in timed events).

excessive log output from packing-QWK events.

the startup->socket_open() callback wasn't being called.
I'm not sure if this is correct with the *nix Spy socket stuff however.

to handle this somehow (but currently doesn't).
Also, remove some debug output.

Add the '..' parent directory to libs and dirs
Fly the TVFS flag now that relative dirs are working

LIST should likely check the return value now...

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.

files (sending or receiving).

Does not support CRAM-MD5 challenges longer than 16 bytes (32 hex chars)

I'm probably doing something wrong here, since I didn't write this code
(particularly if there are multiple advertised addresses in the session
which we have configured links for) - but this should at least give Al
something to test.

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.