key was missing from the sbbs.ini file, it would default to 0 seconds which
could cause continuous high CPU utilization after server recycling.

(optionally).
Sub-board operators can now see all poll-results (always) for locally-posted
polls (same as pollster).

(no functional change).

- Closures (polls can be closed for new voting by the pollster)
- Results can have configurable visibility:
  a. Only to voters (and the pollster) - the default
  b. Everyone
  c. Everyone once the poll has closed
  d. Only the pollster

Changes to smb_getmsgtxt():
Main change: poll questions can now be quoted when replying to a posted poll
(the results cannot be quoted).
Also: there's now automatically a blank line inserted between comment header
fields and poll answers or the msg body text.
Also: upon any malloc failure, the function now returns NULL.
New functions: smb_msg_is_from() and smb_addpollclosure().

been read. This way, the configured bsy_timeout value is used. Before, the
value of 0 was used which results in an infinite timeout (max age) for the
mutex, requiring a manual deletion of the file (no automatic recover) if
SBBSecho happened to crash. Now, it'll use the default bsy_timeout value
of 12 hours or the configured value in sbbsecho.ini.

1. If QWKE was enabled for the QWKnet account on the Hub, a user could spoof
   their name with a "From:" QWKE kludge line in the message body. Fixed by
   not processing QWKE "From:" kludge lines at all, ever.
2. If an @VIA kludge line was in the message body, it could over-ride the
   correct value from the HEADERS.DAT (oops). Really, the SENDERNET* lines
   in the HEADERS.DAT were always being overriden by either the @VIA kludge
   line (if present) or just the auto-genereated SENDERNET info (from the
   QWK-ID of the QWKnet account or hub. Normally, in a single hop QWKnet
   message, there will be no @VIA line, so spoofing is still possible in that
   case.

Use the proper method to auto-set the QWK_EXT (QWKE) flag for the user when
TODOOR.EXT is discovered in a REP packet.

record (e.g. the user number is invalid), the user number should be 0 after
returning. This would cause, for example, sbbs_t::login() to accept a login
string with an invalid usernumber (e.g. "12345") and do some strange things.
The same side-effect was missing in the (new) fgetuserdat().

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.

Fixed printf() arguments.

it just calls the (newer) functions readuserdat() and parseuserdat() in a easy
replacement for getuserdat() for places where all users are read in a loop
(the file is only opened one time, dramatically reducing the amount of time).
Added an argument to openuserdat() so it can be used in more situations
(i.e. where the file needs to be opened for modify/create acces).

module. This is a reversal of the revision 1.102 commit (Jan-2-2016), but only
for Baja (JS is left with the new behavior). As the commit message said
"We'll see", and what we saw was that the yesnobar.bin and noyesbar.bin
long-standing Baja modules no longer returned "No" when the user hit Ctrl-C.
So at least for now, we have different behavior with regards to the console
abort (ctrl-C) flag between JS and Baja. :-/

up in 'top' output and provide some confusion.

clients:
1. The host_name is not known at the time loginBanned() is called, so that was
    a bogus value (left over from the previous connection) being used in the
    ipfilter_exempt.cfg file check.
2. Sometimes, getnameinfo() would fail, but still return 0, so previous
    host_name value would be erroneously stored as the current client hostname.

* uses new text.dat strings:
- PollVoteNotice
- PollAnswerNumber
- PollAnswerFmt
- PollAnswerChecked

The actual answer of a poll is still crude (uses the old crufty uselect scheme)
and doesn't support multiple-choice polls. This will be addressed.

add_poll() method now sets the when_written/imported time stamps and zones
as needed and configured.

(and configured).

it displays a string of text and fills the background color up to the
specified percentage fo the string length. I will be using it for displaying
poll results, but it could possibly be used for progress displays and such.
The colors used are configured via the "backfill" and "unfill" attributes in
ctrl/attr.cfg.

be used in displaying poll results. Set the default backfill to white on
magenta.

be used in displaying poll results.

There (will be) the possibilty to cast mutliple votes in a single vote-msg
(ballot), when multi-choice polls are introduced later. There were just too
many things call vote/votes and it was getting confusing in my own head. So the
msg type for messages that contain votes is now "ballot".

they don't fill your error.log file up.

field can have that line automatically stripped from the displayed header:
- The \r\n's were moved from the end of the MsgSubj and MsgAttr strings
to the beginning of the MsgAttr and MsgTo strings.
Also, fixed the number in the VoteMsgUpDownOrQuit comment.
Removed "I'm" from the "Sorry.." vote related strings.

console input on Windows (e.g. the prompt() method no longer worked).
This change was related to his JSDoor work, so that might be broken now.

SMBLIB dependency to projects (e.g. filelist) that don't already have it.

invalid conversion from æconst char*Æ to æchar*Æ

- wasn't opening sub-board correctly (now using new smb_open_sub)
- for single-hope QWK packets, wasn't setting the sender netaddr (QWK-ID)

"the right way", this will be used to replace a lot of copy/pasta over time.

MsgDownVoteNotice.
Also moved the R_Voting string, so the last few voting related strings in the
text.dat have been re-arranged (sorry about the thrash) - if you don't have
these new 8 lines, the default strings are used and you're fine.
When listing messages from the "Reading" prompt, the vote status and Replied
attribute flag are now indicated: 'V' = voted up (more than down), 'v' = voted
down (more than up), and 'R' = replied-to. Unread/new messages still show a '*'
in the A (for attributes) column.
Voting via JS still does not automatically send a notice to the poster, that
still needs to be worked out.

(new header properties: upvotes and downvotes), regardless of the
"include_votes" argument value (default: false).
get_all_msg_headers() reads the entire index already, so there's really no
performance penalty unless there are actual votes (and even then, very low).
The MsgBase.get_msg_header() function will *not* return these vote totals since
that would incur a pretty substatial performance hit on that function.

(like save_msg), except you only need a few properties, in order of importarnce:
attr: you need to have this set to MSG_UPVOTE, MSG_DOWNVOTE, or MSG_VOTE
thread_back or reply_id: either of these must be set to indicate msg to vote on
from: name of voter
from_net_type and from_net_addr: if applicable