RE: no signing table

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Fri, 4 Mar 2011 09:22:23 -0800

> -----Original Message-----
> From: opendkim-users-bounce_at_lists.opendkim.org [mailto:opendkim-users-bounce_at_lists.opendkim.org] On Behalf Of Fabrizio Regalli
> Sent: Friday, March 04, 2011 8:58 AM
> To: opendkim-users
> Subject: no signing table
>
> Hi list,
>
> apparently I have no problem with opendkim. My sent messages are
> correctly signed I verified them with gmail/yahoo and other smtp test.
> Everything looks good.
> However my /var/log/mail.log contains a lot of this messages:
> [...]

These are logged for arriving messages. Taking them in turn:

> Mar 4 16:51:55 server opendkim[22095]: 1F40D4F338: no signing table match for `myuser_at_mydomain'

This means it looked for 'myuser_at_mydomain' and other variants of it in the SigningTable (if you have one) and didn't find a match, so it's not going to sign the message.

> Mar 4 16:51:55 server opendkim[22095]: 1F40D4F338: no signature data

This means the arriving message did not appear to have a signature on it.

> outmail017.snc4.facebook.com [66.220.144.149] not internal

This means the SMTP client IP address (the one shown) was not in your InternalHosts list, so the mail will not be signed.

> I don't think this is a problem but, just to be sure, could please
> someone confirm everything is it ok?

Yes, those are all normal. You can get rid of the "no signing table match" and "not internal" ones if you find them annoying by turning off "LogWhy" in your configuration file. That setting is meant to be on only if you're trying to figure out why mail isn't being signed when you think it should.

We should consider including the second one in "LogWhy" for some future release, but currently there's no way to turn that one off without turning logging off entirely.

-MSK
Received on Fri Mar 04 2011 - 17:22:30 PST