On Mon, 14 May 2007, Murray S. Kucherawy wrote:
> I can concur with this as the likely solution. We ran into this with
> the libmilter we ship commercially when it's used on a newer Linux
> system against which it isn't certified.
To be more precise about what's going on here:
Sendmail, Inc. ships a libmilter with its commercial products which was
compiled against the glibc that was current at the time we shipped. In
between then and now apparently the symbol `__ctype_b' was renamed or
removed from newer versions of that library, but of course the shipped
libmilter still has references to it. Thus, if someone upgrades glibc,
that reference will no longer resolve and you get that error.
Recompiling libmilter against your current glibc is known to solve the
The only caveat here is that the current open source contains an enhanced
version of libmilter with new capabilities. Though we went to some
lengths to make the new stuff backward-compatible with the old stuff and
so far I've seen no problems, I must also admit I haven't tried all
possible combinations. Fortunately the open source for 8.13.8 is still
available for download if you do happen to run into any problems.