Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Fri, 6 Jun 2014 00:44:03 -0700 (PDT)
From: zespri <nab@brutsoft.com>
To: users@spamassassin.apache.org
Message-ID: <1402040643146-109464.post@n5.nabble.com>
Subject: I'm getting T_DKIM_INVALID from gmail
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I realize that this is not directly related to spam assassin, but I appeal to
all you helpful folk here.
For whatever reason if I send an email from gmail when it arrives it's
marked with T_DKIM_INVALID. I inspected the original and the result and
there are a few differences. Dkim header has this:
"h=mime-version:in-reply-to:references:date:message-id:subject:from:to:content-type;"
I'm guessing these are the fields that are being signed.

The differences are:
1) Delivered-To header was gmail address became target address
2) New headers: Return-Path, X-Spam-Checker-Version, X-Spam-Level,
X-Spam-Status, Received, DKIM-Signature, X-Received
3) The last and I'm guessing the most important difference is that
Content-Type header is different. 

Here is what Content-Type header looks like:
Content-Type: multipart/alternative; boundary=089e013cb942d5a93f04fb25badd

Everything that goes after boundary= is different in the original message
and what ends up in the inbox.

I'm receiving the emails with postfix and it then goes to spamc and then to
dovecot. This is from master.cf:

> flags=DRhu user=vmail:vmail argv=/usr/bin/spamc -u ${recipient} -e
> /usr/lib/dovecot/deliver -d ${recipient}

Do you happen to have an idea why this is happening?

Cheers,
Andrew


--
View this message in context: http://spamassassin.1065346.n5.nabble.com/I-m-getting-T-DKIM-INVALID-from-gmail-tp109464.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.