for each domain to avoid needing to sort through other properties.

sort addresses by "distance from destination".  If this doesn't work, we'll
need a source address key in the ini file.

Strip trailing slashes from the SBBSEcho outbound directory.

each section has a comma-separated list of zones in the "Zones=" key and a
"DNSSuffix=" which indicates the DNS domain for pW.fX.nY.zZ.example.com
lookups.

If there is only one domain that covers a zone, the domain will be set to
that one.  If there is more than one, it will not be auto-filled.

inbound is not defined, log an error, and leave the file in the temp directory.

Thanks for the report!

ShellLB() Objects.

gracefully.

This works around an apparent bug in binkp where it doesn't appear to
initialize the BinkD compatible crypto correctly when using an empty
password.

error message being logged.

buffer, when supplied).
Now, when a value buffer (non-NULL pointer) is supplied, we return a pointer to
that buffer instead of the value in the string list (which is not trimmed).
This was introduced in rev 1.120 (July 2011) as part of an optimization
(optional value buffers).
iniReadString() was not affected.

Convert log_level to LogLevel to be more consistent with sbbs.ini, services.ini
etc.

the constructor things.  This allows TLS-enabled services to work correctly,
and removes an ugly hack from the web server.

There's still an odd issue with the NNTP service when using TLS though.

how Radius appears to say goodbye.

correctly.

2016-01-20 06:06:39 ERROR line 1836 renaming c:\fd\outbound\20060640.pk_ to
c:\fd\outbound\20060640.pkt
I think this is because the file 200606040.pkt already existed when the
.pk_ temp file was created and thus the rename will fail (can't rename over
an existing file) and then the packet is sent to the wrong link.
When generating a packet name, keep incrementing until both the .pkt and
.pk_ variants do not already exist. This should fix this scenario.

inbound dir.

This is now being tested live on my system... watch this space for more
updates.

If all configured remote nodes have this option, encryption is not required.

While we're here, if none of the remote nodes are configured, don't restrict
them in any way... it won't be a secure session regardless.

If this is set, and there is a connection attempt which does not support
encryption, an error will be returned.

I epxect to actually require this by default in the near future.

This is a callout if either client.socket is undefined or if
client.socket.descriptor === -1