I apologize if this is not a good thing to ask, but can I pay someone
a few dollars maybe $15-$20 to fix this puppy? I want to punch myself
in the face. It seems so close, yet so far away. Someone could
probably fix it in 5 minutes. LOL.
On Thu, Sep 29, 2011 at 1:21 PM, Murray S. Kucherawy <msk_at_cloudmark.com> wrote:
>> -----Original Message-----
>> From: opendkim-users-bounce_at_lists.opendkim.org [mailto:opendkim-users-bounce_at_lists.opendkim.org] On Behalf Of N.
>> Sent: Thursday, September 29, 2011 12:16 AM
>> To: Murray S. Kucherawy
>> Cc: opendkim-users_at_lists.opendkim.org
>> Subject: Re: Relating to Domains..
>>
>> Hmm interesting. In terms of Postfix, I inserted the lines from Steve's
>> blog:
>>
>> http://stevejenkins.com/blog/2010/09/how-to-get-dkim-domainkeys-
>> identified-mail-working-on-centos-5-5-and-postfix-using-opendkim/
>>
>> smtpd_milters = inet:127.0.0.1:8891
>> non_smtpd_milters = $smtpd_milters
>> milter_default_action = accept
>> milter_protocol = 2
>>
>> Think line #4 could be the problem? It says its "optional" in a way in
>> Steve's blog.
>
> It shouldn't matter what protocol version you're talking. Even if the versions are incompatible, there should still be at least an attempt to communicate, but your strace showed none occurring. opendkim is just sitting there waiting for a connection that never comes.
>
> It would be unusual for postfix not to log anything if it tries to connect to port 8891 and fails, but I suppose that's possible. You could strace postfix to see if it's trying to connect to your filter, however my knowledge of postfix is near-zero so I wouldn't know how to tell you which process to trace.
>
>> I wonder if there's another way to see if "packet filter is
>> interfering with socket communication" somehow. Nothing is in the
>> maillog - no errors - and the email is getting sent.
>
> A packet filter probably doesn't log anything to the mail log. You might want to check your main syslog file or perhaps a security or audit log, or find out where your packet filter writes its log entries.
>
> You might also try temporarily turning off the packet filter altogether and repeating the test, just to eliminate it as the culprit.
>
> And there are the obvious things too: Did you add these lines to the right postfix configuration file, and direct postfix to re-read it (or restart postfix) after doing so?
>
> -MSK
>
>
>
Received on Thu Sep 29 2011 - 17:38:26 PST