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.

node_dir.

portably.

Also, we're really interested in termios stuff, so we don't actually want
to call setvbuf anyway.

controlling the vbuf of a stream.

var s= new Socket(true, descriptor);

This creates a new socket object from a socket descriptor.

Once again, actually using these is NOT SAFE, you need to pay very close
attention to the C source code to know what functions you can use in multiple
threads.

The log function gets overwritten, so it should remain somewhat safe, but
everything else is a potential bug in your background script.

can be used from background threads.

If the parent thread has a bbs and/or console object, create the object in
the children as well.

Accessing the console object from more than one thread is very much a bad thing.
Accessing the BBS object from more than one thread may be bad as well...

- the default protocol (line 27) was hard-coded to 'Y' rather than whatever the user had
selected.
- the "BBS default color (line 41) wsa hard-coded to 14 - now uses the
External Programs (default attribute) value from ctrl/attr.cfg (default: 15).

It's unlikely these changes will actually affect the operation of any doors,
but might as well make the content a bit more dynamic/accurate.

Use lazy resolution for file_area, msg_area, and xtrn_area objects to prevent
having to pay the price during startup if the objects are never accessed.

The delay now occurs the first time a member of the specified objects is
accessed.

These objects also now have associated class names... FileArea, MsgArea, and
XtrnArea respectively.