name(s) are zero-length strings.

attribute for netmail (both *.msg and in the mail base). This option should
*not* be used when the DeleteNetmail option is enabled (set to 'Yes').
A warning will be logged in this configuration as dupe netmail msgs may be
sent in that case.

by Bill McGarrity.

number is particularly interesting to me given the error's he reported seeing.

sbbsecho.h:186:7: warning: array æpktTypeStringListÆ assumed to have one element
Warning: size of symbol `pktTypeStringList' changed from 8 in .../rechocfg.o

For packet creation, the only difference (from Type-2+) is with packets created
from point nodes: the origNet field won't be set to 0xffff (as is the case with
FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
net (ala Squish) when configured for Type-2+ packet generation.
When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
reported as "2e" for valid "2+" packets. This is normal and expected when the
originating node is not a point and the auxNet field is 0.
The second set of orig/dest zone fields in a type 2e/2+ pkt header will
now be used when importing if the old/QM orig/dest zone fields are 0.
Also, the originating point field may now be imported even if the auxNet field
is not used (origNet != 0xffff).

New umask sbbsecho.ini configuration option (global), maybe used to over-ride
the default *nix file creation mode mask (077), similar to sbbs.ini.

Use more formal terminology (e.g. "Type-2", not "type 2.0").

Version 0.17 beta: Updated one of the error messages, and made a screen drawing optimization when viewing poll results

- %RESCAN returns a different failure result if the requested echo is a
pass-through area (cannot be rescanned)
- %UNLINKED will return only the unlinked echoes even when an "additional
echolist" is utliized and the linked areas are all pass-through (for Bill).

If what appears to be a QWKnet addressed was passed, but the QWK-ID portion was
exactly 9 characters, a 1-byte stack corruption would occur as the 10-char
local variable (node) could be written with 11 chars (9-char QWK-ID, colon,
null). The reported issue happend when attempting to send netmail to
"hemo@ujointbbs" which is neither a valid Internet email address or a valid
QWKnet address.

Version 0.16 beta: Added a main menu option to display poll stats - Lists the polls by highest number of votes (highest first), and for each one, lists the answer(s) with the highest number of votes (highest first).

Version 1.17 beta 33: Improved to better handle message text that starts with "By <name> to <name> on <date>" - Some of those messages have ANSI codes (such as cursor movement codes, etc.) in that part of the text, which can mess up the display of the message when using the scrolling interface.

findstr() and findstr_in_list().
This means that rather than listing an IP address range using the traditional
wildcard characters (e.g. "192.168.1.*"), you could specify a subnet range
using CIDR notation (e.g. "192.168.1.0/24").
The '!' prefix is supported for CIDR match lines (for negated match results),
but no other wildcard/match characters are (e.g. '^', '~', or '*').
You can mix and match traditional match lines and CIDR match lines in the same
filter file.
IPv6 CIDR notation is not yet supported.

If a key in the [feeds] section of modopts.ini begins with '_crosspost',
the value is assumed to be: 'url,sub1,sub2...', for example:

[feeds]
_crosspost1 = http://my-feed/rss.xml,dove-gen,syncprog,general

Avoid duplicate key names by tacking a number onto the end:
_crosspost1, _crosspost2

The old style 'sub = http://my-feed/rss.xml' pairs are still supported.

Version 1.17 beta 32: Fix for some (new) instances where it wasn't checking the sub-board code to see if it was "mail" before checking the can_read property

Added a revision history note for version 1.17 (even though it's still in 'beta').  Also, updated the readme to include some notes on voting, and added a list of lines from text.dat used by the reader.

Version 1.17 beta 31: Added some checks to ensure the user won't be able to read a sub-board if they don't have permission to (if the sub-board's can_read property is false).

Added a section with notes for sysops, which explains where to delete polls from within SlyVote and which text lines from text.dat are used in SlyVote.

Version 0.15 beta: If there is more than one topic area (sub-board) configured, a menu option will be added to change the topic area.  Also, now it actually loads text.js so that references to text line definition variables will work properly.  Also, it now checks whether the user can post & read messages in the sub-board before allowing the user to vote & view results.

Version 1.17 beta 30: Made an update that should (hopefully) fix a message number error when a new user does a newscan for the first time (I thought I had fixed that some time ago, but it looks like I didn't fix it for all cases).

When getting the message text, now checks if it's reading personal email before checking if it's a moderated message area, avoiding an 'undefined' error.  This would more than likely not happen with SlyVote though..

Bug fix: When getting the message text, now checks if it's reading personal email before checking if it's a moderated message area, avoiding an 'undefined' error.

converted from unicode, then the path was being free()ed.

in your USERPROFILE and (in my case at least) root of C:
When the 'type' parameter to get_syncterm_filename() was is 2
(SYNCTERM_DEFAULT_TRANSFER_PATH), the fn (filename) argument would
remain uninitialized (random/garbage) at the point that it creates the
directory stored in 'fn' if it doesn't exist. Often garbage would be an invalid
filename (or just 0) which would cause Windows to fail the request to create
the directory. But other times, the garbage would still be a valid directory
name (usually just one or two characters).

The code after this assumes 'fn' is initialized and (like I just pointed out),
in some cases, it's not. So there might be another fix here needed.

Version 0.13 beta: Added support for validating messages in moderated areas. It seems it's using the wrong message number though, which will need to be fixed..

Started working on a way to validate a message in a sub-board where the message requires moderation.  Doesn't seem to be successfully saving the updated message header though.

Improved the look of the sub-board chooser menu when SlyVote starts by displaying the SlyVote stylized text and the vertical bars around the menu.  Also, added a help screen for the result viewer mode.

Bug fix: Unknown variable referenced when reading poll results and the user tries to vote on one when they've already voted on it.

Now displays the topic area (message sub-board) on the main screen.  Also, updated the "vote on all topics" feature to display the topic number and total number of topics.

When voting on a topic, made the subject/question centered and in bright green to set it apart.  Also, added an ESC=Quit text in the lower left when voting on a topic to let the user know they can quit out of voting on a topic.