At Nelgin's suggestion, if all the messages in a packet are either good or bad, say so (since no .good or .bad file will be generated in that case).

When this function was called multiple times (e.g. multiple messages in a pkt),
it would keep appending to the current (static) string, eventually overflowing
the buffer and corrupting the stack. Although reported in pktdump, it could
have also happened with fmsgdump if passed multiple stored message (.msg) files.

Fixes #295 reported by Nelgin

or any lines that were only terminated with carriage-return (\r)
since these are treated rather-oddly by the FTN software as a
line-ending and line-feeds are to be ignored. So transfer \r to \n
on output and ignore the \n's in the body text.

Hopefully not introducing any bugs in the process.

Hopefully not introducing any bugs in the process.

Also converts Ctrl-A chars to '@", so behaves similar to fmsgdump now.
SEEN-BY's and AREA lines aren't dumped with -c because they don't begin with
a Ctrl-A.

file containing only the good or bad messages, leaving the orignal *.pkt file
intact.
The -recover option will *only* create a *.good file (renamed from .recovered).
Now, if the recovered (good) or bad output file has no messages or is the exact
same size as the original pkt file, the output file is automatically deleted.

valid pkdmsg type.
This will allow better re-sync with a badly corrupted packet.
I waffled about whether it should try to read the variable header fields if the
DateTime field of the fixed header is invalid. Currently, it does. The pkdmsg
header does not have very good identifying marks to re-sync with, so it's
still possible that a valid msg that follows a corrupted one could get skipped.
I would need some good set of varying examples of corrupted packets to test
with, but I'm sure it's possible to "do better".

duplicates of all the parsed packet files, but excluding all corrupted packed
messages. The recovered packet files are named *.recovered.
Also improved the corrupted packed message header detection to make this
feature more useful.
Created at the request of Nelgin who promises to test and use, for better or
for worse, in sickness and in health, from this day forward, yadda yadda yadda.

Fix GCC warning: field precision specifier ‘.*’ expects argument of type ‘int’, but argument 3 has type ‘long unsigned int’ [-Wformat=]

size_t.

Print wanring if type 2+ orig/dest zones don't match the zone fields in the
type-2 portion of the header.
Updated some pkt header field names in fidodefs.h.

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

Display the packet password, if one was specified.