I had similar no sig issues with dkim milter and postfix until I switched to opendkim.
Had to build/compile and install myself, but it was well worth it. Murray can give you the details, but dkim-milter is end of life. Go with opendkim http://www.opendkim.org/ ________________________________ From: patricio [mailto:[email protected]] Sent: Saturday, May 22, 2010 11:27 PM To: [email protected] Subject: [dkim-milter-discuss] error seting up dkim-milter with sendmail onia64 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 at http://www.elandsys.com/resources/sendmail/dkim.html <http://www.elandsys.com/resources/sendmail/dkim.html> i have initiated the dkim-filter with: dkim-filter -l -p inet:8...@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 [email protected] and [email protected], 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 at /var/log/maillog May 22 20:04:10 mail sendmail[380]: o4N13x28000380: Milter insert (1): header: Authentication-Results: mydomain.com; dkim=pass (512-bit key)\n\[email protected]; x-dkim-adsp=none May 22 20:08:01 mail dkim-filter[31077]: o4N17O5i000497: no signature data May 22 20:08:10 mail dkim-filter[31077]: o4N182Ad000518: no signature data May 22 20:08:50 mail dkim-filter[31077]: o4N18oFm000629: no signature data May 22 20:12:03 mail dkim-filter[31077]: o4N1BkbZ001062: no signature data May 22 20:14:46 mail dkim-filter[31077]: o4N1EZEF001171: no signature data May 22 20:17:42 mail dkim-filter[31077]: o4N1HTvT001299: no signature data May 22 20:18:47 mail dkim-filter[31077]: o4N1IT1Z001368 DKIM verification successful May 22 20:18:48 mail sendmail[1368]: o4N1IT1Z001368: Milter insert (1): header: Authentication-Results: mydomain.com dkim=pass (1024-bit key)\n\[email protected]; x-dkim-adsp=none May 22 20:21:19 mail dkim-filter[31077]: o4N1L6A9001495: no signature data May 22 20:21:51 mail dkim-filter[31077]: o4N1Lb4r001520: no signature data that is, as i understand, that my dkim-filter is only verifying, not signing the messages, any idea to solve this?? CONFIDENTIALITY NOTICE: The information in this Internet email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized.
------------------------------------------------------------------------------
_______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
