Hello Marc,
Am 09.01.22 um 17:15 schrieb Marc Haber:
The research of this error message leads to a big discussion without an
solution here:
Did the research not lead you to the documentation in the package, such
as /usr/share/doc/exim4-base/NEWS.Debian.gz, which explains the issue?
No - sorry - why should someone search and find important informations in other
package News?
Please feel free to re-open this bug if reading NEWS.Debian doesn't
help.
The 'trick' with $local_part_data did not help and only leads to more other
problems ...
But your hint rescues the day - thank you very much!
For other desperate exim users - add to the exim4.conf configuration:
.ifdef _OPT_MAIN_ALLOW_INSECURE_TAINTED_DATA
allow_insecure_tainted_data = yes
.endif
When there is the time the other hints will be used for a correction to the new
configuration challenge.
You already closed the bug that is only "new features" - thanks
Best regards
karsten
