sequence is currently just the <esc>[V and <esc>[U sequences (supported by
SyncTERM).

timeout (usually longer).

Don't export the 'entry' property of the BBS object to msg base(s).

soon.

argument, in case the caller doesn't want 76 characters per encoded line.

exists in the message body.

stupidity that results in all the entries being removed and protect against
simultaneous edits and such.

a one line script, but it's handy.

When displaying message body text, skip all initial ocurrences of CR or LF
(rather than all initial white-space). Some people use white-space for
centering or justifying blocks of text and we don't want to mess up the
presentation of their messages.

CR or LF, just a convenience wrapper for SKIP/FIND_CHARSET(p, "\r\n")

* Implemeneted Add and Remove commands
* Begun implementation of Edit command
* Smplified json model a bit:
- bbs.xtrns -> bbs.doors
- bbs.software.bbs -> bbs.software
- bbs.terminal.support[.type] -> bbs.terminal.types[]
- dates are always stored as strings (rather than just sometimes)

chat, rather than the old startup options flag ([BBS]->SYSOP_AVAILABLE).
This will be much easier for other processes/programs to query and control.

I likely wrote this so BinkIT could make NetMail great again... then I moved
to Michigan and got drunk.

A lot of LDesc stuff has leading whitespace.

be defined.

environment variable (to the same value as SBBSNNUM) as some door games
(e.g. Bordello, by T&J Software) have support for this environment variable
built into their configuration file parsing. This makes setting up multiple
nodes much easier/faster, as you can re-use the same configuration file for
all of them by just specifying this environment variable in the .cfg file
(e.g. "c:\sbbs\node%PCBNODE%\door.sys"). Unfortunately, you can't use just
*any* environment variable, it has to be one of the ones specifically supported
by their programs (or door frame door kit?). Anyway, this simple hack can save
a lot of time setting up some of these doors.
I did not do this for executing native (32-bit) programs as I'm pretty sure
there was never a 32-bit version of PCBoard, so that wouldn't make much sense.

Version 1.17 beta 49: Fixed a bug when marking messages as 'read' when the user reads messages that were written to them - It was getting an 'expanded headers' error with recent builds (on/after December 1, 2017).  A similar error used to happen occasionally but not all the time.

Pass 'false' for the expand_fields argument to MsgBase.get_msg_header() since
we call put_msg_header() later with this same message header.

we call put_msg_header() later with this same message header.

has a MIME-encoded file attachment, decode that attachment into a file and
attach to the message FTN-style.
- This allows sending of FTN file attached netmail using your Internet email
  client.
- Only a single attachment is supported (consistent with all attachment support
  in SBBSecho).
create_netmail() enhancements:
Don't add the FLAGS control line if we're in FLO-mode - this line is not used
by BSO/FLO mailers.
If there is a file attachment, but the message contains a subject, add a
Subject: <original subject> line to the message body, since FTN requires the
attached filename be placed in the subject.

(because we're writing the modified header back).

incrementing the argv index in a call to JSSTRING_TO_MSTRING causes the
index to be incremented twice!

portion of the To: header field in the RECIPIENT name as FTN software
doesn't typically expect/handle that.

get the "plain text" part only - this solves one problem with using an Internet
email program to send NetMail. The next problem (ToDo) would be to extract
MIME-encoded file attachment(s) and export them the FidoNet way.

Version 1.17 beta 48 - Bug fix: When listing messages in reverse order in lightbar mode and all messages are selected/de-selected, the checkmarks on the screen now update properly.  Also, updated so that when listing personal email, it will use the regular formatting colors rather than the colors for messages to the user, since all personal emails are to the user (the 'to user' colors for each email might be obnoxious).

<PAGING> tag in the ndoe status display.

supported), remove the file path information from the message subject
(it's not needed and could be seen as a security issue).

an errorneous exit (and trigger the -! pause on error).

before the IPv6 changes made in rev1.615. This also left the localspy#.sock
files in the temp directory after sbbs was shutdown, so that's now fixed.

When fixing a non-hyper-allocated message base, the newly created .sha
(header allocation) file would contain one extra zero-record because I
wasn't accounting for the SMB/status header (32 bytes) in the .shd file
when I was initialing the new .sha file. This explains chksmb warning
	!Size of SHA file (x) does not match SHD file (y)
after running fixsmb on a message base.

a message for the sysop.

controls. Since Nov-28-2016, this would trigger a recycle of all the servers,
which was really unecessary. So instead, just make sure we save the .ini file
when the program closes (in addition to the other times its saved).