Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-24 Thread Jeremy Harris via Exim-users
On 24/06/2020 21:10, Patrick Porteous via Exim-users wrote: > I need to do a single key lookup on a file using a condition > statement in the correct de-tainted method? That is simplest (though any lookup would do; the point is to only use the tainted data for lookup keys). >  Prior to the

Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-24 Thread Patrick Porteous via Exim-users
On 2020-06-19 17:28, Jeremy Harris wrote: > On 19/06/2020 17:33, Patrick Porteous via Exim-users wrote: > > I'm having the same problem as Vladislav Georgiev after upgrading from > > 4.93.3 to 4.94-1.  After applying the update, I receive the following > > error when trying to send from any of my

Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-19 Thread Scott Ellis via Exim-users
Agreed - this was problematic for me, since I use .forward files for vmail users. I ended up solving it with: local_parts = ${lookup{${lc:$local_part}}dsearch{/var/mail/vmail}} require_files = +/var/mail/vmail/${local_part_data}/.forward file=

Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-19 Thread Jeremy Harris via Exim-users
On 19/06/2020 17:33, Patrick Porteous via Exim-users wrote: > I'm having the same problem as Vladislav Georgiev after upgrading from > 4.93.3 to 4.94-1.  After applying the update, I receive the following > error when trying to send from any of my domains.  Is this a bug or is > this something I

Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-19 Thread Patrick Porteous via Exim-users
Hello, I'm having the same problem as Vladislav Georgiev after upgrading from 4.93.3 to 4.94-1.  After applying the update, I receive the following error when trying to send from any of my domains.  Is this a bug or is this something I need to change in my config file for the new version? 

Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-19 Thread Kurt Jaeger via Exim-users
Hi! Jeremy wrote: > On 18/06/2020 13:43, Vladislav Georgiev | NS1.bg via Exim-users wrote: > > 2020-06-18 15:26:49 Tainted filename for search: '/etc/valiases/domain.com' > > Docs, concept index, de-tainting. Ah, thanks! I'm having the same problems with our config template and this looks like

Re: [exim] Tainted filename for search in Exim 4.94-1

2020-06-19 Thread Jeremy Harris via Exim-users
On 18/06/2020 13:43, Vladislav Georgiev | NS1.bg via Exim-users wrote: > 2020-06-18 15:26:49 Tainted filename for search: '/etc/valiases/domain.com' Docs, concept index, de-tainting. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at

[exim] Tainted filename for search in Exim 4.94-1

2020-06-19 Thread Vladislav Georgiev | NS1.bg via Exim-users
Hello, After the update to 4.94-1 the following forwarding router stopped working. It works in 4.93-3. userforward: driver = redirect allow_defer allow_fail domains = !$primary_hostname require_files = "+/etc/valiases/$domain" user =