https://bugs.exim.org/show_bug.cgi?id=2844
--- Comment #2 from Heiko Schlittermann <hs@???> ---
Changing the internal state of Exim via Perl should be considered intentional.
Perl is used here to *extend* Exim's functionality.
Regarding the ALRM handler: I think, it is Exim's duty to make sure that the
wanted handler is installed, prior to the call to alarm().
But - to improve stability, I can imagine a variant of the ${perl...} expansion
which forks a subprocess, to be on the safe side; at the expense of the
operational overhead.
For now I'll rework the places where we rely on our signal handler for ALRM
being installed.
--
You are receiving this mail because:
You are on the CC list for the bug.
