Hi,
On 2022-04-04 17:01, Wietse Venema wrote:
Wietse Venema:
christ...@degenkolb.net:
> Everything runs normal as long as the mymilter container is online.
> If I stop mymilter postfix refuses to accept smtp connections with for
> example the following errors.
..
> As far as I can tell the network-alias gets removed from dockers
> internal DNS server on container stop which triggers the postfix fatal
> error.
> However shouldn't a failed DNS request also evoke the default policy of
> "accept" for this milter?
> Is this a postfix bug or am I missing something? Can I somehow add "DNS
> not Working" to the "it's Ok"-List for this milter?
I guess Postfix pre-dates containers that come and go at any
point in time. Does this patch work for you?
That patch as posted is for recent Postfix versions. Below is a version
that should with Postfix 3.4.
First, thanks for the response.
Well this is a little bit unexpected. I wasn't expecting a source patch.
I can test if the patch solves the "DNS not working" problem but it
might take some time till I can report back if it works.
Currently I just use the prebuild container and have to do the whole
"build a container with a patched postfix" thingy after I have a clue as
how to manage this. A cursory look tells me I have to do some
apt-source, quilt and apt-build wizardry.
How high is the possibility this will, on success, land in a future
release of postfix so I one day I can stop the "build postfix in a
docker container from source"?
Christian
