On 06/06/2020 19:29, Jeremy Harris via Exim-users wrote:
> On 05/06/2020 20:02, Laura Williamson via Exim-users wrote:
>> dkim_selector = ${lookup sqlite {/usr/exim/dkimcertificates select
>> selector from dkimcerts where domain='$sender_address_domain'}{$value}}
>
> As I told Max, one of:
>
>
On 05/06/2020 20:02, Laura Williamson via Exim-users wrote:
> dkim_selector = ${lookup sqlite {/usr/exim/dkimcertificates select
> selector from dkimcerts where domain='$sender_address_domain'}{$value}}
As I told Max, one of:
- use the sqlite_dbfile main option
- use separate tables within one
Hi folks
I have an issue that only appears when using 4.94. I use this to lookup
dkim information for signing outgoing emails
dkim_selector = ${lookup sqlite {/usr/exim/dkimcertificates select
selector from dkimcerts where domain='$sender_address_domain'}{$value}}
dkim_private_key = ${lo
I've got same issue and the recommended change doesn't solve my issues
unfortunately. Rollback to 4.93 solves the problem.
Den 06/06/2020 kl. 00:39 skrev Jeremy Harris via Exim-users:
On 06/06/2020 00:24, Max Kostikov via Exim-users wrote:
2020-06-06 01:02:28 Tainted filename for search:
'/v
Jeremy Harris via Exim-users писал 2020-06-06 13:54:
On 06/06/2020 10:57, Max Kostikov via Exim-users wrote:
And what if more than one SQLite database used with Exim?
One of:
...
- wait for the next release
It suits me best.
Please do not forget about it.
--
With best regards,
Max Kostikov
On 06/06/2020 10:57, Max Kostikov via Exim-users wrote:
> And what if more than one SQLite database used with Exim?
One of:
- Use separate tables within one sqlite db rather than multiple db files
- ensure your sqlite lookup strings do not contain tainted data
(look in the Concept Index for de-
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}
DKIM
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 open
Thanks!
And what if more than one SQLite database used with Exim?
E.g. I use one DB for users and domains and separate DB for antispam
data.
Jeremy Harris via Exim-users писал 2020-06-06 01:39:
On 06/06/2020 00:24, Max Kostikov via Exim-users wrote:
2020-06-06 01:02:28 Tainted filename for se