Ken,
I already started to prepare a section about the motivation of tainting
and about how to de-taint.
Maybe I can share it before we include it into the official docs.
(As it keeps biting me too ;)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
Hi!
> The concept "de-tainting" appears in the index, but not in the manual.
Yes, but: Jeremy can't do all the heavy lifting all by himself.
We need to help him. Write docs etc.
--
p...@opsec.eu+49 171 3101372Now what ?
--
## List details at
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=
Hi, Jeremy. This problem keeps coming up and you answer
From: Jeremy Harris via Exim-users
Date: Fri, 19 Jun 2020 13:29:00 +0100
Docs, concept index, de-tainting.
The concept "de-tainting" appears in the index, but not in the manual.
This index entry gets you to some useful
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
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?
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
On 18/06/2020 13:20, Felix Schwarz via Exim-users wrote:
> sqlite_dbfile = /path/to/user.db
>
> domainlist local_domains = sqlite;select DISTINCT domain from users where
> domain='${quote_sqlite:$domain}' and is_enabled=1;
Two problems.
- the syntax only applies for
single-key lookup
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
On Fri, 19 Jun 2020 10:04:09 +0100 Jeremy Harris via Exim-users wrote:
> On 19/06/2020 09:48, Frank Elsner via Exim-users wrote:
> > Ok, it is not a repro of the initial case.
> > But it is not nomal as it delays the massege.
> >
> > But can you explain this please
> >
> > 22937 tick
Hey,
(sorry for starting a new thread - I was not subscribed previously so I could
not reply in the old thread).
After upgrading to 4.94 I got the ominous error message:
Tainted filename for search: 'select'
As far as I understood "sqlite_dbfile" should solve the problem for me but it
does
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 =
On 19/06/2020 09:48, Frank Elsner via Exim-users wrote:
> Ok, it is not a repro of the initial case.
> But it is not nomal as it delays the massege.
>
> But can you explain this please
>
> 22937 tick check: 1592491915.156500 1592491548.933500
> 22937 waiting 366.223500 sec
Exim
On Thu, 18 Jun 2020 17:02:40 +0100 Jeremy Harris via Exim-users wrote:
> On 18/06/2020 15:58, Frank Elsner via Exim-users wrote:
> > I could reproduce the problem with exim-4.94 which occures after the system
> > came up after suspend:
> >
> > 22937 Process 22937 is handling incoming connection
14 matches
Mail list logo
