start at the first message, don't display message automatically.

default (in the Terminal server), use Raw I/O mode (Ctrl-Z) to toggle this
behavior off/on (same as word-wrap toggle).

writemsg() now handles the anonymous name in the drop files (using WM_ANON
for the first time?).
A little mixed-case NETMAIL.MSG paranoia (for case-sensitive file systems).
More use of SAFEPRINTF().
More use of removecase().
More attribute flags represented (with a single character) in the 'A' column
of mail and sub-board message listings.

files and editors have the correct sender name in all situations (not just
when posting on "real name only" sub-boards).
"ANONYMOUS" postings work too, but mainly Internet & FidoNet Netmail were fixed.
Use removecase() for NETMAIL.MSG (in case there's a lowercase version).
Use subj in place of title and to in place of dest in argument names.
Some constification of argument types.

@-codes can now be center-justified by using the *new* -C suffix (like -L/R).
Centered expanded values are not truncated to fit the @-code length however
(that may change).
SMB_AREAS and SMB_AREA_DESC @-codes now display "Email" and "Personal Email"
rather than a blank/empty string when the current message base is the mail base.

Display local time and time zone in system info list.
Display local time zone in Ctrl-T output.

time zone.

Daylight Savings Time (sic) into a single configuration setting now under the
System menu (System->Local Time Zone), with updated help screens.

FidoNet NetMail can now be gated to an SMTP client (as before), but replies are
now successfully gated back to FTN NetMail. This uses a new more RFC-compliant
To/From address header field format, so older messages (previously gated to
an SMTP client) cannot be successfully replied-to. Tested with Microsoft
"Windows Live Mail 2012" (previously known as Outlook Express).
Test reports/results with other SMTP mail clients would be welcome.

Requires SBBSecho v2.30 or later. File attachments are not yet supported.

It turns out there was actually a reason to use the macro (fewer arguments).
Oops.

apparently SCFG wasn't creating this directory and SBBS only created it if you
sent FTN netmail from the terminal server.

in SCFG.

to confuse sysops (a holdover from the SBBSFIDO days) and would create an
AREAS.BBS file not compatible with SBBSecho. The "AREAS.BBS (SBBSecho)"
export group menu option remains and is the one that sysops should normally use
when wanting to create an SBBSecho-compatible AREAS.BBS file.

hasn't been used in a very, very long time (a hold-over from the SBBSFIDO days)
and only serves to confuse sysops.

FidoNet netmail in the normal mail base (data/mail.*) will now be exported to
FTS-1 (*.msg) files automatically. One way in which the FTN netmail can end up
in the mail base is by using the (legacy/runemaster) Web UI. You should also
get the updated savemsg.ssjs if you're going to use this feature.
To disable this feature use the (new) '-c' option.
Normally, the exported msgs will be deleted unless the '-d' option is used in
which case the messages are just marked as "sent", so they won't be exported
again. This feature does not yet support file attachments.

This will likely lead to the SMTP server supporting the sending of FTN netmail.
Apparently we have to find a better way to encode FTN addresses within
RFC2822-compliant header fields first.

If you're using a BSO/FLO-style mailer, this feature works with the '-f' option
so the full path of an outbound netmail may be SMB->*.MSG->PKT. Direct
export to PKT is certainly possible in the future.

Incremented SBBSecho version to 2.30.

compatibility macro - no functional change.

for the CGI REQUEST_URI variable.

Jacques Mattheij to Stephen Hurd. I'm assuming the derived code is now jointly
copyright by Stephen and myself, so maybe some notices needed to be updated.
<shrug>

Jacques Mattheij to Stephen Hurd. I'm assuming the derived code is now jointly
copyright by Stephen and myself, so maybe some notices needed to be updated.
<shrug>

html_decode() function.

file descriptor (and seems to work on Win32).

broken on *nix now.

not the file object itself.

scope get set properly.

those OSs which require it to be correct (ie: FreeBSD).

These bits may need protection to ensure they are the CORRECT objects.