On 17/11/2022 19:10, Jeremy Harris via Exim-users wrote:
On 17/11/2022 16:36, Martin Clayton via Exim-users wrote:
So, sorry to be a tainted dummy, but I'm still left wondering how to
deal with this.
On 17/11/2022 16:36, Martin Clayton via Exim-users wrote:
So, sorry to be a tainted dummy, but I'm still left wondering how to deal with
this.
Look at your line:
{exists{VHOST_DIR/$domain_data/VHOST_CONFIG_DIR/blacklists/${extract{1}{=!&/}{$item}{$value}{$item
The filename there is
On 17/11/2022 15:12, Martin Clayton wrote:
On 17/11/2022 13:49, Jeremy Harris via Exim-users wrote:
On 16/11/2022 14:06, Martin Clayton via Exim-users wrote:
Removing the rhsbl services (i.e, $sender_address_domain) and all is
well.
[...]
On 16/11/2022 14:06, Martin Clayton via Exim-users wrote:
Removing the rhsbl services (i.e, $sender_address_domain) and all is well.
Looks like I guessed wrong. I'm wondering why this taint error isn't widespread
-- could it be $filter/exists specific?
Aha! (otherwise pronounced
Hi Jeremy
And thanks.
On 16/11/2022 22:16, Jeremy Harris via Exim-users wrote:
On 16/11/2022 14:06, Martin Clayton via Exim-users wrote:
Moving an old system to exim 4.94.2 I'm hitting a taint error with
$dnslist_domain. That's a bit surprising as it's 100% internally
defined -- there's
On 16/11/2022 14:06, Martin Clayton via Exim-users wrote:
Moving an old system to exim 4.94.2 I'm hitting a taint error with
$dnslist_domain. That's a bit surprising as it's 100% internally defined --
there's nothing the outside world can do to change its possible values.
I'm not immediately
