On Wed, 6 Aug 2003, Nigel Metheringham wrote:
> > Again, I have seen no ill effects from this message, just wanted to bring it
> > to Phillip's attention in case it affected anybody else.
I believe I have done all I can in Exim 4.20 with regard to this. If the
message is still happening, it may be from some library that Exim is
calling.
> My theory is that the module loader is somehow triggering this,
... which fits in with my (more general) theory. To track down the
problem, I suppose something like an strace will be needed.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
