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:
On Sun, May 14, 2006 at 07:38:09PM +0100, Justin Mason wrote:
> > Nope, at least not wrt sa-update. The files are supposed to be processed
> > during SA installation, but sa-update doesn't do that and simply installs
> > the files. We should probably change that at some point.
>
> interesting --
Theo Van Dinter writes:
> On Sat, May 13, 2006 at 06:17:37PM -0700, Bart Schaefer wrote:
> > This immediately jumped out at me:
> >
> > -report_contact [EMAIL PROTECTED]
> > +report_contact @@CONTACT_ADDRESS@@
> >
> > Obviously the LOCAL_RULES_DIR reference in the comment is of little
> > conseq
That empty .../rules000300010001 directory will prevent Spamassassin from
working so removing it if it be empty is a needed fix. I did so manually.
Enabling port 8090 allowed sa_update to work correctly so all's well that ends
well.
I would want to place spamassassin.org IP into my DMZ rather t
On Sat, May 13, 2006 at 06:17:37PM -0700, Bart Schaefer wrote:
> This immediately jumped out at me:
>
> -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
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
