improvements to sa-exim

marc, hi,

some recommended improvements to sa-exim particularly the SaRunCond
stuff.

when setting up yes i got a fake message with an SaRunCondSomething
in it - within about two days.

can i recommend putting in something like a digital signature
or md5 hash or an MD5 hash of the MX hostname or a hash of the
filename under which the message is saved into the logs, or
_something_ that is unique and generated server-side that cannot be
forged?

so you get "X-SaRunCond = yes-5e39ac09b2f4".

if nothing else, the hash should be generated from a random number
that is changed every 10 minutes or so.

its life expectancy is only a few seconds (from generated in
exim4 to being saved in the headers to being checked in sa-exim.

what you reckon?

l.

-- 
-- 
expecting email to be received and understood is a bit like
picking up the telephone and immediately dialing without
checking for a dial-tone; speaking immediately without listening
for either an answer or ring-tone; hanging up immediately and
then expecting someone to call you (and to be able to call you).
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:[email protected]"> [email protected] </a> <br />