Re: Ordering of On- configuration Options

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Fri, 14 Mar 2014 09:14:02 -0700 (PDT)

On Thu, 13 Mar 2014, Alan Chandler wrote:
> Mar 12 13:01:56 piserver milter-greylist: (unknown id): skipping greylist
> because this is the default action, (from=<dovecot-bounces_at_dovecot.org>,
> rcpt=<alan_at_chandlerfamily.org.uk>, addr=wursti.dovecot.fi[87.106.245.223])
> ACL 39
> Mar 12 13:01:56 piserver postfix/smtpd[19372]: E39DA200C5:
> client=wursti.dovecot.fi[87.106.245.223]
> Mar 12 13:01:57 piserver postfix/cleanup[19393]: E39DA200C5: milter-reject:
> END-OF-MESSAGE from wursti.dovecot.fi[87.106.245.223]: 5.7.0 bad DKIM
> signature data; from=<dovecot-bounces_at_dovecot.org>
> to=<alan_at_chandlerfamily.org.uk> proto=ESMTP helo=<wursti.dovecot.fi>
> Mar 12 13:01:57 piserver postfix/smtpd[19372]: disconnect from
> wursti.dovecot.fi[87.106.245.223]

It looks like dkim-filter isn't set to do any logging. It logs its own
entries when set to do so. Check your "Syslog" setting. The same setting
exists in opendkim.

The specific entry here suggests it's On-BadSignature that's firing rather
than On-NoSignature. It does look quite possible, based only on what you
cited here, that it's a case of author signatures being clobbered by
mailing list modifications.

-MSK
Received on Fri Mar 14 2014 - 16:14:26 PST