[exim] Two nested 'dsearch' to avoid tainted data ?

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Olaf Hopp (SCC)
Date:  
À: 'Mailing List'
Sujet: [exim] Two nested 'dsearch' to avoid tainted data ?
Dear all,

I am migrating from exim 4.92 to 4.94, so the tainted data "problem" comes into the focus.
I have a transport:

uservacation:
driver = autoreply
file = /etc/exim4/autoreply/${domain}/${local_part}.msg
[...]

After fiddling around with dsearch I ended up with two nested dsearch'es.
One for the directory with the domainname and finally one for the file ${local_part}.msg
within that directory. So I have a line as follows:

file = ${lookup {${local_part}.msg} dsearch,ret=full {${lookup{$domain} dsearch,ret=full,filter=directory {/etc/exim4/autoreply}}/}}

This works as expected. But is there a more elegant solution ?

Greetings, Olaf

--
Karlsruher Institut für Technologie (KIT)
Steinbuch Centre for Computing (SCC)

Dipl.-Geophys. Olaf Hopp

Zirkel 2
Gebäude 20.21, Raum 316
76131 Karlsruhe

Telefon: +49 721 608-48009
E-Mail: Olaf.Hopp@???
Web: www.scc.kit.edu

Sitz der Körperschaft:
Kaiserstraße 12, 76131 Karlsruhe

KIT - Die Forschungsuniversität in der Helmholtz-Gemeinschaft