Hi again
Murray S. Kucherawy schrieb:
> On Sun, 4 Jan 2009, Thomas Bader wrote:
>> Jan 3 23:09:26 valmar dkim-filter[952]: 3C9D8342EEEF SSL
>> error:04067069:rsa routines:RSA_EAY_PUBLIC_DECRYPT:pkcs1 padding too
>> short
>
> Can you use the logs (i.e. grep for "3C9D8342EEEF") to figure out which
> public key was used to sign the message, or go look at the message if it's
> still there and give me the values of "d=" and "s="?
It was a message sent by me to my own account. d equals dawnlink.net, s
equals default (default._domainkey.dawnlink.net). I included you in CC,
so you will also get a fresh DKIM-Signature header from my system. I
used "dkim-genkey" to generate my key pair
Oh, and btw:
# dpkg -l | grep dkim
ii dkim-filter 2.6.0.dfsg-1~bpo40+2
DomainKeys Identified Mail (DKIM) Milter imp
I' using dkim-filter 2.6.0 from backports.org (Debian). I posted OpenSSL
verification information in my other mail to the mailing list.
As I have pointed out in my other mail this also happens with mails send
by 3rd parties to me.
I had one more idea for testing: I sent an empty mail to sa-test (AT)
sendmail.net. The reply sent back to me again caused a "padding too
short" message again, but also did successfully verify too:
Authentication-Results: mailer.dawnlink.net; dkim=pass (1024-bit key)
[email protected]; dkim-asp=none
sendmail.net:1/0 2 pass/0 fail, last l=0, a=1, Mon Jan 5 19:39:57 2009
So I now have three test cases which also cause the same error message:
mails sent by me to my own mail box, mails sent by resistor.net and
mails sent by sendmail.net. Therefore I think the problem is probably
related to a bug in my local OpenSSL library (just guessing, I'm not
sure). Or could it also be the case that my local DNS resolver somehow
messes up the TXT record response?
Regards,
thomas.
------------------------------------------------------------------------------
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss