Re: [exim] DKIM and debian buster...

On 07/07/2020 00:01, Mike Tubby via Exim-users wrote:
> remote_smtp:
>         driver = smtp
>         dkim_domain = ${lc:${domain:$h_from:}}
>         dkim_selector = ${lookup mysql{SELECT selector FROM dkim WHERE
> domain='${quote_mysql:${dkim_domain}}' AND active=1}{$value}{false}}
>         dkim_canon = ${lookup mysql{SELECT canon FROM dkim WHERE
> domain='${quote_mysql:${dkim_domain}}' AND active=1}{$value}{false}}
>         dkim_hash = ${lookup mysql{SELECT hash FROM dkim WHERE
> domain='${quote_mysql:${dkim_domain}}' AND active=1}{$value}{false}}
>         dkim_private_key = ${lookup mysql{SELECT private_key FROM dkim
> WHERE domain='${quote_mysql:${dkim_domain}}' AND active=1}{$value}{false}}
>         dkim_strict = 0

I'd be tempted to roll all those queries together, and then extract
the items from the one result string - just to cut down on DB load.

Unfortunately set= isn't available in a transport; only in a router
or acl. You could hack it via an acl expansion, or you could
just rely on the lookup caching.

I probably should add set= in transports, now I've seen this.
--
Cheers,
Jeremy