Hi,
I use the DKIM library that comes with the milter with my own application.
I'm just testing an upgrade to 2.5.1 and am getting mixed results with
other people being able to validate my messages. I haven't changed the
way I use the API for signing messages.
I sent the same message to seven different automated validators and five
were able to successfully validate the signature and two weren't including
sendmail.net. Everyone was able to validate the messages I signed with
2.4.x. Does anyone have an idea what might have changed and what I can
do to debug it?
I'm able to validate all of the automated responses bar the one from
testing.dkim.org which doesn't have a key in DNS.
Thanks,
Andy
-- Passed --
Authentication-Results: c3po.altn.com
dkim=pass header.d=fiddaman.net (1:0:good);
X-DKIM: Sendmail DKIM Filter v2.5.1 medusa.blackops.org m2QN6OKh027985
Authentication-Results: medusa.blackops.org; dkim=pass (1024-bit key)
[EMAIL PROTECTED]
(dkimtest.jason.long.name)
This is the overall result of the message verification:
pass
testing.dkim.org; v=0.1; dkim=pass, [EMAIL PROTECTED] (
sig from fiddaman.net/apr2007 verified; );
ssp=pass, [EMAIL PROTECTED]
(verifier.port25.com)
DKIM check: pass
-- Failed --
Authentication System: DomainKeys Identified Mail
Result: DKIM signature confirmed BAD
Description: Signature verification failed, message may have
been tampered with or corrupted
Reporting host: sendmail.net
(dk.elandsys.com)
DKIM Test: hardfail (SSP)
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
