normal messages along with voting data (polls, ballots, etc.) would always be
imported in this order: msgs, polls, ballots/votes, and then poll-closures.
This could result in a confusing order of messages in the local msg base where
there were messages in reply to a poll before the poll appears and other
oddities. Anyway, this is now resolved by placing a msg "header block" for each
vote-data item in the MESSAGES.DAT file. Since there is no body/text blocks,
it should be ignored under normal circumstances, but these header blocks are
only created if VOTING.DAT is enabled anyway.
And now, the VOTING.DAT contains an extra line (empty .ini section) with the
HEADERS.DAT offset associated with the chronology of the item. The format
is still backwards compatible with the earlier builds that included VOTING.DAT
support.

Also, fixed the vote/poll/closure Message-IDs containing a msg number of 0
(while not technically a problem, it wasn't the intention) with the use of the
new function: get_new_msg_number().

to be able to delete messages that have no hfields, for example, with sub-op
'D' command.
Now support polls with comments (displayed before the poll answers).
Poll results/statistics are only displayed to sub-ops and users who have voted
already. This may be optoinal behavior determined by the pollster in the future.
Sub-ops can now add comments to any post using the 'A' command from the
[O]perator menu - use with caution.

- Users can be restricted from voting with the 'V' restriction
- Sub-boards can be disalbled for voting in SCFG
- VOTING.DAT can be include/excluded from QWK packets via user cfg
  (when a VOTING.DAT is received in a REP, the user cfg flag is auto-set)
- Adds several new text.dat lines (if not present in yours, uses the default)

What's not yet implemented:
- Notification of votes on your posted messages
- Method to view/audit all votes
- Polling
- Any special handling to auto-exclude votes from msg-related JavaScripts

scanposts(), and listsub(). These functions are exposed in the JS 'bbs' object
as scan_subs(), scan_msgs(), and list_msgs().
Wherease previously, all of "your messages" (messages addressed to you)
would be found/displayed if the user answered (Y)es to the "Subjects Only?"
prompt, and only un-read message (to you) would be displayed if they answered
(N)o to the "Subjects Only?", providing long-standing confusion about the
different behavior, now the user is prompted whether to display un-read
messages only (in scansubs/scanallsubs), and in the case of the logon
question to "Search all subs for un-read messages to you?", only un-read
messages are listed/displayed, regardless of how the user answers the
"Subjects Only?" question.
SCAN_UNREAD is only applicable when combined with SCAN_TOYOU.

Added new commands to the msg reading prompt: 'N' (list new messages), 'U'
list un-read messages to-you.

2 new text.dat entries: DisplayUnreadMessagesOnlyQ and NoMessagesFound

I've likely broken something though, so if you see weird behaviour with
extended ASCII, let me know please.

unmoderated message in a sub.

longer (use lprintf(LOG_ERR,...) instead, which does).
Added sbbs_t::hacklog() for convenience.

A lot of strcpy->SAFECOPY and sprintf->safe_snprintf/SAFEPRINTF conversions
and other general code cleanup too.

getlasgmsg() needs a uin32_t* as the second arg.
loadmail() needs an int32_t* as the second argument.
loadposts() needs an int32_t as the first argument.

ptr value, sets last_read msg num along with ptr to actual last message num.

were no errors) - this forces the updated scan pointers to be saved.

loadmail() change which had a trickle-up effect to the higher level functions
that use loadmail().

QWK packing events to spew unintended output strings into the event log.

it would always update the message at index offset 0, thus not correctly
marking the sent message as deleted and sending dupes later. This also led
to mild mail database corruption (duplicate message numbers and index
header offsets).

deleted after QWK-packing.

mail_t and post_t are now defined as SMBLIB's idxrec_t.
This fixes the problem of msgtoqwk() not having access to the correct idx data.

(to maintain threading across networks).

Don't call closedir() if opendir() returns NULL (fix FreeBSD segfault?).

single array of structures.

Each function that requires a temp string variable, now has its own "tmp" local variable.

Pkzip/unzip required *.* to add/extract all files in a directory. <sigh>