if it didn't already exist.

Created struct fidoaddr (5D address), though it's only used (so far)
in pktdump.c - doesn't really need to be packed.

If you're not using BinkIT (you're using some other FidoNet mailer), you can
safely ignore all the settings/options.
A lot of the online help for the new settings/menus needs to be written
still and the wiki now needs a lot of update to reflect the changes.
The "title" of this program was changed, again, from "SBBSecho Config" to
"[Synchronet] FidoNet Config" since it configures more than just SBBSecho
now.

(e.g. "Zones=1,2,3,4,5,6").

if the thread returns before js_initcx() is called.

discard).
Also, trim trailing white-spaces.

sdl_con.c: In function ‘sdl_mouse_thread’:
sdl_con.c:1424:1: warning: no return statement in function returning non-void

channel we ignore/close, we would get a separate warning for each chunk of
data on that channel until we read past the close.  Instead, if we're closing
a channel, we note the channel ID, and simply discard the information
immediately on the most recently closed channel.

A remote could still cause a bunch of log output by multiplexing two or more
writes to invalid channels, but nobody seems to do that, so this should be
good for now.

syncprog and the commit log again).

of the #if !NO_SOCKET_SUPPORT block. Fixes Windows build of addfiles
and other utils.

the output_thread which may occur after an SSH-related error in the input
thread, e.g.:
Sun Mar 25 2018 01:45 pm bbs.synchro.net
Node 6 SSH ERROR 'Bad argument, parameter 2' (-2) setting channel

Sun Mar 25 2018 01:45 pm bbs.synchro.net
Node 6 SSH ERROR 'Bad argument, parameter 2' (-2) setting channel

Sun Mar 25 2018 01:45 pm bbs.synchro.net
Node 6 SSH ERROR 'Bad argument, parameter 2' (-2) setting channel

Sun Mar 25 2018 01:45 pm bbs.synchro.net
Node 6 SSH ERROR 'Bad argument, parameter 2' (-2) setting channel

Sun Mar 25 2018 01:45 pm bbs.synchro.net
Node 6 SSH ERROR 'Bad argument, parameter 2' (-2) setting channel

Sun Mar 25 2018 01:45 pm bbs.synchro.net
Node 6 SSH ERROR 'Bad argument, parameter 2' (-2) setting channel

... by introducing a new sbbs_t member variable: terminate_output_thread
which is only set to true when the input_thread is terminating.

If there is any possibility that the input_thread could startup and get
an SSH error before the output_thread even starts, then we will want to
move the terminate_output_thread=false initialization to the sbbs_t
constructor.

a temp variable.  Mostly impacting the setting of video flags.

Fix-up the user/####.subs ini style (only one blank line between sections).
Also, don't re-write the .subs file if nothing has changed.

(data/user/*.subs - in familar .ini syntax)
indexed by the sub-board internal rather than the old flat binary file using
the troublesome "pointer index" (ptridx) as an offset. The old files
(data/user/ptrs/*.ixb) will still be read in when the new file doesn't exist,
for upgrading users automatically to the new method of pointer storage.
This should resolve long-standing issues around users' new-scan pointers and
configurations getting corrupted when the sysop inserts/remove sub-boards.
However, if you change a sub-board's internal code, that invalidates the users'
pointers and scan configurations - so that may need to be addrsesed via SCFG.
The subs' ptridx values are still be used for storing QWKnet hub pointers, for
now, but that too will soon be addressed with a new file format for those ptrs
too.

increase post-count width supported from 4 to 5 digits (beautifully).

networking technology for 20 years. :-(

or not).

severity) whenever there is an SSH session establishment failure, because
some of the SSH failure errors are DEBUG level severity and won't be visible
with "Normal" (informational) log output filtering. This resolves the issue
of seing "SSH connection accepted from <ip-address> port <port>" messages
with no follow-up messages as to what happened to that connection.

like a str_list_t declared in line (but the char* is fine?!).

Remember the last forced timed event setting.

- lower log level (raise severity) of "Waiting for ..." msgs from Debug to Info
- log a message when done waiting (for clients, threads, etc.)
- only one #### log line per termination event

(default is ctrl/status.sock).

Windows, every time. For example, this resulted in the same BinkP CRAM-MD5
challenge being sent for every mailer session. Fixed by calling sbbs_srand
in the service's thread, not (just once) in the accept thread.

reach the configured "max size", newly added log lines would not use the
configured color/font for the msg's log-level (they'd all use the default
color/font).

(interval) and display them on a single line with an " [x#]" suffix
which identifies the number of times the message was repeated during that
interval.
Also created a common log_msg() function and eliminated a lot of copy/pasta
in the various *_log_msg() functions.

collate more (repeated/duplicate) log messages into a single line of the
visible log.