Hi Murray,
your last messages to the opendkim-users mainlinglist
arrive at my server with 2 dkim-signatures.
1. medusa3 / blackops.org ( your personal server )
2. mail2010 / opendkim.org ( lists.opendkim.org )
my server (opendkim-2.2.0-Beta1) tries to verify:
Sep 8 14:19:57 taro opendkim[10723]: 7B7402D7E: ns1.qubic.net
[208.69.177.116] not internal
Sep 8 14:19:57 taro opendkim[10723]: 7B7402D7E: not authenticated
Sep 8 14:19:58 taro opendkim[10723]: 7B7402D7E: message has signatures
from opendkim.org, blackops.org
Sep 8 14:19:58 taro opendkim[10723]: 7B7402D7E: DKIM verification successful
for some unknown reason my server sends an report with
Subject "DKIM failure report for 7B7402D7E" and Content-Type set to
"...report-type=feedback-report..."
The Receiver of the report is set to "msk+dkim_at_lists.opendkim.org"
which will bounce.
I think the msk+dkim is a part of
$ dig _adsp._domainkey.blackops.org txt +short
"dkim=all\; r=msk+dkim_at_blackops.org"
while lists.opendkim.org is the last signature.
The DKIM-REport is not generated, ich I switch back to version 2.1.3
it took some days till I found the bounces in ~dkim/Mail ;-)
( Thats why I ask for a possibility to setup the ReportAddress )
I will configure my server to bcc all mails from the dkim-user to me...
Idee: could opendkim bcc a report to the ReportSender ?
( another reason to setup a good ReportAddress :-)
btw.
2.2.0.Beta1 still dies with
opendkim-db.c:2233: dkimf_db_get: Assertion `db != ((void *)0)' failed.
I enabled corefiles but gdb do not print me any backtrace.
I think, 2.2.0.Beta1 dies only while verifing Mails *your* mails sent
to the mailinglist. perhaps the doublesignature is one reason.
I stitched back to 2.1.3
Andreas
--
Viele Grüße
Andreas Schulze
Received on Wed Sep 08 2010 - 12:51:13 PST