on that msg offset will fail (since include_votes is false, the default).

Version 1.17 beta 4: Bug fix - When going to the next area after reading the last message, it was showing empty messages.  This seems to be fixed now.

'from' fields were > 127 chars in length. Now using smb_init_idx() since it
does the "right thing".

The duplicates aren't removed from the header file, just not indexed.

header records (index with the same message number points to a different
message header).

Incremented smblib version 2.60 (to indicate all the recent changes).

If the msg->offset is 0, we must call smb_getmsgidx() to find its offset,
otherwise smb_putmsg() which calls smb_putmsgidx() will overwrite the index
of the first message.

- Include Kludge Lines     (Yes)
- Include VOTING.DAT File   (Yes)
- Include HEADERS.DAT File   (Yes)
- Extended (QWKE) Packets    (No)
- Exported Ctrl-A Codes    (Strip)

SBBS/QWKnet nodes now have more control over the REP packet files created
by their systems. If the "uplink" (hub) is complaining about receiving
unsupported files (e.g. VOTING.DAT) or kluge lines (e.g. @TZ), just turn them
off.

Also, Ctrl-A codes may now be retained in QWKnetmail. And the @REPLYTO kludge
line enabled for the first time (!).

  poll if you answer No to the "Close Poll" question.
- Display the "votes" msg header value for the sysop 'H'eader command.

header of the original message (after the first reply), but wasn't setting the
same flag in the index.
This results in "Attributes mismatch" errors from chksmb.

already have a reply_id header field, causing REPLYID header fiels to be
set to garbage characters.

Version 1.12: Updated the message area chooser to work better with Synchronet 3.17.  Null message headers seem to be more common with Synchronet 3.17 due to the message voting feature that was introduced in that version.

- the in-order QWK voting data importing wasn't working because the
  ini sections returned from iniGetSectionList do not contain the square
  brackets. So search for just the hex-offset (into MESSAGES.DAT) rather
  than the offset in square brackets.
- Stop zeroing the vote message upon import (oops), causing SMBLIB -105
  errors upon adding the votes.

Ubuntu 12.04.2 LTS (gcc v4.6.3)

(routed netmail, time zone kludges, etc).

Also allow multi-answer polls to be added using the '-votes=<value>' argument.

"name" argument to a char* correctly.

by Bill McGarrity: new bug.

New MsgBase header propeties:
- total_votes (total number of votes this msg or poll has received)
- tally[], an array of 16 numbers indicating the total votes for each poll answer
  in the case of a normal message, tally[0] is the same as upvotes and tally[1]
  is the same as downvotes.
This should complete what echicken needs to display polls and voting results
in his web UI.

smb_voted_already(), e.g. to @-codes in a custom msg header.
New @-codes (e.g. for custom message headers):
@MSG_VOTED@
@MSG_UPVOTED@
@MSG_DOWNVOTED@
These all 3 act the same way: they display the PollAnswerChecked (checkmark)
if the user voted on the currently displayed message/poll, if the user up-voted
or if the user-downvoted. If the user did not vote, nothing is displayed.

smb_voted_already(), e.g. to @-codes in a custom msg header.

(reading the msg) submitted an up-vote or down-vote on the current msg.

get_all_msg_headers).
Added new method: get_user_votes(msg number, user name or alias)
The user name or alias must match the posting configuration on the local
system (i.e. if set for real names, pass the user's real name instead of alias).
This function returns 0 for no votes on the reference message, 1 for an
up-vote, 2 for a down-vote or in the case of a poll-response, a bit-field of
votes.

On polls, this is the maximum number of votes per ballot in response to this
poll (0 is the same as 1).
On ballots, this is the bit-field of votes submitted by the user (e.g. bit 0
set is a vote for answer 1, bit 1 for answer 2, etc.).
For normal messages, this field has no current use.

temp-ban (was logging the total number of login attempts, including dupes).

"Always Prompt for Password" setting is set to "No".
This change enables the auto-hack-log, throttling, filtering, and banning
logic for these types of failed login attempts.

Version 1.17 beta 2: Working on filtering out messages that are deleted, unverified, poll/vote messages, etc. so they don't show up in the message list or reader interfaces.