Nico Schottelius via Postfix-users:
> [Two-layer architecture: large IPv6-only Kubernetes clusters with
> external connectivity, plus smaller dual-stack, transit-only,
> Kubernetes clusters that gateway from/to external IPv4.]
> So long story short, each mx instance will be a container, in total we
> have planned 8 of them (4 edge nodes, 4 inside the clusters) and for
> that we can use our home brewed containers, but I think that others would
> also profit from official postfix containers that can just be
> trustworthily downloaded and used.
I may be missing something, but how would you customize a 'standard'
Postfix container image for these widely-different use cases? If
it involves another Dockerfile to add another layer and "RUN postconf"
commands, why not prepend your preferred Dockerfile commands already?
FROM debian:12.7
RUN apt-get update && apt-get install -y postfix && rm -rf
/var/lib/apt/lists/*
RUN postconf maillog_file=/dev/stdout
RUN ...postconf commands for other settings...
One reason to NOT distribute Postfix binaries is to avoid delays
when a security bug needs to be fixed. When binary packages are
built by distro maintainers, the workload is distributed, instad
of making the Postfix project a bottleneck.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
