Hello,
for some project we're thinking about adding something *like*
x-signature: <some signed message digest>
to get this working in a quite straight way it would be nice to have
some variable containing a (or the) digest of the message body. (Or even
more comfortable, digest of the message body and selected header lines,
but this could be discussed later and is out of scope now.)
Currently I'm using something like ${run{/…/digest $message_exim_id}}.
The "digest" script calls "exim -Mvb | tail -n +1" to get the message
body. But this looks awful and relies on features I do not know (e.g.:
how sure can I be that inside the data acl the "exim -Mvb <id>"
command already works?)
So, to get the long story short: I thinking about having
$message_body_hash_sha1
(or something similar, the "interface" could be thought about)
What do you think? (I believe, the implementation shouldn't be too
difficult (\0 are already counted, thus some part of the code seems to
see the "message stream").
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann HS12-RIPE -----------------------------------------
gnupg encrypted messages are welcome - key ID: 48D0359B ---------------
gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B -
