I've been testing DKIM verification with a number of opendkim versions,
but I just noticed that outgoing messages were not being signed with
any of them. The last time they were signed was when I was testing
dkim-milter versions. What could be wrong?
When I run `opendkim-testkey', it reports that the keys do not match.
I assume I can correct this by regenerating the keys, but does
the opendkim check on this? Nothing was logged when it started up.
I reviewed the signing critera. The domain on the `From' header is
correct, matching `Domain testing.umanitoba.ca' in opendkim.conf. The
client did not authenticate, but it did connect to 127.0.0.1. That
should be sufficient. The client did connect to port 25, which I
suppose is excluded somehow. The macro list in opendkim.conf is
empty.
For testing, I'm just running `mailx' on the test mail server. It
invokes sendmail to connect to the local MTA. Here are the syslog
lines generated by the MTA:
Oct 20 11:37:28 setup01 sm-mta[3768]: [ID 801593 mail.info] o9KGbS7f003768: from=<mills_at_testing.UManitoba.CA>, size=395, class=0, nrcpts=1, msgid=<201010201637.o9KGbSfT003767_at_setup01.cc.umanitoba.ca>, proto=ESMTP, daemon=MTA, relay=mills_at_localhost [127.0.0.1]
Oct 20 11:37:28 setup01 opendkim[583]: [ID 699540 mail.debug] o9KGbS7f003768: no signature data
Oct 20 11:37:30 setup01 sm-mta[3768]: [ID 801593 mail.info] o9KGbS7f003768: Milter add: header: X-DCC-UofM-Metrics: setup01; whitelist
Oct 20 11:37:30 setup01 sm-mta[3771]: [ID 801593 mail.info] o9KGbS7f003768: to=<mills_at_cc.umanitoba.ca>, ctladdr=<mills_at_testing.UManitoba.CA> (107/104), delay=00:00:02, xdelay=00:00:00, mailer=esmtp, pri=120395, relay=electra.cc.umanitoba.ca. [130.179.16.34], dsn=2.0.0, stat=Sent (o9KGbUXd014579 Message accepted for delivery)
--
-Gary Mills- -Unix Group- -Computer and Network Services-
Received on Fri Oct 22 2010 - 16:37:58 PST