Expanded codes will not *not* go beyond the terminal column width (minus 1).
If you need the old/wrap behavior, add a "-W" modifier to your @-code.
If a length value is specified with -W, it is ignored.

- MSG_TO, MSG_FROM, MSG_SUBJECT now reflect the header values passed
  to sbbs_t::show_msghdr(), JS bbs.show_msg_header() and not necessarily the
  actual stored (e.g. MIME-encoded) header values.

New codes:
- MSG_CC - reflect a message's CC list, if it has one
- DATETIMEZONE - combines DATETIME and TIMEZONE in one string

used to display a CC list, when applicable.

"read mail" module is executed, so that the node action is correct more often.

show_msghdr(), over-riding the values from the passed smbmsg_t. This is useful
for, say, displaying MIME-decoded values rather than the MIME-encoded versions
of the header fields that you often find in email today.

Copy the upvotes, downvotes, and total_votes to the smbmsg_t, replicating
what is done in sbbs_t::scanposts() - these are used by sbbs_t::show_msghdr()
so we need to copy them if we're going to be replicating that functionality
(showing up/down votes and score) in message headers shown with bbs.show_msg()
and bbs.show_msg_header().

  "Upper case should be used"
Compared with RFC0245 Quoted-Printable encoding:
  "Uppercase letters must be used"

<sigh>
Really.. these specs were written by the same (MIME) working-group?

output.
Added a "include_offset" option to the generate() method.

converted to spaces.
Stripping control chars from decoded header values too: we don't want
someone getting cute w/embedded Ctrl-A codes or ANSI escape sequences.

angle brackets in the "RCPT TO" command sent to the SMTP server. This is an old
bug but now appears because we are now (recently) actually storing the SMTP
forward-path in the message header.

   Any amount of linear-space-white between 'encoded-word's,
   even if it includes a CRLF followed by one or more SPACEs,
   is ignored for the purposes of display.

ERROR to WARNING - for Ragnarok.

Add to_cp437() - returns a CP437 representation of the passed header value

settings affect both NetMail and EchoMail import/export.

Removed the X-Comment-To header field (is this file being used for NNTP?).
Added an 'unfold' boolean argument (defaults to true). If false, don't unfold
the header fields.

Removed extra space from LongLineContinuationPrefix (when used, there's
usually already a space following the cond line-break).
Removed the cond-line break from the AutoMsgHdr.

Decodes those funky strings you see in message (e.g. email) headers:
=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=
=?UTF-8?B?UmVtaW5kZXI6IFdlc3Rlcm4gUml2ZXJzaWRlIENvdW50eSBDb21tdW5pdHkg?=

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)

content-type "charset" parameter value and store in the (new) smbmsg_t.charset.
This is a heap-allocated copy of the text from the message body, so it must be
freed in smb_freemsgmem(). When NULL, the charset can be assumed to be
US-ASCII.

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

attempt to resolve infinite recursion bug -- would love to know what word was attempted so I can recreate the issue -- anyone?

Should fix error reported by pfortran on fsxnet.

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
- cc_list
- replyto_list

Always enclose the 'From' name in quotes.
Don't force a reply-to field if subnum is undefined.

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