On Tue, Aug 19, 2008 at 06:38:07PM -0300, Henrique de Moraes Holschuh wrote: > On Mon, 18 Aug 2008, Debian Bug Tracking System wrote: > > After lots of testing, I succeeded in fixing the problem by removing the > > contents of /var/lib/spamassassin and re-running sa-update and > > sa-compile. It's a pity that even on the highest logging level, there > > was no hint that something was wrong with the contents of this > > directory. > > Do you have spamassassin rule compilation ENABLED? (this is not something > in amavisd-new, but rather spamassassin itself). If it IS enabled, can you > verify if you had a PERL upgrade around the time things broke?
Yes, I use sa-compile on this system and it's run on a daily basis by /etc/cron.daily/spamassassin if there are updates with sa-update. The only perl related update which happened at that time is libnet-ssleay-perl 1.35-1. Maybe the real cause of this problem happened already earlier, but only became visible once amavisd-new was restarted. This machine was updated from Etch to Lenny about three weeks ago, which included the perl 5.8 to 5.10 upgrade. But as amavisd-new was updated to 2.6.0-2 at that time, I suppose it was already restarted at that time too. Perl itself was not updated since. -- Frederik Himpe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
