super-wonderfull srandomdev() where available.

Where we can't, try to use /dev/urandom if possible...

If that fails, start making stuff up...

At some point, the Win32 build should use CryptGenRandom() which is slightly
better on Windows NT/2K/XP and vastly better on Vista... not present on 9x
apparently though.

HAS_DEV_URANDOM and URANDOM_DEV based on that

as well.

This fixes a bug where /dev/urandom is not a character special file
(on FreeBSD it's a symlink) and there is a random() function available.

In this case, the same sequence of random numbers was used for each process
(most noticable with jsexec).

pause if necessary is expected to be handled by the caller.

if true.

Call console.clear() in draw_main(true) so the screen is cleared rather than
overwritten.  On some terminal programs (ie: SyncTERM) this forces the current
screen into the scrollback rather than removing it.

1) When a log file does not exist, mark it as having been parsed rather
   than retrying next time.
2) Keep track of the oldest since date and do not parse after it

Make the config command work... this should be added as an external, or
a menu option.

X11.

If a "Command" key value is included in .ini file, will be used in place of
mail processor's name (section name in square brackets).
If an "Eval" key value is included in .ini file (for non-native mail procs),
the key value will be JS-evaluated instead of executing an external script.
Fix: If a message is received for multiple local recipients and any of the
names match a mailproc's 'to' list, that mail processor will be executed.
These improvements and fixes allow a mailproc.ini entry like the following to
work:
[From Hosted Address]
	From = *@synchro.net,*@swindellfamily.com,*@weedpuller.com
	AccessRequirements=not user 1
	Eval = log("Removing mail from " + reverse_path); file_remove(message_text_filename)

(.can style wildcards are allowed)

to spamd. Some SA features require these header fields.
Received header support is currently disabled due to some issues, like:
1. Getting duplicates Received fields after processing the message
2. SpamAssassin *really* doesn't like dynamic IPs in Received header fields

SMTP HELO string from sender.

created.
Bug-fix for last commit (missing ;).

msg header.
Include the (envelope-from <>) comment in the "Received" header field.
Ingore any existing Return-Path header fields when parsing incomming message
headers.

does not support a zero size either.