Wietse Venema via Postfix-users:
> Michael Tokarev via Postfix-users:
> > 20.12.2024 00:22, Wietse Venema via Postfix-users wrote:
> > > Michael Tokarev via Postfix-users:
> > >> Here's a little change for the `postfix' command I'd love to have
> > >> in Debian, - to assist its 25 years history of running postfix
> > >> chrooted and to have an easier alternative, one way or the other.
> > >>
> > >> It's just a proof of concept, but it is easy enough.  Not yet written
> > >> in a style of other code in this script (like using logging functions
> > >> which is a good idea in this case for sure.
> > >>
> > >> The "idea" is to have
> > >>
> > >>      postfix chroot [-n] on|off
> > >>        - to run services chrooted (on) or non-chrooted (off)
> > >>          (-n to show what would be done instead of actual modifications)
> > >>      postfix chroot query
> > >>        - to query and return the current status (on|off|mixed).
> > > 
> > > Apart from possible BASH-isms, this could work on non-LINUX systems.
> > > But without a way to manage the content of the chroot tree, it will
> > > be useful mainly to "view" or "turn off" chroot.
> > 
> > I'm mostly asking about the approach, if it is okay with you if some
> > distribution is to modify code like this, adding a custom subcommand.
> 
> Please seriously consder why we want to run Postfix chrooted for the masses.
> It makes the system a lot easier to break and a lot harder to repair.

Mainrainers have always addes stuff to Postfix that wasn't up-streamed.
That said, if something is generally useful then I have adopted it
in the past. This one will be difficukt to generalize, though.

        Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to