Copy/paste errors from 2002 (changes -> uifc.changes in the help text).
Use "save/restore" uifc.list() mode, rather than "remain active" for
"Save Changes" prompt - no need to leave the prompt visible while saving
changes.

When processing area manager netmail messages, SBBSecho can modify
(add/change) keys in the [node:*] section of the sbbsecho.ini file. Although
SBBSecho would read node sections that had a domain (e.g. 5D address) just fine
when processing area manager changes and writing those changes back to the
sbbsecho.ini, only 4D addresses (no "@domain") were used in the section naming.
This could result in duplicate node sections being created in the sbbsecho.ini
file (one with a "@domain", one without) and then "bad things" could happen
(e.g. BinkP authentication failures, packet authentication failures, etc.).

Now, when SBBSecho writes linked-node setting to the sbbsecho.ini, it first
checks for the full 5D address of the node and if that section exists, modify
it, otherwise fall-through to the 3D/4D address of the node for the sectoin
naming.

getting kind of crazy common now and being employed even when totally
unnecessary (e.g. encoding strings that contain just plain ASCII):
- normalize message header fields, when possible
- normalize UTF-8 encoded characters, when possible (e.g. special punctuation
  chars)

This allows text filters (e.g. subject.can, name.can) to work on MIME-encoded
header fields and notifications about received e-mails are legible to humans.

Encoded-words that contain actual non-ASCII/CP437 chars (e.g. foreign symbols,
emojis) are left as encoded-words to be dealt with by whatever displays the
message header.

Special handling of folded normalized field values was necessary because
"White space between adjacent 'encoded-word's is not displayed." (per RFC 2047)

This introduces a new request field send_content which indicates if the
content should be sent.  This covers various cases like HEAD responses
where there's an entity, but no content is sent as well as 204, 304, and 1xx
responses where there is not even an entity.

writebuf() will now enforce this, so there's no need for various checks
throughout the code to see if data should be sent or not.

Also, we now only set sent_headers after the headers are sent.

1) Send Content-Length even if we will be closing the connection.
2) Send the highest HTTP version in the status line that has the same major version.

resolved host-name on "Hostname:" log lines.

CryptSupport (default true), to:
PlainTextOnly (default false).

With this option, it is now possible to support CRAM-MD5 authenication while
not allowing encrypted sessions (inbound or outbound) - not sure why.

(strtok can return NULL).

Weird.

one or the other.

*sigh*

Backspace (the "Delete" key on a MacBookPro keyboard) is treated the same
as ESC (exit).
Make the help status bar more clear in Mac OS X builds that the '+' key
may be used in place of the INSert key to add itesm and that fn-DELete key
sequence is used to delete items (or the '-' key, though that isn't stated).

treat the same Delete Char. This is for systems were there is no "Delete Char"
key (e.g. Mac) or where the Delete and Backspace keys send the reverse key
codes. On a Mac, the Backspace key is actually labeled "Delete", so treat
the key-code sent as "Delete item", consistent with the status bar/help
indicator.

on a Mac keyboard and although that key sends the ASCII DEL char (127), we're
converting it to backspace (^H) here. But if the user actually wants the
"delete character" key functionality, there is no dedicated key, so treat
Ctrl-Delete (on a Mac) as Delete (not backspace).

don't need it.

This should fix OS X (and other systems) doing weird things when they
exit SyncTERM.  We were forcibly preventing atexit() handlers from running,
and pretty much everything installed some of them.

reply code.  Maybe this used to be on the same line as the BBS name?

Make resume only perform any actions if curses is suspended.
This may fix the Syncterm OS X raw on exit in -iC mode.
(But may not either)

May fix OS X stack clobbering issue.

never maintened or used since. So... remove from CVS.