You can likely just disable Geo::IP anyway. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6824
On 3/2/2018 1:06 AM, Maurizio Caloro wrote:
Hello together
I have little Geo::IP Trouble
Yesterday i have upgraded Spamassassin to 3.4.1 on debian_version 8.10
3.16.51-3+deb8u1
If i s
Hello together
I have little Geo::IP Trouble
Yesterday i have upgraded Spamassassin to 3.4.1 on debian_version 8.10
3.16.51-3+deb8u1
If i start me service this GeiIP Plugin have some error messages
Mar 02 06:44:15 Servername spamd[22306]: plugin: failed to parse plugin
(from @INC): Can't
On Tue, 2014-09-02 at 11:27 -0700, John Hardin wrote:
> On Tue, 2 Sep 2014, Chris wrote:
>
> >>> ifplugin Mail::SpamAssassin::Plugin::Pyzor
> >>> pyzor_path /usr/local/bin/pyzor
> >>> pyzor_options --homedir /home/chris/.pyzor
> >>> endif
> >
> > Would it be better if I changed the pyzor home dir
On Tue, 2 Sep 2014, Chris wrote:
ifplugin Mail::SpamAssassin::Plugin::Pyzor
pyzor_path /usr/local/bin/pyzor
pyzor_options --homedir /home/chris/.pyzor
endif
Would it be better if I changed the pyzor home dir
to /etc/mail/spamassassin and put the 'servers' file there?
In general that's a bett
On Tue, 2014-09-02 at 10:30 -0700, John Hardin wrote:
> On Tue, 2 Sep 2014, Chris wrote:
>
> > On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote:
> >> On Tue, 2 Sep 2014, Chris wrote:
> >>
> >>> On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote:
> On Mon, 1 Sep 2014, Chris wrote:
>
On Tue, 2 Sep 2014, Chris wrote:
On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote:
On Tue, 2 Sep 2014, Chris wrote:
On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote:
On Mon, 1 Sep 2014, Chris wrote:
System is Ubuntu 14.04 LTS I use fetchmail linked with procmail.
Permissions on
On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote:
> On Tue, 2 Sep 2014, Chris wrote:
>
> > On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote:
> >> On Mon, 1 Sep 2014, Chris wrote:
> >>
> >>> System is Ubuntu 14.04 LTS I use fetchmail linked with procmail.
> >>
> >>> Permissions on the ~/.py
On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote:
> On Tue, 2 Sep 2014, Chris wrote:
>
> > On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote:
> >> On Mon, 1 Sep 2014, Chris wrote:
> >>
> >>> System is Ubuntu 14.04 LTS I use fetchmail linked with procmail.
> >>
> >>> Permissions on the ~/.py
On Tue, 2 Sep 2014, Chris wrote:
On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote:
On Mon, 1 Sep 2014, Chris wrote:
System is Ubuntu 14.04 LTS I use fetchmail linked with procmail.
Permissions on the ~/.pyzor/servers files and directory is:
drwxr-x--- 2 chris chris 4096 Jul 17
On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote:
> On Mon, 1 Sep 2014, Chris wrote:
>
> > System is Ubuntu 14.04 LTS I use fetchmail linked with procmail.
>
> > Permissions on the ~/.pyzor/servers files and directory is:
> >
> > drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor
> > -r
>
> From: Chris
> Sent: Monday, September 01, 2014 10:25 PM
> To: users@spamassassin.apache.org
> Subject: Pyzor errors after upgrade
> System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Once
> mail is tossed to my othe
On Mon, 1 Sep 2014, Chris wrote:
System is Ubuntu 14.04 LTS I use fetchmail linked with procmail.
Permissions on the ~/.pyzor/servers files and directory is:
drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor
-rw-r- 1 chris chris 23 Jul 17 09:28 servers
Are you using this with sp
System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Once
mail is tossed to my other folders what's left is run through SA and
tossed either into my Inbox or my Spam folder. Yesterday morning I
upgraded to the newest version of Pyzor using this command:
pip install --upgrade pyzor
Sin
>> Den 2012-07-26 17:26, Nißl Reinhard skrev:
>>> reading the manuals, I've discovered that the AWL plugin isn't
>>> loaded anymore in spamassassin 3.3. Therefore I put the
>>> following lines into local.cf:
> On Fri, 27 Jul 2012 02:57:26 +0200 Benny Pedersen wrote:
>> oh no, do not put loadlugin
@spamassassin.apache.org
Betreff: Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Den 2012-07-26 17:26, Nißl Reinhard skrev:
> reading the manuals, I've discovered that the AWL plugin isn't loaded
> anymore in spamassassin 3.3. Therefore I put the following lines into
> local
Den 2012-07-27 03:14, RW skrev:
It seems inelegant, but is there a practical reason why this
shouldn't
be done. Some optional plugins such as Botnet and iXhash load
themselves
from their own .cf files.
did --lint not show it ?
On Fri, 27 Jul 2012 02:57:26 +0200
Benny Pedersen wrote:
> Den 2012-07-26 17:26, Nißl Reinhard skrev:
>
> > reading the manuals, I've discovered that the AWL plugin isn't
> > loaded anymore in spamassassin 3.3. Therefore I put the following
> > lines into local.cf:
>
> oh no, do not put loadlugi
Den 2012-07-26 17:26, Nißl Reinhard skrev:
reading the manuals, I've discovered that the AWL plugin isn't loaded
anymore in spamassassin 3.3. Therefore I put the following lines into
local.cf:
oh no, do not put loadlugin into *.cf files its wrong pr design, but so
much wiki and bad behavior s
Hi,
reading the manuals, I've discovered that the AWL plugin isn't loaded anymore
in spamassassin 3.3. Therefore I put the following lines into local.cf:
loadplugin Mail::SpamAssassin::Plugin::AWL
use_auto_whitelist 1
but the file auto-whitelist hasn't been touched since the upgrade from 3.1 to
Den 2012-03-18 14:44, Bernard Lheureux skrev:
I get ; <<>> DiG 9.2.4 <<>> -t txt 2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
But the DNS resolution works correctly, what does that mean ?
dig +trace 2.2.3.updates.spamassassin
18.3.2012 17:24, Bernard Lheureux kirjoitti:
> I use my own Bind9 DNS server which is running OK for a long time ago...
> And the 2 forwarders on this server are the 2 DNSes of my ISP what could
> be wrong ?
> Do you know if I could try to use public DNS as forwarders ?
> If yes, which ones ?
Try
On 03/18/2012 04:24 PM, Bernard Lheureux wrote:
I found why, that was related to my firewall, now everything is OK...
I simply had to disable the outgoing rules for DNS-OUT, because OUT is
allowed from all, and now all is OK
Thanks a lot to all of you !
On 03/18/2012 03:40 PM, Kevin A. McG
On 03/18/2012 03:40 PM, Kevin A. McGrail wrote:
Which ports should I open to ensure it works not only port 53 udp and
tcp ?
I'm assuming dig -t txt 2.3.3.updates.spamassassin.org @ns.erols.com
doesn't work for you either.
http://systembash.com/content/dns-server-firewall-open-ports/
Has
On 03/18/2012 02:59 PM, Kevin A. McGrail wrote:
Could this be related to a firewall rule that should be blocking it
?
Which ports should I open to ensure it works not only port 53 udp
and tcp ?
I get ; <<>
I get ; <<>> DiG 9.2.4 <<>> -t txt 2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
But the DNS resolution works correctly, what does that mean ?
It means DNS is not working correctly for you.
Here's an old ISP in my areas's DN
On 3/18/12 9:44 AM, Bernard Lheureux wrote:
I get ; <<>> DiG 9.2.4 <<>> -t txt 2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
But the DNS resolution works correctly, what does that mean ?
it means the DNS resolution isn't working
On 03/18/2012 02:33 PM, Kevin A. McGrail wrote:
On 3/18/2012 9:30 AM, Bernard Lheureux wrote:
On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to
work anymore since I've upgraded from 3.1.3 this seems to be related
to a DNS problem, but I can't find what I need to adapt to fix it
On 3/18/2012 9:30 AM, Bernard Lheureux wrote:
On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to
work anymore since I've upgraded from 3.1.3 this seems to be related
to a DNS problem, but I can't find what I need to adapt to fix it,
could you help me ?
Definitely sounds like D
On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to work
anymore since I've upgraded from 3.1.3 this seems to be related to a DNS
problem, but I can't find what I need to adapt to fix it, could you help
me ?
All that I get in DBG mode is:
Mar 18 14:27:47.241 [15822] dbg: channel:
On Tue, 4 Jan 2011 09:53:05 -0500
"Mike Gibson" wrote:
> I have recently inherited a web server with roughly 50 clients. Last
> week I started getting complaints about excessive amounts of junk
> mail being delivered.
spamassassin should be the last line of defence, you should be using
blockl
On 1/4/11 9:53 AM, Mike Gibson wrote:
I have recently inherited a web server with roughly 50 clients. Last
week I started getting complaints about excessive amounts of junk mail
being delivered. I upgraded my SpamAssassin Rules, Clam AV,
MailScanner, and SpamAssassin Engine (3.2.5 à 3.3.1),
I have recently inherited a web server with roughly 50 clients. Last week I
started getting complaints about excessive amounts of junk mail being
delivered. I upgraded my SpamAssassin Rules, Clam AV, MailScanner, and
SpamAssassin Engine (3.2.5 à 3.3.1), in that order. At first, this seemed to
r 0.001 each
(network tests enabled, no Bayes because it hasn't been trained
sufficient.)
So the overall score for that test message is 4.0 (rounded), exactly as
the log shows. Below the required_score threshold.
There is nothing wrong with your SA, it works just as expected.
> > Af
de]
Sent: Monday, August 23, 2010 7:40 PM
To: users@spamassassin.apache.org
Subject: Re: After upgrade the SA to 3.3.1, Mail scanning stop working partially
On Mon, 2010-08-23 at 08:16 +0530, Suhag Desai wrote:
> After upgrade the SpamAssassin Server version to 3.3.1, my mail
> scanning sto
On Mon, 2010-08-23 at 08:16 +0530, Suhag Desai wrote:
> After upgrade the SpamAssassin Server version to 3.3.1, my mail
> scanning stop working partially.
> Below is the setting for local.cf
>
> rewrite_header Subject SPAM
> report_safe 1
> required_sc
On Mon, 2010-08-23 at 07:16 -0500, Daniel McDonald wrote:
> > After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning
> > stop
> > working partially.
>
> This is a known bug.
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6419
It is rather
Still not clear from the link
-Original Message-
From: Daniel McDonald [mailto:dan.mcdon...@austinenergy.com]
Sent: Monday, August 23, 2010 5:46 PM
To: spamassassin
Subject: Re: After upgrade the SA to 3.3.1, Mail scanning stop working
partially
On 8/22/10 9:46 PM, "Suhag Desai&qu
On 8/22/10 9:46 PM, "Suhag Desai" wrote:
> After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning stop
> working partially.
>
This is a known bug.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6419
--
Daniel J McDonald, CCIE # 2495, CISSP # 78281
After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning
stop working partially.
Below is the test.cf file for checking whether SA working as per the given
score.
[r...@spd SPECS]# cd /etc/mail/spamassassin/
[r...@spd spamassassin]# cat test.cf
body
John Wilcock wrote on Thu, 28 Jan 2010 08:31:07 +0100:
> Presumably because you didn't run sa-update while the ruleset was
> missing from the update...
Hm, it *is* missing. But maybe not from the compiled rules, well.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.co
Le 27/01/2010 22:31, Kai Schaetzl a écrit :
John Wilcock wrote on Wed, 27 Jan 2010 17:43:56 +0100:
someone forgot to include 72_active.cf and 80_additional.cf in the
sa-update files.
Now I understand. However, why am I not getting these warnings with a
spamassassin --lint?
Presumably becaus
At 10:02 AM Wednesday, 1/27/2010, John Wilcock wrote -=>
Le 27/01/2010 18:57, Justin Mason a écrit :
Either someone forgot to delete all these rules, or (more likely IMO)
someone forgot to include 72_active.cf and 80_additional.cf in the sa-update
files.
I think you're dead right. It appears
John Wilcock wrote on Wed, 27 Jan 2010 17:43:56 +0100:
> someone forgot to include 72_active.cf and 80_additional.cf in the
> sa-update files.
Now I understand. However, why am I not getting these warnings with a
spamassassin --lint?
Kai
--
Get your web at Conactive Internet Services: http:/
g the same rules...
Jeff
-Original Message-
From: John Wilcock [mailto:j...@tradoc.fr]
Sent: Wednesday, January 27, 2010 10:03 AM
To: users@spamassassin.apache.org
Subject: Re: Fuzzyocr and rule errors after upgrade to 3.3.0
Le 27/01/2010 18:57, Justin Mason a écrit :
>> Either someon
On 1/27/2010 1:02 PM, John Wilcock wrote:
Le 27/01/2010 18:57, Justin Mason a écrit :
Either someone forgot to delete all these rules, or (more likely IMO)
someone forgot to include 72_active.cf and 80_additional.cf in the
sa-update
files.
I think you're dead right. It appears one of the bu
Le 27/01/2010 18:57, Justin Mason a écrit :
Either someone forgot to delete all these rules, or (more likely IMO)
someone forgot to include 72_active.cf and 80_additional.cf in the sa-update
files.
I think you're dead right. It appears one of the build scripts does
the wrong thing with the 3.3
On Wed, Jan 27, 2010 at 16:43, John Wilcock wrote:
> To state the problem again, 463 of the scores in the 50_scores.cf from 3.3.0
> sa-update refer to rules that used to be in 72_active.cf or 80_additional.cf
> in 3.2.5, but that neither of these two files are anywhere to be found in
> the 3.3.0 s
Le 27/01/2010 17:31, Kai Schaetzl a écrit :
John Wilcock wrote on Wed, 27 Jan 2010 15:27:17 +0100:
Me too... 463 of them, to be exact.
Do you want to say that you changed the score of 463 rules?
No, absolutely not. On this test box I haven't changed the scores of any
rules. There are absol
John Wilcock wrote on Wed, 27 Jan 2010 15:27:17 +0100:
> Me too... 463 of them, to be exact.
Do you want to say that you changed the score of 463 rules?
> However, these two files don't seem to exist in
> /var/lib/spamassassin/3.003000/updates_spamassassin_org/
Indeed, that's why you are getti
Le 27/01/2010 07:30, Ed Kasky a écrit :
Also - is anyone else getting a lot of "warning: score set for
non-existent rule" errors? I ran sa-update after teand continue to get
a slew of them...
Me too... 463 of them, to be exact.
With the exception of ACCESSDB where the score is set to 0 anyway
At 03:31 AM Wednesday, 1/27/2010, you wrote -=>
Ed Kasky wrote on Tue, 26 Jan 2010 22:30:23 -0800:
> FuzzyOcr
is it mentioned in the release notes? check back with the author of this
plugin if it is compatible with 3.3.0
> Also - is anyone else getting a lot of "warning: score set for
> non-ex
Ed Kasky wrote on Tue, 26 Jan 2010 22:30:23 -0800:
> FuzzyOcr
is it mentioned in the release notes? check back with the author of this
plugin if it is compatible with 3.3.0
> Also - is anyone else getting a lot of "warning: score set for
> non-existent rule" errors? I ran sa-update after tean
I just upgraded to 3.3.0 from 3.2.4 and get the following errors:
Jan 26 22:10:41.856 [32397] dbg: plugin: loading FuzzyOcr from
/etc/mail/spamassassin/FuzzyOcr.pm
Jan 26 22:10:42.038 [32397] warn: plugin: eval failed: Insecure
dependency in open while running with -T switch at
/etc/mail/spa
>On Tue, 26 Jan 2010 15:13:53 -0500, you wrote:
>Quoting "john ffitch" :
>
>> After attempting to move to Sa 3.3.0
>>
>> water:~ # /etc/cron.daily/sa-update
>> http: GET http://yerp.org/rules/stage/330903380.tar.gz request
>> failed: 404 Not Found: > 2.0//EN"> 404 Not Found
>> Not Found The
Quoting "john ffitch" :
After attempting to move to Sa 3.3.0
water:~ # /etc/cron.daily/sa-update
http: GET http://yerp.org/rules/stage/330903380.tar.gz request
failed: 404 Not Found: 2.0//EN"> 404 Not Found
Not Found The requested URL
/rules/stage/330903380.tar.gz was not found on this
> :0wf
> | /usr/bin/spamassassin
If there is even the slightest chance for a mail surge -- you probably
should add a lock file to that recipe. (Not to mention using spamc
again, which you appear to already have switched to. ;)
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\
> This seems to have been SELinux related. When I temporarily disable it,
> procmail is able to execute spamc and properly filter incoming messages.
> Thanks for the suggestion. This is a huge relief!
Ah, goodie. :) Please file a bug with RH against SELinux, for both
permission denied issues (
+,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i c<<=1:
> (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0;
> }}}
>
>
>
--
View this message in context:
http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21999350.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
d changing .procmailrc to use spamc, but I'm getting the same
"permission denied" error--i.e., it complains:
/bin/sh: /usr/bin/spamc: Permission denied
procmail: Program failure (126) of "/usr/bin/spamc"
--
View this message in context:
http://www.nabble.com/Spamassas
On Thu, 12 Feb 2009, nycsurf wrote:
Spamassassin correctly identifies the sample spam message when I do
spamassassin -D < /usr/share/doc/spamassassin-3.2.5/sample-spam.txt
Does /usr/bin/spamassassin behave properly from the command line?
{sorry for two messages}
procmail: Executing "/usr/b
> I recently upgraded to spamassassin-3.2.5-1.el5 using up2date and
> spamassassin is no longer filtering messages. Spamassassin correctly
> identifies the sample spam message when I do
[...]
> I've googled extensively to see if anyone else is having this problem and
> what possible solutions might
On Thu, 12 Feb 2009, nycsurf wrote:
Here is the relevant part of the log file for a sample email after turning
the verbose option on in .procmailrc:
procmail: Assigning "DROPPRIVS=yes"
procmail: Assuming identity of the recipient, VERBOSE=off
procmail: Assigning "PATH=/bin:/usr/bin:/usr/local/b
hat didn't
do anything.
I could only find one relevant posting with a similar error (located here
http://use.perl.org/~samtregar/journal/29278), but that doesn't sound like
my problem.
Thanks for any suggestions.
--
View this message in context:
http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21982029.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
On 02/04/08 16:33, [EMAIL PROTECTED] (Daryl C. W. O'Shea) wrote:
Christopher Bort wrote:
I have recently upgraded a SpamAssassin installation from
3.2.1 to 3.2.4. Since then URIBL hits have dropped to nearly
zero, where before there were several hundred per day.
Immediately after the upgrade,
Christopher Bort wrote:
> I have recently upgraded a SpamAssassin installation from 3.2.1 to
> 3.2.4. Since then URIBL hits have dropped to nearly zero, where before
> there were several hundred per day. Immediately after the upgrade, there
> were a handful of hits on URIBL_BLACK, but I have not
I have recently upgraded a SpamAssassin installation from 3.2.1 to
3.2.4. Since then URIBL hits have dropped to nearly zero, where before
there were several hundred per day. Immediately after the upgrade, there
were a handful of hits on URIBL_BLACK, but I have not seen any at all in
the last fe
now why it suddenly wants to load a
>> Win32 module?
>>
>> Jon
>>
>> Jon Armitage
>> System Administrator, 365 Media Group
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Perl-error-after-upgrade-to-3.2.3-tf4428549.html#a12942940
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
e way. Anyone know what we may
be experiencing?
GA
--
View this message in context:
http://www.nabble.com/Scan-Time-Problem-After-Upgrade-tf4429657.html#a12636664
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Hi;
I've seen this as well. I did a cpan upgrade and upgraded all perl
mods on a BSD, but not SA which was at 3.2.3. I think that may be due to
an issue with Sys:Syslog v0.20
SA seems to be working fine, as you say.
[96054] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains:
/u
Apologies if I am asking in the wrong place, since I can see that there are
several possible reasons.
We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box running Red
Hat 9. At the same time I used CPAN to upgrade any out-of-date perl modules.
Now, when SA starts, we get the foll
Frank Bures wrote:
After yesterday upgrade to 3.2.2 I am seeing these in the logs (upon spamd
restart):
spamd[19878]: rules: meta test FM__TIMES_2 has dependency
'FH_HOST_EQ_D_D_D_D' with a zero score
spamd[19878]: rules: meta test FM_SEX_HOST has dependency
'FH_HOST_EQ_D_D_D_D' wit
After yesterday upgrade to 3.2.2 I am seeing these in the logs (upon spamd
restart):
spamd[19878]: rules: meta test FM__TIMES_2 has dependency
'FH_HOST_EQ_D_D_D_D' with a zero score
spamd[19878]: rules: meta test FM_SEX_HOST has dependency
'FH_HOST_EQ_D_D_D_D' with a zero score
An
Hello!
> Hmm... I know you said standard Etch packages but those versions do
> not match the versions in Etch. They match the versions in Testing.
> Therefore I conclude that you are actually running Debian testing.
>
Didn't think so but obviously I must mess things up while experimenting
with
Stefan Hoth wrote:
> Since I upgraded my box to debian etch I have the same errors day by day.
>
> I'm running SpamAssassin version 3.2.0 running on Perl version 5.8.8
> (standard etch-package) with amavisd-new-2.4.2 (20060627) (also etch-pack).
Hmm... I know you said standard Etch packages but
Hello list!
I'm new here so please be nice to me :)
Since I upgraded my box to debian etch I have the same errors day by day.
I'm running SpamAssassin version 3.2.0 running on Perl version 5.8.8
(standard etch-package) with amavisd-new-2.4.2 (20060627) (also etch-pack).
There is a cronjob bund
On Thu, Jun 14, 2007 at 08:45:17AM -0400, Steven W. Orr wrote:
> I downloaded the tarfile and built an rpm. When I installed the rpm, the
> rpm was smart enough to restart SA. Should this postinst code in the rpm
> not also have rerun sa-compile before the restart? Seems logical to me.
The scrip
On Wednesday, Jun 13th 2007 at 17:14 -0400, quoth Rosenbaum, Larry M.:
=>> From: Steven W. Orr [mailto:[EMAIL PROTECTED]
=>>
=>> [EMAIL PROTECTED] ~]# rpm -Uvh
=>> /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm
=>> /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm
=>> Pre
> From: Steven W. Orr [mailto:[EMAIL PROTECTED]
>
> [EMAIL PROTECTED] ~]# rpm -Uvh
> /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm
> /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm
> Preparing...
###
> [100%]
> 1:perl-Mail-Spa
[EMAIL PROTECTED] ~]# rpm -Uvh
/usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm
/usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm
Preparing...### [100%]
1:perl-Mail-SpamAssassin
Ok, I saw the upgrade file. I've done quite a bit of modifications on
the local.cf file.
But I still get a bunch of errors when restarting spamd.
Any help ?
Le mardi 12 juin 2007 à 21:06 +0200, LESOUEF Emmanuel a écrit :
> Hello,
>
> After upgrading SA from 3.0 to 3.1, I get the attached logs
Hello,
After upgrading SA from 3.0 to 3.1, I get the attached logs when I restart
spamd.
This seems to be a configuration error. In fact, the local.cf file has been
wrote for the 3.0 version.
Can someone help me with it ?
Thanks.
--
Emmanuel Lesouef
DSI | CRBN
t : 0231069671
m : [EMAIL PROTE
Thanks a lot Justin. This is a big relief. I was worried that SA may
fall apart on me today and this makes me feel a lot better.
Thank you!
Joe
Justin Mason wrote:
hi Joe -- yep, it is. In fact you should probably use the G_ flag
for calling a method in void context, can't recall which one
hi Joe -- yep, it is. In fact you should probably use the G_ flag
for calling a method in void context, can't recall which one that is ;)
--j.
Joe Flowers writes:
> Thanks Justin. I am embedding Perl inside a C program, so I hope this is
> still true. It used to return a non-NULL or at least t
Thanks Justin. I am embedding Perl inside a C program, so I hope this is
still true. It used to return a non-NULL or at least the following call
used to always return a "count" of 1 and not 0 like it is now after the
SA upgrade.
count = perl_call_method("Mail::SpamAssassin::PerMsgStatus::finis
hi Joe --
just ignore the return value of finish() -- it's a void method.
(note how it doesn't mention a return value in its POD doc ;)
--j.
Joe Flowers writes:
> Hello Everyone,
>
> I'm getting a weird error message that I have never gotten before over
> several versions of SA. I just upgrad
Hello Everyone,
I'm getting a weird error message that I have never gotten before over
several versions of SA. I just upgraded from "SpamAssassin version 3.1.7
running on Perl version 5.8.8" to "SpamAssassin version 3.2.0 running on
Perl version 5.8.8". Now, my calls to
Mail::SpamAssassin::Pe
Hi.
Gentoo
Spamassassin 3.1.8-r1
After upgrading from 3.1.3 to 3.1.8-r1 I found many warnings in logs
(see attachment) which fill up all space on my /var/log partition.
This warings is equal to warnings from "spamd -D".
Also I attach versions of my perl modules. May be it will be usefull.
Any
On Thu, Feb 15, 2007 at 03:53:29PM -0300, Raul Dias wrote:
> open (LEARN, "| /usr/bin/sa-learn -u $user --" . $OPTIONS->{type})
> which reflects for: "/usr/bin/sa-learn -u raul --spam" for example.
Hey look at that, piping in has the issue if no target is specified.
For the moment, add in "-" as a
On Thu, 2007-02-15 at 12:45 -0500, Theo Van Dinter wrote:
> On Thu, Feb 15, 2007 at 02:15:47PM -0300, Raul Dias wrote:
> > archive-iterator: invalid (undef) format in target list, 2
> > at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ArchiveIterator.pm
> > line 727, line 1.
> >
> > Just for t
On Thu, Feb 15, 2007 at 02:15:47PM -0300, Raul Dias wrote:
> archive-iterator: invalid (undef) format in target list, 2
> at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ArchiveIterator.pm
> line 727, line 1.
>
> Just for the record, the sa-learn has messages (one eache time) fed thru
> stdin
Just upgraded to 3.1.8.
Everything seems fine except that I get this line when running sa-learn:
archive-iterator: invalid (undef) format in target list, 2
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ArchiveIterator.pm
line 727, line 1.
sa-learn seems to be working fine though.
Just fo
Leon,
> 451 4.5.0 Error in processing, id=15039-05, mime_decode-1 FAILED:
> Can't locate object method "max_parts"
> via package "MIME::Parser" at /usr/sbin/amavisd line 5933.
Your version of MIME::Parser (i.e. MIME-Tools) is too old,
use 5.420.
Mark
On Wed, Nov 22, 2006 at 05:33:39PM +0200, Leon Kolchinsky wrote:
> Nov 22 14:25:39 mail postfix/smtp[15132]: 23CBE1CA24: to=< [EMAIL PROTECTED]
> >, orig_to=< [EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1], delay=25,
> status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in
> process
You should upgrade your MIME::Parser as well.
You are probably using a very old one, where it does not support of
"max_parts" as stated in the error log!
/Micke
Leon Kolchinsky wrote:
Example of maillog errors:
Nov 22 14:25:39 mail postfix/smtp[15132]: 23CBE1CA24: to=< [EMAIL PROTECTED] >, o
Hello All,
I'm running SLES9 with the following versions:
spamassassin-2.64-3.2
perl-spamassassin-2.64-3.2
amavisd-new-20030616p9-3.6
I know I probably stuck with perl5.8.3 because SLES9 don't have the newer :(
I've installed new versions of SA and amavis (see below) with the following
packets
Mark Merchant wrote:
i just upgraded spamassassin 3.1.0 to 3.1.7 ( Rh9 ) and seem to be
getting an extra line-break in the Content-Type header.
outlook apparently sees the semi-colon as a LF and doesn't render
the email correctly. evolution sees it as a semi colon and every-
thing works fine.
a
i just upgraded spamassassin 3.1.0 to 3.1.7 ( Rh9 ) and seem to be
getting an extra line-break in the Content-Type header.
outlook apparently sees the semi-colon as a LF and doesn't render
the email correctly. evolution sees it as a semi colon and every-
thing works fine.
always in the Content-Ty
On Fri, Oct 20, 2006 at 02:42:09PM -0400, Brian S. Meehan wrote:
> When you say blow them away, are there folders besides the below ones that
> should be removed?
>
> /etc/mail/spamassassin
I'd save these files, since they're your local configs. Copy them back
appropriately after the install.
>
When you say blow them away, are there folders besides the below ones that
should be removed?
/etc/mail/spamassassin
/usr/share/spamassassin
Thank you,
Brian
On Fri, October 20, 2006 14:35, Theo Van Dinter wrote:
> On Fri, Oct 20, 2006 at 02:30:14PM -0400, Brian S. Meehan wrote:
>> Oct 20 14:10
On Fri, Oct 20, 2006 at 02:30:14PM -0400, Brian S. Meehan wrote:
> Oct 20 14:10:20 mail spamd[5776]: configuration file
> "/usr/share/spamassassin/20_net_tests.cf" requires version 3.001007 of
> SpamAssassin, but this is code ve
> rsion 3.04. Maybe you need to use the -C switch, or remove the o
1 - 100 of 289 matches
Mail list logo
