Re: Trouble in using opendkim

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Sun, 16 Dec 2012 22:08:12 -0800 (PST)

On Sat, 15 Dec 2012, Christian R??ner wrote:
> Dec 15 20:19:16 mx0 opendkim[22798]: 3YNz2X1X2sz2WBq: SSL error:0906D06C:PEM routines:PEM_read_bio:no start line
> Dec 15 20:19:16 mx0 opendkim[22798]: 3YNz2X1X2sz2WBq: dkim_eom(): resource unavailable: PEM_read_bio_PrivateKey() failed

This means there's a syntax error in the private key you're using to sign.

If you didn't change anything and we didn't change anything, then I have
no idea where to begin debugging this. Something changed somewhere.

> I had version 1.7.2. Now I upgraded to verion 1.7.3, but this does not
> work either.

The code that parses private keys hasn't been changed between 2.7.2 and
2.7.3.

> opendkim 22798 opendkim 3u IPv6 19204215 0t0 TCP [2a01:4f8:131:1081:88:198:80:230]:34092->[2a01:4f8:131:1081::2]:389 (ESTABLISHED)
> opendkim 22798 opendkim 4u IPv6 19204221 0t0 TCP [2a01:4f8:131:1081:88:198:80:230]:34093->[2a01:4f8:131:1081::2]:389 (ESTABLISHED)

Startup doesn't require the ability to parse keys in certain cases, such
as when using LDAP, so this is not unexpected.

-MSK
Received on Mon Dec 17 2012 - 06:08:29 PST