Hi all,
I'm having a problem running spamassassin on Debian stable
(version 3.1). All of my spam (and I get about 5-10/day) is being marked
as ham with a score of 0.1. In the few days so far that I've ran it,
nothing has been marked as spam except for the test spam file which came
with
Hi Gary,
On Thu, 17 Aug 2006, Gary V wrote:
I would suggest installing a newer version from backports.org.
Thanks for the suggestion! I was not aware of backports.org at
all.
I could also go up to testing or *gasp* unstable, but I really
don't want to. I'm not a very good system
Hi Loren,
On Thu, 17 Aug 2006, Loren Wilton wrote:
For the main rules files you basically can't do this. It would theoreticaly
be possible, but it would take someone a lot of work to figure out what could
be done and then do it. It is far easier to update the whole package, which
will
Hi Michel,
On Fri, 18 Aug 2006, Michel Vaillancourt wrote:
Hi, Ray. I'm a Debian admin as well. However, my experience has
been that for Spamassassin in particular, don't use the .deb package.
Instead, run the CPAN install process; I have it set as a CRON job that
fires monthly. You'll
Hi Gary and others,
On Fri, 18 Aug 2006, Gary V wrote:
read this, it may validate your choice to stay stable:
http://www200.pair.com/mecham/spam/kernel.html
No, I'll definitely stay with stable. I have dabbled with testing
for a bit and it was fun learning about Debian and breaking it and
Hi Gary,
On Sun, 20 Aug 2006, Gary V wrote:
installs an initscript, so there are advantages. Mixing both methods is often
a bad thing however.
Ok, I'll definite refrain myself from doing that.
Are you using DCC/Razor2/Pyzor? Are they (along
with other network based tests) working?
Hi all,
Not pertaining to Debian (I think)... I was wondering in what
order are SA's settings read in. Is this correct:
1) /etc/spamassassin/init.pre
2) /etc/spamassassin/local.cf
3) /usr/share/spamassassin/*.cf
4) ~/.spamassassin/user_prefs
I also have a v310.pre and a v312.pre in
Hi Theo,
On Tue, 22 Aug 2006, Theo Van Dinter wrote:
1) /etc/spamassassin/init.pre
2) /etc/spamassassin/local.cf
3) /usr/share/spamassassin/*.cf
4) ~/.spamassassin/user_prefs
You could just read the spamassassin documentation which talks about all of
this. :)
But to answer your
Hi Bowie,
On Tue, 22 Aug 2006, Bowie Bailey wrote:
Raymond Wan wrote:
1) /etc/spamassassin/*.pre
2a) /var/lib/spamassassin/3.001003/updates_spamassassin_org/*.cf
(if the directory exists)
2b) /usr/share/spamassassin/*.cf
(if the previous directory doesn't exist)
3) /etc/spamassassin
Hi jdow,
On Tue, 22 Aug 2006, jdow wrote:
Never change /etc/share/spamassassin or the /var/lib/spamassassin
directories. Always change /etc/spamassassin/ or
/etc/mail/spamassassin
as appropriate for your install. You can override values set
earlier
with new ones. That change should probably
10 matches
Mail list logo
