is required.

Treat a password of '-' the same as an undefined password in binkit.js.

To fully comply with the binkp/1.1 (FSP-1024) spec, we need to rescan the
outbound after sending an M_EOB... this shouldn't actually be necessary
though since we're holding the .bsy lock the whole time, and nothing else
is allowed to add stuff (per FTS-5005).  This is mostly for FREQs, so once
the req handler is in there, I'll likely ignore this requirement.

Still TODO before callout support is "complete":
1) Enhance handling of received file names
   a) On pkt or bundle files, place in sbbsecho inbound directory. with
      a known unique name... don't rely on the remote to make one up.
   b) For req files, handle the file request directly.
   c) All other files, place somewhere else for processing.
2) Perform actions when files are received... touch semaphores, parse TIC, etc.
3) Update flo files after a partial run... mark successful transfers as skip.
4) Put real data into the .try file.

as "all the information" is sent... per FTS-5005: "The mailer should not wait
for the end of the session when deleting the flow file."

the send as name property.
Add another "sendas" parameter to the addFile() method.

This allows renaming on the fly (which is required for packets).

will ALWAYS have a zone extension"

that would trigger a callout (since it's never handled).

an issue in 2038).

FIDO.Addr parsed from the flo file path... path should have the outbound
directory name in it.

base outbound for a specified node.

Most if it is still TODO.

will be available regardless of the scope of the callback.

caller can addFiles() after the address list is received, hopefully knowing
if it's a secure session or not.

to the constructor, use "UnknownScript/0.0".

Thanks!

strongly enforced address type.

any moment without notice" means that it won't sent an OPT ND.  Just in case,
handle a -1 offset as though NR mode is enabled when version is 1.1.

this session, SKIP files that already exist, and ACCEPT all others.

No longer try to append extra data packets to the end of the file to allow
files to grow in transit... the protocol is really not well suited to this
anyway.  Instead, truncate to the advertised length.

If the want_callback changes the file name, still ACK the correct file.

Escape filenames more consistantly.

filter unwanted properties" warnings by default.  This is more for when
you're worried that your object may be exitended... a rare situation in
Synchronet JavaScript.