- if the sysop had text/menu/<filename>.bak (for example), the optoinal menu
  would attempt to load, resulting in an error ("<filename>.asc not found")
- if the sysop specified menu_file or menu_dir (e.g. via Baja), the existing
  checks for optional menu file existance would not work

<ESC>[5~ and <ESC>[6~ (these appear to be VT-220 sequences).

Not defined in MSVC2013.
Appears to work again/still.

input on Windows (e.g. the prompt() method no longer worked) broke JSDoor,
and caused Windows and Linux console input to behave differently.  Create
functions to cook/thaw the tty, and call them around stdin things.
This change was related to his postpoll.js work, so that might be broken now.

than non-SPAM-tagged email.

xpbeep.c assumes you have sys/ioctl.h on *nix now. Hope you do, mr. fbsd.

SPAM-tagged messages will not be listed/downloaded. This is useful if for
example you use POP3 to download mail to your phone and have limited
storage or sorting options. The SPAM-tagged messages will remain in your
inbox on the BBS so you should use another POP3 or local mail client to
download and delete those messages (which could potentially include
false positives).

and Ctrl-N (next) instead Ctrl-U and Ctrl-D as that wasn't going to work with
fseditor.js's (Ctrl-U is quote).

SBBSCTRL is set. Also changed the library versioning from 3.16 to 3.17.

Created 'install' and 'symlinks' targets to ease the copying (install) or creating of symlinks after build, requires SBBSEXEC env var

(helpful in determining proper BSO directory for an "othernet" zone).

-> Advanced tab

lines - don't check the (invalid) sbbs_t:useron.qwk settings for QWKE
support in this case (!).
If you've been seeing the occasional message with "Subject:" as the first
line followed by some @-kludge lines (e.g. @MSGID, @TZ, etc.) this would
be the cause: you have QWKE support enabled on your hub BBS (e.g. VERT),
which adds the "Subject:" kludge lines for subjects > 25 chars and when
importing QWK messages from a *hub*, these lines weren't (normally)
parsed/stripped.

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

exists in the message body.

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")

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

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.

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.

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.

<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.

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).

- VoteInThisPollNow
- MIMEDecodedPlainText