Hi, > After a bit of digging I found that sa-update had, in fact, updated my system > before I read this.
sa-update had also updated my system, and amavisd was restarted. However, the 72_active.cf in /usr/share/spamassassin somehow overrode the updated one from /var/lib/spamassassin/. Any idea how this could happen? It was necessary for me to manually update the 72_active.cf in /usr/share/spamassassin for this to work. I thought the processing order was: - /usr/share/spamassassin - /var/lib/spamassassin/3.002005/ - /etc/mail/spamassassin Is there something I can do to prevent this from happening again? How do I troubleshoot this? I believe the first two directories are consolidated in v3.3? Very frustrated, Alex
