Hi,

    When relaxed body canonicalization is adopted, in case of body with only empty lines[more than 1], all these empty lines will be removed [as acc. to RFC , all the trailing empty lines need to be removed] and the body is signed.[Basically a body hash for 0 length is generated]. Am i right??

I made use of dkim-milter to sign mails. When my body of the mail has only empty lines, libdkim signs the body for CRLF character (l=2), in case of relaxed canonicalization. Is this the expected behaviour ?

Please help me in this issue.

Thanks,
Deiva Shanmugam

On Wed, Jun 10, 2009 at 5:37 PM, <dkim-milter-discuss-request@lists.sourceforge.net> wrote:
Send dkim-milter-discuss mailing list submissions to
       dkim-milter-discuss@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
       https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
or, via email, send a message with subject or body 'help' to
       dkim-milter-discuss-request@lists.sourceforge.net

You can reach the person managing the list at
       dkim-milter-discuss-owner@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dkim-milter-discuss digest..."


Today's Topics:

  1. Re: Unsuccessful verification status for space between header
     field name and colon. (SM)


----------------------------------------------------------------------

Message: 1
Date: Tue, 09 Jun 2009 07:36:20 -0700
From: SM <sm@resistor.net>
Subject: Re: [dkim-milter-discuss] Unsuccessful verification status
       for space between header field name and colon.
To: dkim-milter general discussion
       <dkim-milter-discuss@lists.sourceforge.net>
Message-ID: <6.2.5.6.2.20090609073032.034eaba0@resistor.net>
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Deiva,
At 03:32 09-06-2009, deiva shanmugam wrote:
>The headers that are being signed are:

[snip]

>Subject :Space after colon

I guess you mean space before the colon.

>The DKIM-Signature generated:
>
>DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>d=<http://lax.qa.juno.com>lax.qa.juno.com;

As the canonicalization is relaxed, the space will be removed.

>Observation: When the headers are signed using relaxed
>canonicalization, the Verification status by Gmail - "hardfail" and
>AOL - "Fail".
>
>If simple canonicalization is observed,then successful verification
>by Gmail and AOL.

That points to a problem when using relaxed canonicalization.

Can you send me a DKIM-signed email to demonstrate the above problem off-list?

Regards,
-sm





------------------------------

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects

------------------------------

_______________________________________________
dkim-milter-discuss mailing list
dkim-milter-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss


End of dkim-milter-discuss Digest, Vol 36, Issue 4
**************************************************