RE: repute-client

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Thu, 5 Jan 2012 10:03:15 -0800

> -----Original Message-----
> From: opendkim-dev-bounce_at_lists.opendkim.org [mailto:opendkim-dev-bounce_at_lists.opendkim.org] On Behalf Of Andreas Schulze
> Sent: Thursday, January 05, 2012 4:31 AM
> To: opendkim-dev_at_lists.opendkim.org
> Subject: repute-client
>
> 1. I saw, that opendkim queries the reputation webserver without a UserAgent Header.
> Maybe there should be send one? ClamAV (www.clamav.net) for example updates pattern via also http.
> The updater (freshclam) sends his version number as user-agent header.
> Now it turns out as a nice feature to block very old installations at the updateserver.
> Maybe there will be some needs to distinguish different clients at the repute server.
> A UserAgent field is very handy and common.

We use libcurl to make our queries. I would have assumed it's adding one, but I guess it's off by default. I'll have it add one.

> 2. I disabled ReputationCache and restarted odk. I also turned off the repute webserver.
> Mails still pass the MTA (very good!) but there is no logging that the configured
> reputation queries fail.

I've added an "On-ReputationError" control, which defaults to "accept", so you can decide what to do if the queries are failing. It will log something now in either case. What's proving difficult is getting the actual text of the error out to the logs. I'll see if I can improve that.

> 3. There is also no other logging related to reputation. But thats a
> point murray is aware :-)

It currently logs nothing if the reputation query succeeds and no limit has been reached. There is logging when a limit is reached, however. I didn't want the logs to get too noisy. Do you want those details for every message anyway?

-MSK
Received on Thu Jan 05 2012 - 18:03:24 PST