RE: difference between opendkim-testmsg and opendkim for verification

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Tue, 29 Jan 2013 11:53:04 -0800 (PST)

On Tue, 29 Jan 2013, Vinubalaji Gopal wrote:
> I can reproduce with just about any email. For example try sed instead
> of the unix2dos command on the simple email you were trying to reproduce
> the problem I described:
> sed -i -e 's/$/\r/' gmail

That leaves me with a message that has one CR on some lines and two on
others. That too will confuse things.

The input message you sent has had its CRs stripped from any header field
that's continued. It looks like something in your handling path is not
doing field wrapping properly.

Is anyone else observing inconsistent results between opendkim-testmsg and
opendkim itself, with the provided sample message or any other?

> I think unix2dos doesn't really put carriage returns instead of newlines
> (probably there is some option to add carriage returns).

According to its man page:

      When called without parameters, the unix2dos utility reads from the stan-
      dard input, transforming LF characters into CR/LF pairs and writing them
      to the standard output.

-MSK
Received on Tue Jan 29 2013 - 19:53:22 PST