Thanks for your quick response!
I did the full lenny (from etch) upgrade yesterday, which got
sendmail, clamav-milter, spamass-milter, spamassassin, and
libmilter. When I posted, I had not upgraded dk-filter and
dkim-filter, since I had originally built them from source so
aptitude didn't get 'em (I *HAD* rebuilt them against the new
libmilter yesterday, though; prior to that they wouldn't work
at all). But I noticed that both of those have Debian packages
now, so I went ahead and switched over to the Debian versions
of them this morning, removing my old versions and configurations.
Unfortunately, I'm still getting the same result. I've rebooted
and restarted several times, and again, all the filters *seem* to
be working ok, just producing the error message.
For the sake of documentation, here are the version numbers
reported by all the various pieces:
libmilter.so points to libmilter.so.1.0.1 (apt:8.14.3-5)
spamd/SpamAssassin: 3.2.5 (apt: 3.2.5-2)
sendmail: 8.14.3 (apt: 8.14.3-5)
clamav-milter: 0.94.2 (apt: 0.94.dfsg)
spamass-milter: 0.3.1 (apt: 0.3.1-8)
dk-filter: 1.0.0 (apt: 1.0.0.dfsg)
dkim-filter: 2.6.0 (apt: 2.6.0.dfsg)
On Tue, 17 Feb 2009, Dan Ragle wrote:
Since upgrading to Lenny today, I've been inundated with
logfile messages of this variety:
Feb 16 23:30:41 adam sendmail[25756]: NOQUEUE: Milter (dkim): to error
state
Feb 16 23:30:41 adam sendmail[25756]: NOQUEUE: Milter (dk): to error
state
Feb 16 23:30:41 adam sendmail[25756]: NOQUEUE: Milter (spamassassin): to
error state
Feb 16 23:30:41 adam sendmail[25756]: NOQUEUE: Milter (clamav): to error
state
So libmilter got upgraded - did sendmail *and* the four milters?
This error sounds like not everything is upto snuff wrt the
sendmail <-> milter API
Or is it likely a matter of not restarting sendmail and the various
milters after updating the library ? - hrm, that shouldn't be needed
since the library is versioned and running apps should use whatever
library they were built against
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
