Re: Signing problems with OpenDKIM on Ubuntu

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Mon, 22 Apr 2013 11:28:26 -0700 (PDT)

On Mon, 22 Apr 2013, Jim Fenton wrote:
> Good thought, I don't see anything in syslog configs to limit logging
> that way. And some of these messages are from LogWhy, right?
>
> Apr 21 07:50:56 kernel opendkim[23151]: r3LEosIT026155: no MTA name
> match (host=kernel.bluepopcorn.net, MTA=MTA-v6)
> Apr 21 07:50:56 kernel opendkim[23151]: r3LEosIT026155:
> medusa.blackops.org [208.69.40.157] not internal
> Apr 21 07:50:56 kernel opendkim[23151]: r3LEosIT026155: not authenticated
> Apr 21 07:50:56 kernel opendkim[23151]: r3LEosIT026155: no signing
> domain match for 'blackops.org'
> Apr 21 07:50:56 kernel opendkim[23151]: r3LEosIT026155: no signing
> subdomain match for 'blackops.org'

This is the LogWhy stuff we're looking for. Was it not added for your
other message? When LogWhy is enabled it should be there for all
messages regardless of mode, because it's explaining the logic it's using
to make the sign vs. verify decision before it makes its conclusion.

-MSK
Received on Mon Apr 22 2013 - 18:28:50 PST