The milter is running and listening at port 10030 (I can connect with
The postfix instance does receive and handle the mail (I can see that in
But postfix makes no connection to port 10030.
I normally have an iptables rule that allows only user "amavis" to
connect to port 10030, but I've tried removing that restriction and that
did not help.
I always helps to ask for help - you then immediately see what you've
missed. I've suddenly seen the word "no_milters" in my mail below,
which probably explains the problem.
I expect it will help to remove that word - sorry for the inconvenience.
On 2017-11-26 21:44, Jesper Dybdal wrote:
> For incoming mail, I use Amavis as a pre-queue filter.
> I use policyd-spf-python for SPF check and let Amavis do DKIM check.
> I then wanted to add DMARC check. I am trying to do it using the
> opendmarc milter in the postfix instance to which Amavis re-injects
> the mail.
> However, the milter is not called at all.
> The postfix instance in question is defined as:
> 127.0.0.1:10028 inet n - y - - smtpd
> -o syslog_name=postfix/10028
> -o smtpd_authorized_xforward_hosts=127.0.0.0/8
> -o smtpd_client_restrictions=
> -o smtpd_helo_restrictions=
> -o smtpd_sender_restrictions=
> -o smtpd_relay_restrictions=
> -o smtpd_recipient_restrictions=permit_mynetworks,reject
> -o smtpd_data_restrictions=
> -o mynetworks=127.0.0.0/8
> -o milter_protocol=6
> -o milter_default_action=accept
> -o smtpd_milters=inet:127.0.0.1:10030
> The milter is running and listening at port 10030 (I can connect with
> The postfix instance does receive and handle the mail (I can see that
> in the log).
> But postfix makes no connection to port 10030.
> I normally have an iptables rule that allows only user "amavis" to
> connect to port 10030, but I've tried removing that restriction and
> that did not help.
> Have I completely misunderstood something?