Your message dated Mon, 30 Jun 2014 13:43:29 +0200
with message-id <[email protected]>
and subject line Re: Bug#749337: Acknowledgement (spamassassin: false DKIM
invalid signal on signed letters)
has caused the Debian Bug report #749337,
regarding spamassassin: false DKIM invalid signal on signed letters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
749337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749337
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: spamassassin
Version: 3.3.2-5+deb7u1
Severity: important
Case
1 MUA sending the same letter (changing only Message-ID and Date) to
Exim MTA (server A)
Server A adds some headers (the same headers except the recieved: ) then
signs it and gives it to server B's Exim via SMTP.
Server B's Exim uses spamassassin to check the e-mail.
/etc/default/spamassassin modified for debuging, added options:
--syslog=debug --debug=dkim
>From 10 letters sent, 3-4 has failed dkim signature according to
spamassassin. Exim also checks it, it says verification succeeded.
For those cases, when the verification fails, spamd doesn't log anything.
If I upload the supposedly wrong letter to the server, it passes the
following check from the command line:
spamassassin -t -D dkim < /tmp/asd
May 26 14:27:56.768 [23620] dbg: dkim: using Mail::DKIM version 0.39
May 26 14:27:56.771 [23620] dbg: dkim: performing public key lookup and
signature verification
May 26 14:27:56.782 [23620] dbg: dkim: DKIM, i=@<sanitized>.hu,
d=<sanitized>.hu, s=mailbox1, a=rsa-sha256, c=relaxed/relaxed, pass,
does not match author domain
May 26 14:27:56.782 [23620] dbg: dkim: signature verification result: PASS
May 26 14:27:56.782 [23620] dbg: dkim: adsp: performing lookup on
_adsp._domainkey.<sanitized>.<sanitized>.hu
May 26 14:27:56.788 [23620] dbg: dkim: adsp result: U/unknown (dns:
unknown), author domain '<sanitized>.<sanitized>.hu'
May 26 14:27:56.791 [23620] dbg: dkim: VALID signature by
<sanitized>.hu, author system@<sanitized>.<sanitized>.hu, no valid matches
May 26 14:27:56.791 [23620] dbg: dkim: author
system@<sanitized>.<sanitized>.hu, not in any dkim whitelist
With the command above, no invalid signature message came out.
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages spamassassin depends on:
ii adduser 3.113+nmu3
pn libarchive-tar-perl <none>
ii libhtml-parser-perl 3.69-2
ii libnet-dns-perl 0.66-2+b2
ii libnetaddr-ip-perl 4.062+dfsg-1
ii libsocket6-perl 0.23-1+b2
ii libsys-hostname-long-perl 1.4-2
ii libwww-perl 6.04-1
ii perl 5.14.2-21+deb7u1
ii perl-modules [libio-zlib-perl] 5.14.2-21+deb7u1
Versions of packages spamassassin recommends:
ii gcc 4:4.7.2-1
ii gnupg 1.4.12-7+deb7u3
ii libc6-dev 2.13-38+deb7u1
ii libio-socket-inet6-perl 2.69-2
pn libmail-spf-perl <none>
ii make 3.81-8.2
ii perl [libsys-syslog-perl] 5.14.2-21+deb7u1
pn re2c <none>
ii spamc 3.3.2-5+deb7u1
Versions of packages spamassassin suggests:
ii libdbi-perl 1.622-1
ii libio-compress-perl [libcompress-zlib-perl] 2.052-1
ii libio-socket-ssl-perl 1.76-2
ii libmail-dkim-perl 0.39-1
pn libnet-ident-perl <none>
ii perl [libcompress-zlib-perl] 5.14.2-21+deb7u1
pn pyzor <none>
pn razor <none>
-- Configuration Files:
/etc/default/spamassassin changed [not included]
/etc/spamassassin/local.cf changed [not included]
-- debconf-show failed
--- End Message ---
--- Begin Message ---
thanks
We found out that the problem was a configuration issue in our MTA and
the problem is not a spamassassin bug. Sorry for the incorrect bugreport.
--- End Message ---
