2 new configuration params: MaxLogSize (default: 10M) and MaxLogsKept (10)

error: ‘handle_mutex’ undeclared

This reverts commit 6a4fbf28.

This allows the playback thread to open the device and errors to
be checked.  Otherwise, the first sound won't play.

1) user.number immediately after login() remains zero, but changes
   "sometime" after.  Avoid using user.number right after login()
   call to generate filename.  All data/user/0000.imap files can
   be deleted after this change.
2) Saving Seen data would modify the object storing it when binary
   seen values were used.  Use JSON.parse(JSON.stringify() to make
   a copy before saving and restore it afterward.  Should fix issue
   reported by nickshanks1 over IRC.

Addresses issue #239

Also note the spectacularily poorly named WIN_REDRAW and WIN_NODRAW
flags.  WIN_REDRAW indicates that this *is* a redraw of the menu,
which indicates that you don't need to redraw the menu (because it's
already correct on screen).  Weird, but not insane... WIN_NODRAW on
the other hand indicates this is *not* a redraw, and that the window
is incorrect on screen and you therefore *must* redraw the menu.

That is to say:
WIN_REDRAW prevents the window from being redrawn
WIN_NODRAW forces the window to be redrawn

The previous attempt completely disabled pulse audio.

It seems that the "real" ALSA will actually silently fail if you
try to clear errors when no errors have occured.  The FreeBSD
emulation of ALSA does not have this insane requirement, so this
went unnoticed for the 1.1 release.

I suspect that this actually fixes SF bug 24, because ALSA is
preferred over pulseaudio.

The jury is still out on some details...
1) If you press ESC while editing the comment, it currently cancels
   the edit.  Would people expect ESC to exit the program instead?
2) The format/colours of the displayed comment... right now it's
   using the UIFC background colours, and not draing a border or
   window.
3) Just how long should the comment field be, and how should it be
   edited.

While errors on transmit seem to be handled well, errors on receive
do not, especially through js_recv_line() which has been seen to
trigger a large number (hundreds) of ECONNRESET errors.  To prevent
this, simply close the socket when an otherwise unhandled error
occurs.

Almost certainly fixes that issue, but the underlying cause is still
undetermined.  The calling script (imapservice.js) was checking
Socket.is_connected after each recv_line() call, so if the socket
was actually reset, it would be expected to only call it once.

An alternative would be to explicitly handle the error that is
seen (CRYPT_ERROR_PARAM1), but let's try a generic fix first and see
of anything breaks because of it.  Most likely issue would be an
inability to recv() data after calling shutdown(), but I don't think
many people do that except to move the TIME_WAIT to where they want
it.

It fixed an issue in js_socket.c, no reason to expect better
behaviour with TLS.  This may fix SZ YModem-G transfers on
cvs.synchro.net...

Don't include the obsolete unstructured regex in abs.unstrctured,
and use the abnf.unstructured for parsing headers.

This fixes an issue seen running the IMAP server on gratuitously
spammy messages.

- Backtab also exits with K_TABEXIT when the string is selected
- Backspace scrolls the text to the left of the cursor to the right
  if the left of the input is not the start of the string.

This falls squarely into the "How did that ever work?" category.

Fix for Altere's logons yesterday list that isn't rotating out because nobody
logged on today.

Previously, the height was left the same, and the width was set to
the next-lowest "standard" size.  Now the cterm window is set to
the size of the requested mode and both top/bottom and side bars
are added to make the virtual screen the same as the requested one.

Using the "current" mode still retains the old behaviour.

Closes SF request 11

With maximized windows, unexpected behaviour occured when the program
resized itself, then the window manager minimized/restored the window
Should address SF bugs #18 and #13

This is used by some BBSs to enable encryption without needing to
integrate the BBS user base into their SSH server (and presumably
so they don't need to run multiple SSH servers).  All users log in
with the same username (ie: "bbs") and no password is requested or
required.

Once the BBS starts, it prompts for the BBS user name and password
as normal.

In SyncTERM, the user/password/syspass fields are redefined as
SSHuser/BBSuser/BBSpassword and they are moved around when you
change the connection type.  This means that if you change a listing
that has a syspass to SSH (no auth) and back, the syspass is lost.

I'm not sure if I plan to fix this or not.

It would be fine if this only warned while building JS, we're used
to ignoring that, but this bugger warns while building Synchronet
stuff.

Only supported on FreeBSD, Linux, Solaris, OS/2, GNU, Cygwin, and Darwin
Should allow OpenBSD to build JS engine.

Not yet tested, so more patches may be incoming.

There are too many options now to fit in an 80x25 screen, so group
all the log options into a separate sub-menu.

While we're here, notice that we're writing paths up to MAX_PATH
into an 80-character buffer and fix that.