Discussion:
[dkim-milter-discuss] error seting up dkim-milter with sendmail
patricio
2010-05-20 23:20:18 UTC
Permalink
I have sendmail 8.13.3, I have installed dkim-milter 2.8.3 in a red hat enterprise linux 5 on a ia64 integrity server, the installation process was ok, i have installed the adsp and selector dns records, i have set up the line for the socket in sendmail configuration, all of that following the guide on http://www.elandsys.com/resources/sendmail/dkim.html
i have initiated the dkim-filter with:

dkim-filter -l -p inet:***@localhost -d mydomain.com -k /etc/ssl/mail.domainkeys/private/default.mydomain.key.pem -s default

now, when i probe my smtp sign tthe messages, to check-***@verifier.port25.com and sa-***@sendmail.net, every time they answerme that i havent dkim,

whe i try the dkim with:
dkim-testkey -d mydomain.com -k /etc/ssl/mail.domainkeys/private/default.mydomain.key.pem -s default

it says:

dkim-testkey: /etc/ssl/mail.domainkeys/private/default.mail.key.pem: WARNING: unsafe permissions
dkim-testkey(15003): unaligned access to 0x60000fffff88000e, ip=0x20000000002d2e80
dkim-testkey(15003): unaligned access to 0x60000fffff88000e, ip=0x20000000002d2ec1
dkim-testkey(15003): unaligned access to 0x60000fffff88000e, ip=0x20000000002d6250
dkim-testkey(15003): unaligned access to 0x60000fffff88000e, ip=0x20000000002d2f80




dmesg says the same:

dkim-testkey(12194): unaligned access to 0x60000fffffe17ffe, ip=0x20000000002d6250
dkim-testkey(12194): unaligned access to 0x60000fffffe17ffe, ip=0x20000000002d2f80
dkim-testkey(5463): unaligned access to 0x60000fffffd13ffe, ip=0x20000000002d2e80
dkim-testkey(5463): unaligned access to 0x60000fffffd13ffe, ip=0x20000000002d2ec1
dkim-testkey(5463): unaligned access to 0x60000fffffd13ffe, ip=0x20000000002d6250
dkim-testkey(5463): unaligned access to 0x60000fffffd13ffe, ip=0x20000000002d2f80
dkim-testkey(5559): unaligned access to 0x60000fffffd47ffe, ip=0x20000000002d2e80
dkim-testkey(5559): unaligned access to 0x60000fffffd47ffe, ip=0x20000000002d2ec1
dkim-testkey(5559): unaligned access to 0x60000fffffd47ffe, ip=0x20000000002d6250
dkim-testkey(5559): unaligned access to 0x60000fffffd47ffe, ip=0x20000000002d2f80
dkim-testkey(6590): unaligned access to 0x60000fffff9effce, ip=0x20000000002d2e80
dkim-testkey(6590): unaligned access to 0x60000fffff9effce, ip=0x20000000002d2ec1
dkim-testkey(6590): unaligned access to 0x60000fffff9effce, ip=0x20000000002d6250
dkim-testkey(6590): unaligned access to 0x60000fffff9effce, ip=0x20000000002d2f80
dkim-testkey(7748): unaligned access to 0x60000fffff957fce, ip=0x20000000002d2e80
dkim-testkey(7748): unaligned access to 0x60000fffff957fce, ip=0x20000000002d2ec1
dkim-testkey(7748): unaligned access to 0x60000fffff957fce, ip=0x20000000002d6250
dkim-testkey(7748): unaligned access to 0x60000fffff957fce, ip=0x20000000002d2f80
dkim-testkey(13113): unaligned access to 0x60000fffffb77fde, ip=0x20000000002d2e80
dkim-testkey(13113): unaligned access to 0x60000fffffb77fde, ip=0x20000000002d2ec1
dkim-testkey(13113): unaligned access to 0x60000fffffb77fde, ip=0x20000000002d6250
dkim-testkey(13113): unaligned access to 0x60000fffffb77fde, ip=0x20000000002d2f80
dkim-testkey(14883): unaligned access to 0x60000fffffe3000e, ip=0x20000000002d2e80
dkim-testkey(14883): unaligned access to 0x60000fffffe3000e, ip=0x20000000002d2ec1
dkim-testkey(14883): unaligned access to 0x60000fffffe3000e, ip=0x20000000002d6250
dkim-testkey(14883): unaligned access to 0x60000fffffe3000e, ip=0x20000000002d2f80
dkim-testkey(14916): unaligned access to 0x60000fffffc9000e, ip=0x20000000002d2e80
dkim-testkey(14916): unaligned access to 0x60000fffffc9000e, ip=0x20000000002d2ec1
dkim-testkey(14916): unaligned access to 0x60000fffffc9000e, ip=0x20000000002d6250
dkim-testkey(14916): unaligned access to 0x60000fffffc9000e, ip=0x20000000002d2f80



any idea??

Loading...