bundles:
1. If the unpackable bundle file was more then 48 hours old, it would not try
to rename it - the file date/time comparison logic was backwards and was trying
to rename the file only if it was *less* than 48 hours old (and could in
theory still be in transit).
2. If the unpackable bundle file was more than 48 hours old, SBBSecho would
continuously and indefinitely try to unpack it consuming CPU cycles and
generating log output. Forever.

Deuce.

don't read/write the file for *every* property!
Fixed several apparent memory leaks (upon errors) and at least one
freed-pointer usage.

header fields, not just the filler portion) - much more sane.

deletion by the maintenance process).

Don't reset the origin zone in import_netmail().
Fix-up type 2+ packet header parsing (ugh this is ugly).

Use zone information from packet header (rather than default/system zone)
since packed message headers don't zone information - use this address
for replying to AREAFIX requests.

Joe Delahaye.
Increment version to 2.21.

or 'longs'. Amazing that no one noticed.

int is 64-bit (not 32-bit).

MS's CRTL throws an assertion. Buffer size must be >=2.

than never?).

(e.g. "in private chat with digital man" rather than
"in private chat with sysop").

"local chat with sysop" rather than "private chat with node 0".

don't try to run it. Previously it would display an error to the user:
"Sorry, you have insufficient access to run that program" (which is confusing
for the user).

value in node status (e.g. for local chat user event).

<Deuce> It sohuldn't be passing strchr(str, 0) as a macro argument.
<Deuce> Pop that bugger into a temp char * and she'll be golden.
<Deuce> If you could make/commit that change for me, that'd be great

counter/limits as branch counter/limits.

If an external progarm is configured (in SCFG->External Progarms) is configured
to "execute on event" set to "Local/Sysop Chat", then that program will be
executed when the remote user is "pulled" into sysop-chat (e.g. via F10 key in
sbbsctrl) rather than running the normal built-in chat.
Don't change the current node's action (to XTRN) if it's currently PCHT
(private chat) as that's a signal to the local sysop chat app that the user
has disconnected.

If an external progarm is configured (in SCFG->External Progarms) is configured
to "execute on event" set to "Local/Sysop Chat", then that program will be
executed when the remote user is "pulled" into sysop-chat (e.g. via F10 key in
sbbsctrl) rather than running the normal built-in chat.

as spammers are now hijacking common/valid mail subjects (e.g.
"Google Email Verification") for their spam messages and blocking all msgs with
such subjects is too heavy-handed an approach. :-(

if a received messages is for local or relay. This comparison predates the
domains.cfg file which makes it obsolete. And it really bugged Deuce and
apparently was a problem for his new IPv6-happy version of resolve_ip(). :-P

Whatever we needed windows.h for here is gone.  this fixes the windows.h -> winsock.h / winsock2.h problem.

in SyncTERM.

Win32 binaries end with .exe.

Line with winmm and ws2_32 libs for Win32

Added new telgate flag: TG_NOLF.