Exim complaining about tainted filename

Support
1

Problem Description

I’ve used the upgrade guide to go from Buster to Bullseye, and it all seemed to work, but now my aliases for exim aren’t working. Looks as though there’s no tainting handling in the router - is there a way to force Sympl to regenerate my mail configuration?

Any Error Messages

$ exim -bt <address>
...
LOG: MAIN PANIC
  Tainted filename for search '/srv/<domain>/config/aliases'
<Address> cannot be resolved at this time: failed to expand "${lookup{$local_part}lsearch{/srv/$domain/config/aliases}}": NULL

Environment

  • Sympl Version [9.0/10.0]: 11
  • Sympl Testing Version? [Yes/No] No
  • Debian Version [Buster/Stretch]: Bullseye
  • Hardware Type? [Dedicated/Virtual/Pi] VM
  • Hosted On? [name of hosting co] Digital Ocean
2

You’ll want to make sure that the sympl-mail package is up to date (it might not be if any changes were made), then run sudo make from /etc/exim4, which will rebuild the configuration.

Run sudo service exim4 restart to make sure exim is up to date, and you should be fine.

1 Like
3

Actually, I’d changed /etc/exim4/sympl.d/20-routers/25-vhost-aliases to have no $local_part on the home directories so that piping to executables works, so the .dpkg-dist config file was next to it. When I put that new file in place (plus my change to the home directories), it’s now working again.

Thanks.