On Wed, 29 Dec 2021, Jeremy Harris via Exim-users wrote:
> On 29/12/2021 09:45, Cyborg via Exim-users wrote:
>> It was about changing environments while in queue.
>
> There's two parts to this.
>
> 1) (The bit Evgeny spoke to):
> Once a message is frozen, that frozen state is on the message
> in the spool. The configuration is not relevant.
>
> 2) The Exim configuration file is not reloaded automatically by
> the exim daemon if it changes. It is documented that SIGHUP
> should be used (the traditional Unix method) to tell it to do
> so.
>
> Child processes of the daemon (message acceptance, transport,
> queue-runner processes) get the config loaded by the daemon.
>
> Individually started exim processes, eg. for command-line mail
> submission, will get the then-current state of the config file.
>
> "Configuration" here is not only the config file itself but also
> any files pulled in via .include directives. It does *not* cover
> the content of external files or databases used via lookups in
> the configuration, nor results from external processes.
(When) are lookups cached between delivery attempts ?
--
Andrew C. Aitchison Kendal, UK
andrew@???
