Re: [exim] Filter behavior when run from shell vs systemd

On Tue, Feb 13, 2018 at 4:15 AM, Marius Stan via Exim-users < exim-users@exim.org> wrote: > It might be selinux that's preventing access to that file. > try running setenforce 0 and see if the error goes away. > That was it! This is the third time selinux has had me scratching my head,

Re: [exim] Filter behavior when run from shell vs systemd

Gabe da Silveira via Exim-users (Di 13 Feb 2018 08:23:17 CET): > Hi all, > > I'm setting up exim to process emails based on the existence of a set of > centrally managed forward files. So I have an accept router configured as > follows: How did you test and what was the

Re: [exim] Filter behavior when run from shell vs systemd

Hello, It might be selinux that's preventing access to that file. try running setenforce 0 and see if the error goes away. Marius On 13/2/2018 9:23 AM, Gabe da Silveira via Exim-users wrote: Hi all, I'm setting up exim to process emails based on the existence of a set of centrally managed

[exim] Filter behavior when run from shell vs systemd

Hi all, I'm setting up exim to process emails based on the existence of a set of centrally managed forward files. So I have an accept router configured as follows: email_address_check: driver = accept condition = ${if exists{DOMAINS_DIR/$domain/$local_part/forward}} verify_only The