On Thu, 18 Dec 2008, deiva shanmugam wrote:
> I had built 64-bit libdkim in solaris 10. I'm trying to cross
> check whether the body hash and signature created by libdkim against
> openssl , by doing manual canonicalization and calculating hash and
> signature using openssl commands. But the hash created by both of them
> The Data Was very simple to be: "This\r\n"
> But the hash was completely different.
> The openssl command was:
> opennsl dgst -sha1 -in Inputfile -out Outfile
> Inputfile contains : This\r\n
> The Version of dkim-milter i'm using is: dkim-milter-2.8.0.Beta4
In general, please restrict conversations about the beta releases to the
beta list. However, this probably applies to all versions and is a
general theory question.
In the public releases, try setting the environment variable DKIMDEBUG to
"c", then restart your filter and send your test message. In /var/tmp
you'll find some "dkim.*" files named, in part, after the MTA job ID that
was processed. You should be able to back-track from your logs or the
Received: headers in your message to find the canonicalized body. You can
then "diff" that against your original file to see how they may have
changed between your file and what the MTA actually saw.
The method is different in the 2.8.0 Beta releases. Check your
dkim-filter.conf(5) man page for details there.