message-ID (e.g. when exporting from SBBSecho).
This addresses compliance with this [editorialized] clause in FTS-9:
     No system
     should ever add an MSGID and/or REPLY to,  or modify an existing
     MSGID / REPLY contained in,  a message not originating on that [FTN]
     system.

Messages gated from other networks (technically coming from another system,
but originating into an FTN from this system) will still have an FTN Message-ID
generated/added.

Since SBBSecho normally tosses to downlinks directly from packets, this adding
of generated Message-IDs would no normally occur. However, if a downlink
rescanned an area, any messages missing Message-IDs would get them generated
automatically and they would appear to have originating on the local system.
This was never the intention, so this is just a long standing but infrequently
observed (and never reported) bug.

for Australian and New Zealand timezone abbreviations/value-macros.

- user alias was missing from some messages or in the wrong place
- added hostname and IP address to the "ILLEGAL FILENAME ATTEMPT" warnings

comparison between signed and unsigned integer expressions

"SYD" (Sydney) +10:00, is now "AEST" with a DST (+11:00) counterpart, AEDT.
Added ACST (+9:30) with its DST (+10:30) counterpart, ACDT.
"WEL" (Wellington) +12:00 is now "NZST" with a DST (+13:00) counterpart,
NZDT.

exec.cpp:438:8: error: case value evaluates to 2684500526, which cannot be narrowed to type 'int32_t' (aka 'int')
      [-Wc++11-narrowing]
                case 0xA0023A2E:
                     ^

The switch cases were unsigned, but the passed value was an int32.

Certain strings could cause infinite loops otherwise.
(See previous commit, I was having CVS problems.)

maintenance and any system daily event to *not* execute in the event thread
(i.e. very soon after midnight), but instead require a BBS user logon/off to
initiate these daily tasks, or (as I use it) another instance of sbbs which
is better suited to these daily tasks.

default answer for these prompts.

mail base can't be opened (e.g. it's locked for maintenance).

with Chrome (the browser). Chrome will attempt to "CWD" to a filename and if
that filename was an alias from the ftpalias.cfg, we would return a
successful (213) response - erroneously. The code did appear to check for
this condition by calling ftpalias() with a NULL second (filename)
parameter, but that didn't actually work. The 'alias+1' check for a slash
appears to have (always?) been clearly wrong as a prefixed slash is already
skipped (in the requested path) before calling ftpalias().

message text (when relevant and available) - this helps when re-wrapping the
message text (e.g. for quoting) and not always guessing "80 columns".

now have their output translated to PETSCII equivalents for PETSCII terminals
(but input is not yet translated).
.seq files are now sent untranslated via printfile() and putmsg() to PETSCII
terminals (using the new P_PETSCII putmsg mode flag).
.seq files (and P_PETSCII mode text printed via putmsg) is now converted
(poorly) from PETSCII to CP437 - this is still a work-in-progress.
Remove the remants of WIP and HTMLterm support from putmsg() and printfile().

File not found.
d:\sbbs\text\menu/msgtabs.asc

can we get a slight change in the sbbsecho code or maybe in echocfg so that
when a link is set to passive, areafix notices are NOT sent to them even if
"send notices" is specifically set to yes?

Send CR/NUL for <Enter> rather than CR/LF. Although the Telnet spec (RFC854)
requires that either combination be accepted as a single "new line" character,
some Telnet servers treat CR and LF as separate input characters and do weird
things (e.g. treat the LF as a second <Enter> key or <^J> or invalid input).
If we ever come across a Telnet server that does something weird with CR/NUL
(and works better receiving CRLF) then perhaps we'll need a configuration
option. Hopefully not. Of course, in binary mode, none of this applies.

don't ask Guests (during logon) either.
Removed some more WIP and HTMLterm support.
Remove a couple unnecessary if (text[somethingQ][0]) checks.

menu() if it does (exist) and doing something else if it doesn't.

(a bbs "call") shouldn't be going in those log files (data/logs/<date>.log)
anyway.
Also, truncate the node.log if there was no successful login. We don't
want all those failed login attempts and filtered IPs to clog up these
log files. All those same messages go to (the normal) syslog() output anyway.

to the log message becomes redundant.

Also, using mnemonics() for better dumb terminal support.

display/menu file.
Also, the WORDWRAP @-code may now appear anywhere in the file and multiple
times in the file (to mark multiple word-wrapped blocks of text).

it'll use the bbs.menu() function to display it - with automatic file
type/extension selection based on current terminal. Since the bbs.menu()
function looks for files in text/menu, you'll need to change the path
e.g. from "../text/system.msg" to just "../system.*" to display text/system.*

file (text/bullseye.*), so you can use terminal-custom screen files.
Thanks, Nelgin!

Removed the hokey animation (not well supported in all terminals).
Using new @-codes WORDWRAP, CONDMENU, COLS, ROWS, and TERM.
If the display/menu file text/banner.* exists, it'll display that as well
(before the text) - using the new CONDMENU @-code.

only if it exists (on disk) and displays no error message if the file does not
exist. Nearly identical to the existing MENU @-Code, but without the need to
insure the file actually exists first.

means no error message will be displayed/logged if the referenced file does
not exist.

display the auto-term values.
Removed WIP and HTML term support.
Removed Color/Mono from the PETSCII mode info.
Fix what appears to be a couple of been-there-forever bugs in regards to
displaying/toggling the 'default to quiet mode' setting.

terminals - thanks Nelgin!

has used this feature in 20+ years.

don't use the stored user terminal type. This allows the same user (e.g.
the sysop) to be logged onto multiple nodes concurrently with different
terminal types without effecting the other node/session.
Guest sessions were already immune to this problem.

RIP/ANSI/PETSCII, if the files exist.

Newly supported files: text/menu/*.msg (higher priority than .asc when the
terminal supports IBM extened ASCII, aka CP437). These are the same format
as .asc files (and supported more readily by PabloDraw).
Newly supported files: text/menu/*.seq - native PETSCII files for PETSCII
terminals only. Support in the underlying putmsg() function is still
pending.
Also, the text/*.msg files now supports alternative file formats for
RIP/ANSI/PETSCII, if the files exist.
WIP menu support removal.
The new menu/display file selection priority will be detailed on
wiki.synchro.net, but rest assured, it's backwards compatible with
the previous/old priority with the exception of the removal of WIP support
and HTML support.