messages (frame), introduced in rev 1.231.

passed (as an array), the message's data blocks would be allocated with a
refcount of 1, as though only one message header referenced the data. This
is really only an issue with bulkmail/multiple-recipient email and when the
first message was deleted, the remaining (headers) would point to free
data blocks which could and eventually would be overwritten by another
message's data (body text). chksmb would only catch the problem when the
refcount reached 0 but there was still one or more message headers pointing
at the data.

and smb_incmsg_dfields(), now lock and unlock the SMB header.
This shouldprevent some mail base corruption as well as this error:
-203 (smb_incmsgdat 13 'Permission denied' reading allocation record at offset
795568) incrementing data allocation units

If the 'chat [node]' command is issued but the user on that node is not waiting in the pager script, send them a telegram (request_page_format).  Useful if the sysop arrives a bit late or just wants to invite someone to chat.

semaphore_scan_interval is really an ircbot setting; moved it to the appropriate section, got rid of [scanner] section. Scanner does not need parameters.

Use a Frame for all output.  Call bbs.node_sync in loop.  Prevent node messages from being delivered.

when there are no key presses.

If the old syntax was used (with a list of integers), it would cause a segfault after
displaying a corrupted/small dialog due to lots of problems parsing the argument list.

Call uifc.bail() to clean up the screen before exiting.

Server Config dialog.

Also fixed the exit menu for long screen (not saving/restoring the bg).

paged by a user on the terminal server.

Use alert(), since we have it.

(using -i). These aren't quite as good as the IDs we can generate when we
have access to the BBS configuration (scfg_t), but it's decently unique and
identifiable.

It requires a recent build of sbbs v3.17 with the new file_cdate() global
method (JS). It doesn't do the right thing for non-GMT date/times currently.
And it doesn't work if you run maintenance/pack with smbutil since it
writes to new files and removes the old and renames which resets the file's
creation date/time stamp. So... either we'll be reading the <code>.ini file
or changing smbutil behavior.

<code>.ini and add a single key to the global/root section:
Created = 0x<time_t> which can be used (e.g. by nntpservice.js) to determine
the date/time the message base was created.
This makes the <code>.ini files an official part of the SMB format. Wheee.

  union xp_sockaddr addr = {0};

mode, a freeing of header or data storage at the end of the file will now
result in the file (the allocation file *and* the data/hdr file) being
truncated - saving potentially many megabytes of disk space for
non-maintained msg bases (e.g. the mail base). Previously, self-packing
and fast-alloc msg-bases would never shrink without running smbutil m,
but that's now no longer true.

Something similar could be done for hyper-alloc msgbases, but I'm not sure
that's really needed since the email base can never be hyper-allocated and
this change was really for the email msgbase where allocation files are a
must due to the multiple-recipients/headers per msg data feature.

files don't correlate correctly with the data (sdt) or hdr (shd) files.
Report errors if either the data or hdr file are not a logical length
(e.g. not evenly divisble by the block length).
Report the oldest message (in days) in the msgbase, from import date/time.

ToDo: report messages posted/imported (or written) in the future
ToDo: keep the stats in an array for sensible clearing and reporting