RE: [dkim-ops] no signature data on the log

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Fri, 12 Mar 2010 10:45:33 -0800

“no signature data” means the filter decided your message should be verified rather than signed, and then logged that the message was unsigned. This means the information you provided for Domain or the SigningTable doesn’t match the properties of the mail you are sending, so it’s never selecting “sign” mode for your mail.

Adjust your configuration to contain this line:

LogWhy True

Then restart your filter, send a message through it, and see what it says. This line will cause some additional logging that should reveal why your configuration and your mail’s content aren’t lining up for signing.

Please subscribe to opendkim-users_at_lists.opendkim.org<mailto:opendkim-users_at_lists.opendkim.org> for further support.

-MSK

From: dkim-ops-bounces_at_mipassoc.org [mailto:dkim-ops-bounces_at_mipassoc.org] On Behalf Of Murat ALTIPARMAK
Sent: Friday, March 12, 2010 9:48 AM
To: dkim-ops_at_mipassoc.org
Subject: [dkim-ops] no signature data on the log

Dear All;

I hope that someone could help me here on this list. I successfully installed "opendkim 2.0" from tar.gz file on debian 4.0 box without any problem and error. After the installaton, according to the configuration steps I generated public and private keys and put the public key in the DNS zone file. Now

> opendkim-testkey runs and returns without error.

I also edited /etc/opendkim.conf file according to our needs pointing out our domain, selector and the location of key file and etc. And now I am starting opendkim and it is starting successfully as below from the log file:

Mar 12 11:53:09 mail01 opendkim[18687]: OpenDKIM Filter v2.0.0 starting (args: -x /etc/opendkim.conf)

However, whenever I try to send an email I am always getting the same log as below indicating that no signature data:

Mar 12 18:11:08 mail01 opendkim[18687]: o2CGB8jg023669: no signature data

I checked the permissions of the private key file and it is readable by both root and dkim users.

What am I doing wrong or missing? Is there anyone who experienced the same error?

Thank you in advance...

Murat


Received on Fri Mar 12 2010 - 18:45:43 PST