--On Tuesday, April 10, 2012 10:59 PM +0000 "Murray S. Kucherawy"
<msk_at_cloudmark.com> wrote:
>> -----Original Message-----
>> From: locuse_at_mm.st [mailto:locuse_at_mm.st]
>> Sent: Tuesday, April 10, 2012 3:44 PM
>> To: Murray S. Kucherawy; opendkim-users_at_lists.opendkim.org
>> Subject: Re: opendkim AUTH pass-es for received mail, but fails on
>> forward ...
>>
>> hi
>>
>> On Tue, Apr 10, 2012, at 02:51 PM, locuse_at_mm.st wrote:
>> > (2) i'll explore this a bit with a different source email
>>
>> sending from an _at_gmail.com account, instead of an @fastmail.fm account,
>>
>> ...
>> From: locuse <#####_at_gmail.com>
>> To: locuse_at_doma.locusetest.net
>> ...
>>
>> for the scame scenario as the OP, forwarded mail again fails AUTH
>> similarly,
>>
>> http://pastebin.com/8Z4ESQC1
>
> Sorry, I was focused before on the ADSP temperror, not the DKIM failure.
>
> The altered Date: field is almost certainly the problem, assuming your
> DKIM signer signed the Date: field (most do). Look at your
> DKIM-Signature and see if "date" was listed in the value of the "h=" tag.
Just to note, Zimbra uses a redirect, not forward, as per section 4.3 of
<
https://www.rfc-editor.org/rfc/rfc3028.txt>. The only change we should be
making to the headers is to add X-Zimbra-Forwarded: <value>.
I'm not sure why Date: is changed, I'm investigating if that is Zimbra or
one of the components underneath (such as amavis).
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Received on Tue Apr 10 2012 - 23:18:51 PST