Postings by Jesper Dybdal

The compatibility_level mechanism

The compatibility_level mechanism is an excellent and very well designed
idea.  But I must have misunderstood something - or there is an error.

Around christmas I upgraded from postfix 2.11 to 3.1.6 (Debian 9).

I let the system run with compatibility_level=0 for a couple of months.

I then checked the log file for occurrences of "using
backwards-compatible", which I thought would tell me where I depended on
obsolete default settings.

Apart from some "chroot=y" warnings (which I fixed), there were no such

So I recently set compatibility_level to 2.

Very soon after that I saw t

Why is milter not called?

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

However, the milter is not called at all.

The postfix instance in question is defined as: inet n  -       y       -       -       smtpd
        -o syslog_name=postfix/10028
        -o smtpd_authorized_xforward_hosts=
        -o smtpd_client_restrictions=
        -o smtpd_helo_restrictions=

Putting all outgoing mail on hold?

Is there a simple way to put all outgoing mail (i.e., everything that
would normally be processed by the default "smtp" instance) into the
HOLD queue?

The reason I would like to do that is that the IP address on which I run
my little server is about to change, and I would like outgoing mail to
be held until I am sure that the new address has a proper reverse DNS
and is not in any problematic DNSBLs. I could also just block outgoing
port 25 with a firewall rule, but using HOLD will give me better
control: I can then release individual mails if I want to.

VERP uses the recipient name after virtual_regexp rewriting

I have just installed a mailing list manager (Mailman) for use with my
Postfix installation (which has just been upgraded to 2.5.5).