Wietse Venema via Postfix-users wrote in
<4xvs4j0h5qzj...@spike.porcupine.org>:
|Nico Schottelius via Postfix-users:
|> Marvin Renich via Postfix-users writes:
|>> [...]
|>> Do you expect the postfix devs to release containers for every popular
|>> combination of distribution and containeriz
* Nico Schottelius:
> It's the opposite and let me put it into clear, logic terms:
Oh, do try. ;-)
> I need a postfix container [0]
> I can easily build a postfix container [1]
> Others might start using my postfix container due to the lack of an
> official postfix container [2]
If (!) you publ
Nico Schottelius via Postfix-users:
>
> Marvin Renich via Postfix-users writes:
> > [...]
> > Do you expect the postfix devs to release containers for every popular
> > combination of distribution and containerization technology (Docker,
> > kubernetes, LXC, OpenVZ, etc.)? Even picking one distr
Nico Schottelius:
> > That is NOT an official image. The web page even has a very clear
> > disclaimer:
> >
> > Note that these images come with absolutely no warranty or support.
> >
> > In other words, don't use these images for mission-critical applications,
> > such as providing an email se
On Fri, Oct 18, 2024, at 09:31, Bill Cole via Postfix-users wrote:
>
> I suspect that this thread has already taken more time & effort than it would
> take for one sysadmin with k8s expertise to build a working Postfix container
> for their own use. I'm sure that it has taken more time than just
* Marvin Renich via Postfix-users [241018 08:14]:
> My apologies! I had explicitly set Reply-To, and expected the mailing
> list software to _not_ replace it.
Okay, it seems that the list software _adds_ the original sender to the
existing Reply-To header. So if I don't set Reply-To, it just ha
On 2024-10-18 at 05:58:16 UTC-0400 (Fri, 18 Oct 2024 11:58:16 +0200)
Emmanuel Seyman via Postfix-users
is rumored to have said:
* Nico Schottelius via Postfix-users [18/10/2024 10:55] :
- Others might start using my postfix container due to the lack of an
official postfix container [2]
Th
Hey Emmanuel,
Emmanuel Seyman via Postfix-users writes:
> * Nico Schottelius via Postfix-users [18/10/2024 10:55] :
>>
>> - Others might start using my postfix container due to the lack of an
>> official postfix container [2]
>> - To avoid that, my recommendation is that the postfix project p
* Nico Schottelius [18/10/2024 20:39] :
>
> In the best case scenario you get one
> hit with a lot of favorites/stars/whatever and an indication that the
> image is official. That means as a user it is trustworthy and you can
> run your workload with it.
The fact t
* Steffen Nurpmeso via Postfix-users [241017 14:23]:
> postfix-users@postfix.org wrote in
> :
> |[Please do not CC me! That goes against long-standing mailing list \
> |etiquette.]
>
> How about adding a Mail-Followup-To: header then?
> Even though it never became a standard, that is even mor
* Nico Schottelius via Postfix-users [18/10/2024 10:55] :
>
> - Others might start using my postfix container due to the lack of an
> official postfix container [2]
> - To avoid that, my recommendation is that the postfix project provides a
> container itself
This is the part I don't get. Why i
Marvin Renich via Postfix-users writes:
> [...]
> Do you expect the postfix devs to release containers for every popular
> combination of distribution and containerization technology (Docker,
> kubernetes, LXC, OpenVZ, etc.)? Even picking one distribution still
> leaves too many containers.
No,
Ralph Seichter via Postfix-users writes:
> * Nico Schottelius via Postfix-users:
>
>> As mentioned before, I/we can volunteer to building the image(s) and
>> rebuilding them on a new release, if the added workload is a concern.
>
> Why do I get the feeling that you promote the idea of an "officia
Wietse Venema via Postfix-users writes:
> Nico Schottelius via Postfix-users:
>>
>> Marvin,
>>
>> Marvin Renich via Postfix-users writes:
>> > [...]
>> >> - Rerun a docker build & docker push as soon as the underlying OS's
>> >> update their package repository
>> >> - Update the Dockerfile o
postfix-users@postfix.org wrote in
:
|[Please do not CC me! That goes against long-standing mailing list \
|etiquette.]
How about adding a Mail-Followup-To: header then?
Even though it never became a standard, that is even more so
a pity today with that current "x via y" rewriting that places
Nico Schottelius via Postfix-users:
>
> Marvin,
>
> Marvin Renich via Postfix-users writes:
> > [...]
> >> - Rerun a docker build & docker push as soon as the underlying OS's
> >> update their package repository
> >> - Update the Dockerfile once the depending operating system updates
> >> t
[Please do not CC me! That goes against long-standing mailing list etiquette.]
* Nico Schottelius via Postfix-users [241017 09:31]:
>
> Marvin,
>
> Marvin Renich via Postfix-users writes:
> > [...]
> >> - Rerun a docker build & docker push as soon as the underlying OS's
> >> update their p
* Nico Schottelius via Postfix-users:
> As mentioned before, I/we can volunteer to building the image(s) and
> rebuilding them on a new release, if the added workload is a concern.
Why do I get the feeling that you promote the idea of an "official"
container image and your role in it because you
Marvin,
Marvin Renich via Postfix-users writes:
> [...]
>> - Rerun a docker build & docker push as soon as the underlying OS's
>> update their package repository
>> - Update the Dockerfile once the depending operating system updates
>> their image (i.e. The debian based postfix image could
* Nico Schottelius via Postfix-users [241016 20:10]:
> Package maintainers are usually split into two different approaches:
>
> - a) Some built containers directly from *their* source, only using the
> inside distribution as a help to build their own binaries.
>
> advantages:
> - always
Good morning,
Wietse Venema via Postfix-users writes:
> 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 l
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 w
Nico Schottelius:
>
> Salut Wietse,
>
> Wietse Venema via Postfix-users writes:>
> > [...]
> > If there are 'common' container use cases, then I suppose that
> > Postfix could distrtibute example Dockerfiles for that.
>
> While the use cases are likely to differ, a lot of "common" software
> su
Good evening Bill,
Bill Cole via Postfix-users writes:
> On 2024-10-15 at 22:43:51 UTC-0400 (Wed, 16 Oct 2024 11:43:51 +0900)
> Nico Schottelius via Postfix-users
> is rumored to have said:
>
> how do you currently run postfix in containers?
>
> I don't (and neither do most Postfix users) bec
On 2024-10-15 at 22:43:51 UTC-0400 (Wed, 16 Oct 2024 11:43:51 +0900)
Nico Schottelius via Postfix-users
is rumored to have said:
how do you currently run postfix in containers?
I don't (and neither do most Postfix users) because a robust MTA
installation is a terrible fit for a Docker contai
Salut Wietse,
Wietse Venema via Postfix-users writes:>
> [...]
> If there are 'common' container use cases, then I suppose that
> Postfix could distrtibute example Dockerfiles for that.
While the use cases are likely to differ, a lot of "common" software
such as nginx provide minimal containers
Nico Schottelius via Postfix-users:
Checking application/pgp-signature: FAILURE
-- Start of PGP signed section.
>
> Hello fellow postfix users,
>
> how do you currently run postfix in containers? As far as I can see
> there is no official image out there, just a number of people who
> published
27 matches
Mail list logo
