new Socket(true) // creates an IPv6 TCP socket
new Socket(SOCK_STREAM, true) // creates an IPv6 TCP socket
new Socket(SOCK_DGRAM, true) // creates an IPv6 UDP socket
new Socket("myprot", true) // creates an IPv6 TCP socket named "myprot"

support to the JS API.

success. Upon failure to resolve, resolve_ip() returns null.

exit), just log the error and continue processing. Reported by wkitty42.

- Don't ever try to unpack a 0-byte file.
- Don't log anything or try delete if the file is < 24 hours old.
- Try to delete the file if it's >= 24 hours old (and log a msg, INFO-level).

I plan to convert all these to wiki-syntax eventually anyway.

show_msghdr()

contain UTF-8 characters.

The following message list formats were changed to no longer
artificially limit the length of displayed message subjects. If you have
a wide terminal (> 80 cols), show more of the message subject.
This is done by using the newly-supported bprintf(P_TRUNCATE,...)
feature, so no printf-format magic needed here.
- MailWaitingLstFmt
- MailOnSystemLstFmt
- SubMsgLstFmt

The following message list formats were changed to no longer
artificially limit the length of displayed message subjects. If you have
a wide terminal (> 80 cols), show more of the message subject.
This is done by using the newly-supported bprintf(P_TRUNCATE,...)
feature, so no printf-format magic needed here.

- Use the P_TRUNCATE pmode flag to prevent long msg subj from wrapping the
  terminal
- Use msghdr_text() to do the magic UTF-8/CP437 dance for messages with UTF-8
  header fields (e.g. to/from/subject)

This is why I assigned MSG_HFIELDS_UTF8 the same bit-flag value as P_UTF8. :-)

auto-limiting the length of printed lines to avoid  terminal line wrapping.
putmsg() already supported this pmode flag.

when decoding. Linear-white-space between regular atoms or between atoms
and encoded words is retained (as a single space character, Yoda).

flag in the message header.
When displaying message header fields containing UTF-8 using show_msghdr()
with text.dat string or with msghdr.asc and @-codes, do the "dance" to be sure
it's displayed correctly depending on the user's terminal (UTF-8 or not).

Advertise STARTTLS support (in EHLO response) when *not* already using a TLS
connection.

a message is posted to a different conference than the original sub-board with
completely different header information. I suspect this has something to do
HEADERS.DAT creation or import - not sure. So I added a "Conference"
headers.dat field for *messages* (it already existed for votes) and use that
value to confirm that the message header at the associated offset value in the
QWK packet has the same conference number as the section in the headers.dat
file. This is really just a sanity check and will only catch messages that were
mistakening cross-posted (to a different conference) - *but* it log errors and
save the bad QWK or REP file for me to examine more closely and see what's
going on - and the message won't be imported (just "lost", which is also bad).

So added more QWK import success/error checking and logging (especially for QWK
packets since REP importing already had a lot of stats covered).

Another check would be to store the original message number in the headers.dat
file as well and use that to confirm that the headers.dat section is the
correct match for the QWK message at that offset. I did not implement this
check, yet. The conference number check seems like it'll catch most of the bad
msgs and lead me to the root-cause.

pointer type mismatch in conditional expression
format '%s' expects argument of type 'char *', but argument 5 has type 'void *'

(in addition to the auto-ZMODEM upload detection). Using an evil "goto" for
code reuse.

Discards any previously quoted/typed text, but remains in the editor with the
uploaded text available for append or edit.

any previously quoted/typed text and save as the final message text (no
editing). Useful for upload of pre-written messages or ANSI art or whatever.

(defauls to enabled, for backward compatibility).
Added new autohang args to bbs.send_file() and bbs.receive_file() (default:true)
Added support for "description" argument to bbs.send_file() as well.

auxattr flag since we normally want the attach file to be deleted automatically
when the message is delivered. SBBSecho now won't be deleting the file
attachment unless this flag (or the .msg \1FLAGS "KFS" equivalent flag) is set.

file-attachment deletion in write_flofile() - not the KILLSENT attribute flag.
Export the SMB MSG_KILLSENT auxattr from SMB mail to FTN netmail \1FLAGS KFS.

"UTF-8", set the msg's auxattr MSG_HFIELDS_UTF8 flag because FTS-5003 states:
  "The character set identifier applies to all parts of the message,
   including the header information and the control lines like origin
   and tear line."

MIME-encoded.
If any RFC822* header field is a MIME-encoded UTF-8 string, then set the
(new) auxattr MSG_HFIELDS_UTF8 flag. This will be used (soon, hopefully) to
display UTF-8 encoded header fields to users. There's a gotchas here:
- MIME-encoded header fields with other non-ASCII/8-bit charsets (e.g. CP437,
  ISO-8859) are still stored "as decoded", though the MSG_HFIELDS_UTF8 flag
  may be set *later* (which would be weird), resulting in a mixture of valid
  and invalid UTF-8 header fields. One solution would be to UTF-8-transcode all
  the non-UTF-8 header fields if *any* of them are UTF-8, but we wouldn't
  know which charset to translate *from*. Assuming CP437 isn't going to be
  correct 100% of the time - so punt for now and deal with it at display
  time. e.g. if the MSG_HFIELD_UTF8 auxattr flag is set, but an hfield contains
  invalid UTF-8 data, don't display as UTF-8 (e.g. treat as CP437). We don't
  have translations for other charsets (e.g. ISO-8859) setup yet anyway.

- this is the version used in SyncTERM v1.0.
I happened to try SyncTERM 0.9.5b recently (CTERm 1.151) and it failed
to either load or activate loaded fonts, so: not-supported.