I'm currently running exim 4.92 and having no taint issues, the moment I
update to 4.96 I get the below message in the logs and messages bounce.
I understand the tainting and not trusting 3rd party entered data but
I'm looking to fix this the right way, as google has presented a few
hacks and
On 24/07/2023 21:35, ael via Exim-users wrote:
On Mon, Jul 24, 2023 at 06:52:14PM +0200, Andreas Metzler via Exim-users wrote:
I am currently playing around with shipping a native systemd service
file for exim. Both openSUSE and archlinux provide nice starting
maybe very slightly off-topic.
ael via Exim-users (Mo 24 Jul 2023 22:35:28 CEST):
> On Mon, Jul 24, 2023 at 06:52:14PM +0200, Andreas Metzler via Exim-users
> wrote:
> >
> > I am currently playing around with shipping a native systemd service
> > file for exim. Both openSUSE and archlinux provide nice starting
>
> Offlist
On Mon, Jul 24, 2023 at 06:52:14PM +0200, Andreas Metzler via Exim-users wrote:
>
> I am currently playing around with shipping a native systemd service
> file for exim. Both openSUSE and archlinux provide nice starting
Offlist and maybe very slightly off-topic. Please also support sysvinit
or
Hi Andreas,
Andreas Metzler via Exim-users (Mo 24 Jul 2023
18:52:14 CEST):
> I am currently playing around with shipping a native systemd service
> file for exim. Both openSUSE and archlinux provide nice starting
> points. However, both[2] use Type=simple and reading the docs [1] I cannot
>
Hello,
I am currently playing around with shipping a native systemd service
file for exim. Both openSUSE and archlinux provide nice starting
points. However, both[2] use Type=simple and reading the docs [1] I cannot
understand why. - The error detection Type=exec offers and Type=simple
lacks
