RE: opendkim getting hardfail with Google

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Thu, 10 Mar 2011 10:32:59 -0800

> -----Original Message-----
> From: Rolf E. Sonneveld [mailto:R.E.Sonneveld_at_sonnection.nl]
> Sent: Thursday, March 10, 2011 8:39 AM
> To: Murray S. Kucherawy
> Cc: opendkim-users_at_lists.opendkim.org
> Subject: Re: opendkim getting hardfail with Google
>
> may I suggest to make 'none' the default to preserve existing behavior
> and to minimize the added complexity for sites that will not use this
> functionality?

The mechanism in 2.3.0 is to make no changes if ReplaceRules isn't defined; however, ReplaceRules affects all header fields if it is defined.

The new mechanism adds a second setting called ReplaceHeaders. The two interact as follows:

- If ReplaceRules isn't defined, nothing happens (as before).
- If ReplaceRules is defined but ReplaceHeaders isn't defined, all header fields are affected (as before).
- If both are defined, only those header fields named in the ReplaceHeaders data set are affected (new).

Thus, I think the current design preserves backward compatibility.

-MSK
Received on Thu Mar 10 2011 - 18:33:06 PST