Re: OpenDKIM isn't signing nor throwing any errors in log

From: Antony <sunnydelight_at_umich.edu>
Date: Sat, 10 Mar 2012 13:16:48 -0600

Todd,

Thank you for the reply. I got in touch with people on postfix mailing
list, and figured out the problem.
I had used vim to modify the postfix main.cf file, and that somehow does
not sit well with postfix.
The solution is to use postconf -e to add each entry manually, like so
sudo postconf -e 'smtpd_milters=inet:127.0.0.1:8891'
sudo postconf -e 'non_smtpd_milters=inet:127.0.0.1:8891'
sudo postconf -e 'milter_default_action=accept'
sudo postfix reload
sudo postfix -n

Viola!

Thank you all for the quick response. It feels good to get things to work.

-Antony

On 3/10/12 1:00 PM, Todd Lyons wrote:
> On Sat, Mar 10, 2012 at 6:38 AM, Antony<sunnydelight_at_umich.edu> wrote:
>> I can confirm that yes, Postfix, somehow disregards the setting in its
>> main.cf and remains unaware of OpenDKIM
>> The test is as simple as setting smtpd_milters& non_smtpd_milters to a
>> port that is not listening, i.e. inet:127.0.0.1:1234
>> After restarting the postfix and trying to send out another email. The
>> mail.log shows no sign of communication between Postfix& OpenDKIM; hence,
>> no errors of what so ever.
> The HOWTO by Steve has 3 specific lines in the postfix configuration,
> did you put all three?
>
> 1 smtpd_milters = inet:127.0.0.1:8891
> 2 non_smtpd_milters = $smtpd_milters
> 3 milter_default_action = accept
>
> I believe if you do postconf -a, it should print out all configuration
> settings (as read from its config files). If the above settings are
> not in it, then you are right, it is likely reading a different config
> file than what you thought.
>
> strace -e trace=file postconf -a # (or trace=open)
>
> Will show what files are accessed when you run the postconf command.
>
> ...Todd
Received on Sat Mar 10 2012 - 19:17:18 PST