You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2014/06/26 21:46:02 UTC
[Bug 7062] New: Mail-DKIM-0.4 seems brokken compared to opendkim
testing
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7062
Bug ID: 7062
Summary: Mail-DKIM-0.4 seems brokken compared to opendkim
testing
Product: Spamassassin
Version: 3.3.2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Plugins
Assignee: dev@spamassassin.apache.org
Reporter: me@junc.eu
X-Spam-Rules: TestsScores=(BAYES_95=3,BOGOFILTER_UNSURE=0.1,DIET_1=0.001,
DKIM_SIGNED=0.1,HTML_IMAGE_RATIO_02=0.437,HTML_MESSAGE=0.001,SPF_PASS=-0.1,
T_DKIM_INVALID=0.01)
while opendkim add
Authentication-Results: duggi.junc.org;
dkim=pass (1024-bit key) header.d=example.com header.i=innocent@example.com
header.b=gBP9Uw+x;
dkim-atps=neutral
is this the same problem as in bug 6462 ?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7062] Mail-DKIM-0.4 seems brokken compared to opendkim testing
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7062
Mark Martinec <Ma...@ijs.si> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Mark Martinec <Ma...@ijs.si> ---
Without further evidence, I can only close this as not-a-bug,
at least not in Mail::DKIM nor in SpamAssassin.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7062] Mail-DKIM-0.4 seems brokken compared to opendkim testing
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7062
Todd Rinaldo <to...@cpanel.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |toddr@cpanel.net
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7062] Mail-DKIM-0.4 seems brokken compared to opendkim testing
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7062
--- Comment #1 from Mark Martinec <Ma...@ijs.si> ---
(In reply to Benny Pedersen from comment #0)
> X-Spam-Rules: TestsScores=(BAYES_95=3,BOGOFILTER_UNSURE=0.1,DIET_1=0.001,
> DKIM_SIGNED=0.1,HTML_IMAGE_RATIO_02=0.437,HTML_MESSAGE=0.001,SPF_PASS=-0.1,
> T_DKIM_INVALID=0.01)
>
> while opendkim add
>
> Authentication-Results: duggi.junc.org;
> dkim=pass (1024-bit key) header.d=example.com header.i=innocent@example.com
> header.b=gBP9Uw+x;
> dkim-atps=neutral
I'm not aware of any such issues with Mail::DKIM 0.40
or in a DKIM plugin in SpamAssassin.
If opendkim is used as a before-queue milter and SpamAssassin as
a post-queue content filter, then it is very likely that a message
has been altered inbetween.
> is this the same problem as in bug 6462 ?
Possibly. Sendmail is notorious for changing header fields,
like 'prettyfying' some syntax (like adding a space after colon),
or for canonicalization of addresses in From/To/Cc header fields
(like adding a missing domain name). The more the original message
has a broken or unusual header section, the more likely some
'smart' MTA will try to 'fix' it, breaking a DKIM signature while
doing so.
The best way to find out is to capture the message as it is
seen by opendkim, and comparing it to what is passed on to SpamAssassin.
Sometimes it is possible to guess what the change was by studying
the message as delivered to a recipient.
--
You are receiving this mail because:
You are the assignee for the bug.