example client.

Will tie into sbbscon.c after DigitalManian approval.

Fixes recvline() returning an zero-length "line" on timeouts, which causes
infinite loops and 100% CPU utilization with IMAPv4-TLS service (and likely
any other service that uses recvline with a short timeout).

Added "Node # SSH" to a lot of SSH-related log messages.
Lowered the severity of the SSH "attempt to use channel" msg from ERROR
to WARNING.
Removed "last:" from temp-ban message when there is no last-used username.

when creating a new netmail message. Not exactly an "address book", but a
convenience nonetheless.

I'm calling these "user properties", but that might change.

exists in a .QWK packet. Also, delete the other control/metadata files
case-insensitively (just in case).

the return value if recv() for non-TLS sockets.

TLS, use MSG_WAITALL for reading integers, add a time() based timeout,
return as soon as any bytes are read (including zero), and generally
behave more closely to how recv() itself behaves.

first one.

reason.

to be changed to something the individual clients can frob in the near
future.

bytes have been sent!

"Sometimes" the write timeout value is used for read timeouts.  Since we
use a read timeout of zero, and a mutex, this can cause some serious delays
in SSH processing.  As a workaround, we set the write timeout to zero.
However, a flush failure has historically been fatal.

So, we now change the write timeout to one second just before a flush, and
have a flush timeout not be fatal anymore... we set it back to zero after
the flush.

The fiddling with the write timouts will be removed once the bug is fixed,
but the flush timout not being fatal may stay forever... add some comments
to remind us to remove the hack in the future.

attempt.

"unique" login attempt (e.g. hack attempt).

code merely introduced a 5 second delay in the Node 0 thread.

(import netmail) command along with the '-n' option to set the recipient
net address (and network type). Previously, only Internet or QWK netmail
was supported.

bad login.

(.sid file), don't divide the fread() results (it's already in number of
records read). This could cause msgbase maintenance to not take place
or corruption of a msg base.

my jsexec includes debug output... and this is super-normal.

Also, change READTIMEOUT back to zero since that issue is fixed now.

log messages.

SSLv3 (!) and even SSLv2(!!) clients still in the wild.  Sysops aren't
expected to be able to fix other peoples ancient broken stuff.

the SSH session.  Also, do an INFO level log entry to indicate what
happened to your socket.

missing "SSH" when logging channel use errors.

sends would cause MAC errors.

so support that.

for a match... which caused a memory leak.

Thanks scan-build!

So, we really should initialize sock to INVALID_SOCKET before calling it.

This should fix the "random descriptors are closed" issue.