Re: [exim] Tainted filename on DKIM signing in 4.94

2020-06-30 Thread Andy Smith via Exim-users
On 30-06-2020 16:22 +200, Jeremy Harris wrote: Something along the lines of dkim_private_key = \ ${lookup {${sender_address_domain}} \ dsearch,ret=full {/usr/local/etc/exim} \ {$value/dkim.private.key} {false}} -- Cheers, Jeremy Perfect, thanks very much Jeremy. -- ## List

Re: [exim] Tainted filename on DKIM signing in 4.94

2020-06-30 Thread Jeremy Harris via Exim-users
On 30/06/2020 13:59, Andy Smith via Exim-users wrote: > remote_smtp: > driver = smtp > dkim_domain = ${sender_address_domain} > dkim_selector = dkimxy > dkim_private_key = ${if exists \ > {/usr/local/etc/exim/${sender_address_domain}/dkim.private.key}\ >

[exim] Tainted filename on DKIM signing in 4.94

2020-06-30 Thread Andy Smith via Exim-users
Hi all, I have the same issue as reported here: https://lists.exim.org/lurker/message/20200606.112240.9ecf1e56.en.html But I'm too thick to undestand if the solution posted can be applied to my setup as it looks a bit different: remote_smtp: driver = smtp dkim_domain =

Re: [exim] Tainted filename on DKIM signing in 4.94

2020-06-06 Thread Max Kostikov via Exim-users
Ok, I found a solution (thanks, Jeremy!) in the previous thread. So now this configuration works fine begin transports SENDER_DOMAIN = ${if def:h_from:{${lc:${domain:${address:$h_from:{$qualify_domain}} KEYNAME = key${eval10:${substr{4}{2}{$tod_logfile}}%2}

[exim] Tainted filename on DKIM signing in 4.94

2020-06-06 Thread Max Kostikov via Exim-users
I found one more issue found after upgrade to latest Exim 4.94. Now this is related to outgoing messages DKIM signing. Jun 6 12:17:04 beta exim[11180]: 1jhVss-000ORe-45 Tainted filename '/usr/local/etc/exim/dkim/kostikov.co.key0' Jun 6 12:17:04 beta exim[11180]: 1jhVss-000ORe-45 unable to