RE: OpenDKIM 2.3.0 Release = stable!

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Wed, 2 Mar 2011 16:15:30 -0800

> -----Original Message-----
> From: opendkim-users-bounce_at_lists.opendkim.org [mailto:opendkim-users-bounce_at_lists.opendkim.org] On Behalf Of Steve Jenkins
> Sent: Wednesday, March 02, 2011 3:48 PM
> To: opendkim-users_at_lists.opendkim.org
> Subject: Re: OpenDKIM 2.3.0 Release = stable!
>
> How about some integration with Amavis-new? That seems to be an
> extremely popular "front-end" for mail processors, and I know they're
> tinkering with DKIM stuff in there, although I didn't really look that
> hard at exactly what it was doing DKIM-wise when I set it up.

Did you have something specific in mind?

Off the top of my head, and not knowing much about amavisd-new, I suspect the only integration would be to try to do correlation between signing domains and virus traffic, just like I'm using the OpenDKIM stats extensions locally to try to correlate signing domains with spam. Apart from that they're two filters that analyze a message and report a verdict of sorts.

But wouldn't amavisd-new reject messages it finds to be suspect or infected? If that's the case, OpenDKIM wouldn't see them anyway. The only real interaction they'll have is if amavisd-new runs first and adds a header field to suspect messages without rejecting them.

> When I first set up OpenDKIM, I was initially more interested in
> making sure my outgoing mail got signed, but since that's happening so
> reliably now that there's nothing for me to tinker with there, I'd
> like to turn my attention toward verification, scoring (perhaps with
> Amavis-new), and even possible rejection of incoming mail based on the
> sending domain's DKIM policies (or lack thereof).

What policy items do you find interesting for filtering?

-MSK
Received on Thu Mar 03 2011 - 00:15:37 PST