Renamed MIMEDecodedPlainText to MIMEDecodedPlainTextFmt
(since it is now a printf-style format string).
No special handling of non US-ASCII (e.g. UTF-8) characters... yet.

- mime_version (from the message header, if MIME)
- content_type (from the messgae header, if MIME)
- charset (from the plain-text MIME portion content-type header field)

(when set to Yes).

The default is off (no stripping). Previously, Soft-CRs were always stripped,
but this behavior is now seen as an anachronism as CP437 char 141 is an
important non-English laguage character and used as such in FidoNet msgs.

in switch

nicely when displaying at various terminal widths.

For QuickBBS editors, the default will be the same as previous behavior: to
convert Soft-CRs to Hard-CRs (CRLFs).
For non-QuickBBS editors, the default will be to treat Soft-CRs as any other
valid printable character in the text ("Retain").
A 3rd option is available to strip Soft-CRs completely from the generated
message text.

For QuickBBS editors, the default will be the same as previous behavior: to
convert Soft-CRs to Hard-CRs (CRLFs).
For non-QuickBBS editors, the default will be to treat Soft-CRs as any other
valid printable character in the text ("Retain").
A 3rd option is available to strip Soft-CRs completely from the generated
message text.

when the user is using the internal msg editor (useron_xedit == 0) and
replying to a message.

Refer to the dubious get_msg_body() feature of dot-stuffing as that
("dot-stuffing") and not "rfc822-encoding" - because it isn't.
dot-stuffing is a requirment of SMTP (RFC*821) and NNTP, not RFC822 (oops).

- to_list (RFC822TO, previosuly unavailable via JS)
- cc_list
- replyto_list (RFC822REPLYTO, previously unavailable via JS)

Added RFC822FROM to the "field_list" array (previously unavailable via JS).
Removed SMB_CARBONCOPY from the "field_list" (now duplicated in cc_list).

headers

New text.dat strings:
 - HitYourBackspaceKey
 - CharacterReceivedFmt
 - InvalidBackspaceKeyFmt
 - SwapDeleteKeyQ
 - PetTermDetected

Fix up some message header field lengths.

will be sending 0x7f (DEL) when the backspace key is struck: SWAP_DELETE
For example, xterm sends 0x7f when backspace and hit and an ANSI escape
sequence when the DEL key is hit.

I don't yet have a way to *enable* this setting.

Also, allow the user's setting of NO_EXASCII to take effect even when
auto-terminal type detection is used (yes, the user's terminal can support
ANSI and *not* CP437).

the user's your-scan config (&S using the default shell) even when
"Display subjects only" was confirmed. Previously, when only subjects were
shown, all subs were scanned regardless of user config.
Bug reported by John Hiemenz, thanks!

- DELAY:nn (delay nn 10ths of a second)
- POS:nn (move cursor to position nn, not sure if nn is 0 or 1-based)
- CLREOL (same as CLR2EOL)
- YESCHAR (the character/key for "Yes", from text.dat YNQP string)
- NOCHAR (the character/key for "No', from text.dat YNQP string)

and for good measure:
- QUITCHAR (the character/key for "Quit") - not supported by PCBoard

QOFF - user cannot abort the display of the file
QON - user can abort the display of the file

@X00 saves the current color and @XFF restores that saved color.
Thanks to NuSkooler for the PCBoard manual, which is pretty good.

- getnameinfo() was being called with NI_NUMERICHOST in the mail server and
  web server (but nowhere else)
- use a singly-defined macro (STR_NO_HOSTNAME) for the "<no name>" string
  rather than copying it about
- the webserver apparently assumes that session->host_name will always have
  *some* unique value (e.g. the IP address when no hostname is available) - so
  account for that special need <grumble>

(e.g. "<service> connection accepted from: <ip_addr> port <num>").
Some strcpy->SAFECOPY, sprintf->SAFEPRINTF replacements for good measure.

(i.e. posted to yourself). It's confusing when testing the scan for messages
"to you" if messages also *from* you aren't listed. :-)

Don't allow the use of -if, -ix, -ic options when not a *nix build.

terminal width) - only used when the QUOTEWRAP option is set. Common values:
0 - current behavior, wrap the quote file to the current terminal width
80 - wrap 80 columns specifically (actually, 79)
9999 - unwrap to long lines (one line per paragraph)

terminal width) - only used when the QUOTEWRAP option is set. Common values:
0 - current behavior, wrap the quote file to the current terminal width
80 - wrap 80 columns specifically (actually, 79)
9999 - unwrap to long lines (one line per paragraph)

Actually, previously it was wrapping to current terminal width minus 4 when
QUOTEWRAP was enabled. Now, make that current terminal width minus 1
(when quotewrap_cols is set to 0).

When responding to AreaFix requests, it's normal for create_netmail() to be
called with a NULL 'msg' argument value - so don't try to dereference it
(for the "cols" header field value) if it's NULL. Thanks to Mark Lewis for the
bug report.

(default: off) - when enabled, the current terminal width (columns) will be
saved in the msg header.
When using the internal msg editor or raw intput mode, the columns are always
saved in the message editor. fseditor.js should have this option enabled.
In SCFG, this option is called "Record Terminal Width".

(default: off) - when enabled, the current terminal width (columns) will be
saved in the msg header.
When using the internal msg editor or raw intput mode, the columns are always
saved in the message editor. fseditor.js should have this option enabled.

MIME-encoded/embedded attachments.
We probably will want to do this for SMTP-posted messages (to subs) too.

indicate that a message's body text contains one or more MIME-encoded/embedded
attachments - so that entities won't have to parse the message headers/body
to determine whether or not a message has MIME-attachments.

*_net_type hfield has a value of 0 (NET_NONE) - according to smbdefs.h.