Had the same problem - although until I saw your posting I didn't
know it was the same problem.
Fixed it by taking out "SpamAssassin Local State Dir" in
MailScanner.conf.
I don't really know how this will affect things, but at lease Spam is
now being detected again.
David Minard.
Ph: 0247 360 155
Fax: 0247 360 770
School of Computing & Mathematics
Building Y - Penrith Campus (Kingswood)
Locked bag 1797
Penrith South DC
NSW 1797
[Sometimes waking up just isn't worth the insult of the day to come.]
On 14/05/2006, at 11:17 AM, Bart Schaefer wrote:
As sa-update appears to have been successful, I decided to diff the
downloaded files against the installed 3.1.1 ruleset before blindly
restarting spamd.
This immediately jumped out at me:
==================================================
--- /usr/share/spamassassin/10_misc.cf 2006-03-15
14:02:25.000000000 -0800
+++ /var/lib/spamassassin/3.001001/updates_spamassassin_org/10_misc.cf
2006-05-13 17:49:04.000000000 -0700
@@ -1,7 +1,7 @@
# SpamAssassin basic config file
#
# Please don't modify this file as your changes will be overwritten
with
-# the next update. Use /etc/mail/spamassassin/local.cf instead.
+# the next update. Use @@LOCAL_RULES_DIR@@/local.cf instead.
# See 'perldoc Mail::SpamAssassin::Conf' for details.
#
# <@LICENSE>
@@ -42,7 +42,7 @@
# A 'contact address' users should contact for more info. (replaces
# _CONTACTADDRESS_ above if present)
-report_contact [EMAIL PROTECTED]
+report_contact @@CONTACT_ADDRESS@@
==================================================
Obviously the LOCAL_RULES_DIR reference in the comment is of little
consequence, but I suspect the incorrect report_contact address is a
problem.
I also notice that the require_version line has been deleted from
quite a few .cf files.
Is there some sort of local postprocessing that was supposed to
happen, but did not?
Scanned by SCIT E-Mail Gateway http://www.cit.uws.edu.au
Scanned by SCIT E-Mail Gateway http://www.cit.uws.edu.au
