On 11/21/2014 12:32 PM, Bowie Bailey wrote:
> bayes_path is considered to be an administrator setting and is not
> allowed to be specified in user_prefs.
Ah, that's what I get for grepping through the man page instead of paging
through in order. Thanks very much.
On 11/21/2014 2:51 PM, Starchy Grant wrote:
Hello,
I'm working on a limited test of a global bayes databases on Debian
Wheezy with spamassassin 3.3.2, and trying to set bayes_path in my
user_prefs file. When I add the line
bayes_path /var/spamassassin/bayes_db/bayes
I see the following in the
On 12/6/2011 12:55 PM, Christian Gregoire wrote:
What happens if you put those lines into a local.cf or similar configuration
file rather than a user preference?
Doesn't look like it's taken into account. The rule is not triggered
Then you are putting it in the wrong place or the rule isn't hi
>What happens if you put those lines into a local.cf or similar configuration
>file rather than a user preference?
Doesn't look like it's taken into account. The rule is not triggered
>What are your command line parameters for spamd and spamc?
/usr/bin/spamd --socketpath=/tmp/spamassassin.sock
On 12/6/2011 10:28 AM, Christian Gregoire wrote:
Hi,
With the following prefs file (taken from
http://wiki.apache.org/spamassassin/WritingRules) :
header LOCAL_DEMONSTRATION_SUBJECT Subject =~ /\btest\b/i
score LOCAL_DEMONSTRATION_SUBJECT 0.1
I get the below error :
Dec 6 14:39:
Jeffrey,
> I'm running SpamAssassin version 3.3.1, running on Perl version 5.10.0.
> I'm seeing a lot of errors similar to:
>
> config: failed to parse line, skipping, in
> "/tmp/.spamassassin13924v0B7j5tmp/60_adsp_override_dkim.cf":
> adsp_override ebay.com
>
> during the daily cron run. (the
Drew Burchett wrote:
> I made this same mistake yesterday.
Turned out that I hadn’t enabled razor in v310.pre.
Thanks very much for the reply Drew!
I found that the line loading the Razor plug-in in v310.pre
was commented out:
# Razor2 - perform Razor2 message checks.
#
# Ra
From: "analyzer" <[EMAIL PROTECTED]>
Matt Kettler schrieb:
At 06:51 AM 12/30/2005, analyzer wrote:
hanks four your help. My provider had updated the system. Now
spamassassin 3.0.8 is install and it run fine.
3.0.8?
Sry, my mistake 3.0.3.
Provider screwed up again. 3.0.4 is the one tha
From: "analyzer" <[EMAIL PROTECTED]>
Matt Kettler schrieb:
At 06:51 AM 12/30/2005, analyzer wrote:
hanks four your help. My provider had updated the system. Now
spamassassin 3.0.8 is install and it run fine.
3.0.8?
Sry, my mistake 3.0.3.
Provider screwed up again. 3.0.4 is the one tha
Matt Kettler schrieb:
At 06:51 AM 12/30/2005, analyzer wrote:
hanks four your help. My provider had updated the system. Now
spamassassin 3.0.8 is install and it run fine.
3.0.8?
Sry, my mistake 3.0.3.
At 06:51 AM 12/30/2005, analyzer wrote:
hanks four your help. My provider had updated the system. Now spamassassin
3.0.8 is install and it run fine.
3.0.8?
Gary V schrieb:
You might try to manually install a little older version of Net::DNS
cd /usr/local/src
wget http://www.net-dns.org/download/Net-DNS-0.48.tar.gz
tar xzvf Net-DNS-0.48.tar.gz
cd Net-DNS-0.48
perl Makefile.PL
Do you want to enable these tests? [y] n
make
make test
make install
You might try to manually install a little older version of Net::DNS
cd /usr/local/src
wget http://www.net-dns.org/download/Net-DNS-0.48.tar.gz
tar xzvf Net-DNS-0.48.tar.gz
cd Net-DNS-0.48
perl Makefile.PL
Do you want to enable these tests? [y] n
make
make test
make install
___
It would be nice if someone actually could tell us what the deal is with
IPv6 on Debian Sarge.
Sorry I am getting off topic here, but:
Looks like if you do a fresh install with 'linux26' (to get the 2.6 kernel),
IPv6 is enabled. I personally have had issues (segfaults) after I to
upgraded fr
Thanks for your help. I can't install IO::Socket::INET6.
The same thing happened on my (newer) Debian system. If you use IPv6, this
may be serious
and we'll need to find out why. If, like me, you only use IPv4, just
'force install IO::Socket::INET6'.
I think the big problem is it looks lik
Keith Dunnett schrieb:
analyzer wrote:
Thanks for your help. I can't install IO::Socket::INET6.
Here the output:
The same thing happened on my (newer) Debian system. If you use IPv6,
this may be serious
and we'll need to find out why. If, like me, you only use IPv4, just
'force install
analyzer wrote:
Thanks for your help. I can't install IO::Socket::INET6.
Here the output:
The same thing happened on my (newer) Debian system. If you use IPv6,
this may be serious
and we'll need to find out why. If, like me, you only use IPv4, just
'force install IO::Socket::INET6'.
Reg
Keith Dunnett schrieb:
analyzer wrote:
Package: libnet-dns-perl
Versions:
0.19-0.1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)
That isn't what we want, and it doesn't look like Debian woody offers
a suitable version, so
analyzer wrote:
Package: libnet-dns-perl
Versions:
0.19-0.1(/var/lib/apt/lists/ftp.tiscali.de_pub_debian_debian_dists_woody_main_binary-i386_Packages)(/var/lib/dpkg/status)
That isn't what we want, and it doesn't look like Debian woody offers a
suitable version, so we'll do
everything via
Keith Dunnett schrieb:
analyzer wrote
Yes, i had updated the libnet-dns-perl. apt-get and cpan say its up
to date.
Spamassassin doesn't - so you haven't *successfully* updated it. Paste
the full output of
apt-cache showpkg libnet-dns-perl
then go into CPAN and run:
test Net::DNS
analyzer wrote
Yes, i had updated the libnet-dns-perl. apt-get and cpan say its up to
date.
Spamassassin doesn't - so you haven't *successfully* updated it. Paste
the full output of
apt-cache showpkg libnet-dns-perl
then go into CPAN and run:
test Net::DNS
Again, paste the full out
Keith Dunnett schrieb:
Net::DNS ist up to date.
Spamassassin say:
[7841] warn: dns: Net::DNS version is 0.12, but need 0.34 at
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
Did you update it as described in previous e-mail?
apt-get update
apt-get install libnet-dns-perl
Net::DNS ist up to date.
Spamassassin say:
[7841] warn: dns: Net::DNS version is 0.12, but need 0.34 at
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
Did you update it as described in previous e-mail?
apt-get update
apt-get install libnet-dns-perl
There are more errors:
Keith Dunnett schrieb:
There is a problem with Net::DNS. How can I update this pachages to
the newest version.
spamassassin --lint
[15694] warn: dns: Net::DNS version is 0.12, but need 0.34 at
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
First try:
# apt-get update
#
Keith Dunnett schrieb:
analyzer wrote:
server:~# spamassassin -V
SpamAssassin version 2.20
My provider have configured the system. Perhaps there is anything false.
Perhaps you have multiple copies of SpamAssassin on the system? Try
'whereis spamassassin'.
As Jonn said, these errors are
At 12:49 AM 12/27/2005, Matt Kettler wrote:
server:~# spamassassin -V
SpamAssassin version 2.20
My provider have configured the system. Perhaps there is anything false.
And spamassassin --lint works?? That's quite strange indeed.
Nevermind.. I re-read your original message. you never used
At 01:25 PM 12/26/2005, analyzer wrote:
Matt Kettler schrieb:
At 10:18 AM 12/26/2005, analyzer wrote:
Sry, my mistake. I use version 2.20. I can't update to the newest
version, beacause the confixx compatibility.
You are not using SA 2.20.. SA didn't even support the --lint command
until
analyzer wrote:
server:~# spamassassin -V
SpamAssassin version 2.20
My provider have configured the system. Perhaps there is anything false.
Perhaps you have multiple copies of SpamAssassin on the system? Try
'whereis spamassassin'.
As Jonn said, these errors are likely to be the product o
Matt Kettler schrieb:
At 10:18 AM 12/26/2005, analyzer wrote:
Sry, my mistake. I use version 2.20. I can't update to the newest
version, beacause the confixx compatibility.
You are not using SA 2.20.. SA didn't even support the --lint command
until 2.40. The fact that you could run a --lin
At 10:18 AM 12/26/2005, analyzer wrote:
Sry, my mistake. I use version 2.20. I can't update to the newest version,
beacause the confixx compatibility.
You are not using SA 2.20.. SA didn't even support the --lint command until
2.40. The fact that you could run a --lint clearly indicates you're
Sry, my mistake. I use version 2.20. I can't update to the newest
version, beacause the confixx compatibility.
Karsten
Jonn R Taylor schrieb:
SA 3.1.0 uses differand config option. If you look at the docs you
will see this. I found this when I upgraded from 2.x version.
Jonn
On Mon, 26 De
31 matches
Mail list logo
