Well, I haven't tracked down the bug specifically (I'm not actually an
exim user -- I was just tracking down a bug), but it appears that
libident is busted.
If ident on the connecting host returns a string that libident doesn't
understand, it appears to cause a SEGV.
For some reason at customer that I consult for, someone changed the
format of the identd string that is returned. (for the record, to:
%u,%U,%g,%G,%l,%L,%p,%c,%C using redhat 5.0) We were then unable to
connect to any EXIM running hosts, though all other mailers seem to work
fine. The versions I noticed varied from 1.8x to 2.0x. Once I
restored things to the default, it started working fine.
it's probably something somebody should look at.
darrell fuhriman
grumblesmurf consulting
--
*** Exim information can be found at
http://www.exim.org/ ***
