Re: [exim] Callouts that don't immediately work

On Tue, Mar 29, 2011 at 6:29 AM, Jaap Winius <jwinius@???> wrote:
> Frustrated, I backed off and thought about it for a while. Then I ran some
> more tests a few hours later... which all completed without any problems. As
> if nothing had ever been the matter.
> Is this normal behavior? Any explanations?

At least on CentOS, the init script that stops and (re)starts exim,
just stops the listening processes, allowing any existing sessions to
continue to completion. If you tell it to stop a second time, it will
kill all processes (i.e. those that were in the process of delivering
and those that were in the process of receiving). Is it possible that
when you restarted exim that there were some processes left which were
in the process of delivery/reception that were using the old config?
I would expect though, that new inbound connections would fork from
the (now restarted) listening process, which would use the new config,
so my query is likely not relevant to your case. But it's the only
thing that pops into my head that would work... or... for some
reason, the listening process did not get restarted at the time you
thought it did.

--
Regards...      Todd
"It is the nature of the human species to reject what is true but
unpleasant and to embrace what is obviously false but comforting."
"You might be a skeptic if you have pedantically argued the topic of pedantry."