On a recent new system I installed only amavisd-new and clamav in a
first step, _not_ including spamassassin. The result was that amavisd
refused to start due to execution errors. Once I installed also
Spamassassin, then amavisd would start as expected without any
changes applied to configurations.

Judging from the most recent control file, the implicit dependeny
on Spamassassin should still be present.

Mats Erik Andersson schrieb am Wednesday, den 24. March 2010:
This should be fixed in newer versions (amavis shouldn't bail out if
spamassassin isn't installed). I will test this later.

Thanks for reporting
Alex

Mats Erik Andersson schrieb am Wednesday, den 24. March 2010:
This should be fixed in newer versions (amavis shouldn't bail out if
spamassassin isn't installed). I will test this later.

Thanks for reporting
Alex

Not sure if this should be a separate ticket or not...

The amavisd-new cron.d entry calls:

/usr/sbin/amavisd-new-cronjob sa-sync

This script calls /usr/bin/sa-learn. It doesn't appear to check if
sa-learn is installed or not.

And, if spamassassin is installed, but is configured with bayes turned
off, the script returns:


This happens even if sa is not enabled in amavis.

Ideally, the cron job could check to ensure that both sa is installed
and amavis is configured to do spam checking (and, if possible, if bayes
is turned on).

Or - maybe the installation of the cron job should be dependent on a
dpkg configuration question?

jamie