Pedro, ideas are great but patches are essential. If you are interested in
said feature, please consider submitting a patch to achieve it. Especially
because I can guarantee you that very few people will put any cycles on a
3.3.X release issue.
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraisin
>Given your findings, I kinda suspect *all* of the tflags=multiple rules
>are misbehaving from time to time under 3.3.1 - the compiled code may be
>getting into an infinite loop somehow if the number if *real* hits on the
>rule exceeds some value - I note there were 17 hits on "your business
On Fri, 20 Apr 2018, Bill Cole wrote:
On 20 Apr 2018, at 14:50 (-0400), John Hardin wrote:
Given your findings, I kinda suspect *all* of the tflags=multiple rules are
misbehaving from time to time under 3.3.1 - the compiled code may be
getting into an infinite loop somehow if the number if *r
On 20 Apr 2018, at 14:50 (-0400), John Hardin wrote:
Given your findings, I kinda suspect *all* of the tflags=multiple
rules are misbehaving from time to time under 3.3.1 - the compiled
code may be getting into an infinite loop somehow if the number if
*real* hits on the rule exceeds some valu
On Fri, 20 Apr 2018, Chris Conn wrote:
Yeah, because 3.4.x implements maxhits.
So, should I disable the __GENERATE_LEADS family for < 3.4.0? I suspect it
would be prudent, but I am surprised the other tflags=multiple rules aren't
also problematic in the same manner...
Hello,
I don`t t
Yeah, because 3.4.x implements maxhits.
So, should I disable the __GENERATE_LEADS family for < 3.4.0? I
suspect it would be prudent, but I am surprised the other
tflags=multiple rules aren't also problematic in the same manner...
Hello,
I don`t think I am in a position to comment on whe
On Fri, 20 Apr 2018, Chris Conn wrote:
WTF? If tflags=multiple is supported at all, it should behave properly
(i.e. not hitting over and over on the *same bit of text*).
maxhits was implemented after 3.3.1; is it possible that there are just a
*lot* of instances of "your business" in that t
WTF? If tflags=multiple is supported at all, it should behave properly
(i.e. not hitting over and over on the *same bit of text*).
maxhits was implemented after 3.3.1; is it possible that there are
just a *lot* of instances of "your business" in that test message, and
it's simply hitting all
On Fri, 20 Apr 2018, Chris Conn wrote:
On 4/18/2018 10:32 AM, Benny Pedersen wrote:
Chris Conn skrev den 2018-04-18 16:00:
this is a relatively old install, SA 3.3.1 on Centos6 (stock RPMs)
maybe solved in centos7 ?
I believe I found the issue. On my Centos6 boxes with SA 3.3.1 (the
mai
On 4/18/2018 10:32 AM, Benny Pedersen wrote:
Chris Conn skrev den 2018-04-18 16:00:
this is a relatively old install, SA 3.3.1 on Centos6 (stock RPMs)
maybe solved in centos7 ?
i do not use precompiled problems
Hello,
I believe I found the issue. On my Centos6 boxes with SA 3.3.1 (the
maybe solved in centos7 ?
i do not use precompiled problems
Hello,
I guess I will soon find out. Not using bayes or anything, most plugins
are disabled actually. Just trying to figure out which one is
misbehaving, as spamd grows to 4Gb of resident memory usage, at 100%
CPU, and eventual
Chris Conn skrev den 2018-04-18 16:00:
this is a relatively old install, SA 3.3.1 on Centos6 (stock RPMs)
maybe solved in centos7 ?
i do not use precompiled problems
On 18/04/2018 16:08, David Jones wrote:
I too have been seeing a very high number of SA timeouts via
MailScanner the past week and would like to know how to troubleshoot
these timeouts. I have never been able to catch problem messages in
the act to figure out what is causing them.
FWIW, w
On 04/18/2018 09:00 AM, Chris Conn wrote:
Hello,
We recently started having problems on a few servers with spamd
processes starting to hog RAM (3G++ per child) and we are noting some
timeouts in the logs. as well, we are seeing this msg
Apr 18 08:48:24 spamd[2451]: plugin: eval failed
Hello,
We recently started having problems on a few servers with spamd
processes starting to hog RAM (3G++ per child) and we are noting some
timeouts in the logs. as well, we are seeing this msg
Apr 18 08:48:24 spamd[2451]: plugin: eval failed: __alarm__ignore__(156)
Apr 18 08:58:25 spamd
/redis.pid
logfile /var/log/redis.log
#loglevel notice
loglevel verbose
databases 16
save 600 1
dir /var/lib/redis
dbfilename dump.rdb
maxclients 1024
timeout 30
I see this error:
abr 10 08:18:56.229 [8978] dbg: bayes: _open_db(not yet connected)
plugin: eval failed: bayes: Redis failed: Error
/redis.pid
logfile /var/log/redis.log
#loglevel notice
loglevel verbose
databases 16
save 600 1
dir /var/lib/redis
dbfilename dump.rdb
maxclients 1024
timeout 30
I see this error:
abr 10 08:18:56.229 [8978] dbg: bayes: _open_db(not yet connected)
plugin: eval failed: bayes: Redis failed: Error
On 07.06.08 16:58, Michał Jęczalik wrote:
> To: Matus UHLAR - fantomas <[EMAIL PROTECTED]>
> cc: users@spamassassin.apache.org
And, please, do NOT send me private copies. I do not need nor want them.
If I wouldn't read this list, I would not answer your message because I
wouldn't know about it.
> On Sat, 7 Jun 2008, Matus UHLAR - fantomas wrote:
>
> >>But spamassassin tries to find it in 5.8.8. And that's probably the
> >>reason. How to tell perl (or spamassassin?) to include
> >>/usr/share/perl/5.10.0 in @INC as well? Now this variable has only 5.8.8
> >>paths. I've created a symlink 5.
On Sat, 7 Jun 2008, Jari Fredriksson wrote:
Aaargh, I guess somebody at debian developers team did
not coordinated perl and spamassassin packages somehow,
but don't know why and how to fix it. ;(
$ perl --version
This is perl, v5.8.8 built for i486-linux-gnu-thread-multi
Copyright 1987-2006,
only 5.8.8 paths.
>>> I've created a symlink 5.8.8 -> 5.10.0, maybe it will
>>> work as a temporary solution.
>>
>> Haven't you upgraded perl w/o reinstalling spamassassin?
>> Or, doesn't spamassassin use old version of libperl?
>
>
>
-> 5.10.0, maybe it will work as a
temporary solution.
Haven't you upgraded perl w/o reinstalling spamassassin? Or, doesn't
spamassassin use old version of libperl?
OK, now I have a symlink and there's another problem:
plugin: eval failed: Undefined subroutine utf8::SWASHGET call
On Sat, 7 Jun 2008, Matus UHLAR - fantomas wrote:
But spamassassin tries to find it in 5.8.8. And that's probably the
reason. How to tell perl (or spamassassin?) to include
/usr/share/perl/5.10.0 in @INC as well? Now this variable has only 5.8.8
paths. I've created a symlink 5.8.8 -> 5.10.0, may
> On Sat, 7 Jun 2008, Matus UHLAR - fantomas wrote:
>
> >% locate utf8.pm
> >/usr/share/perl/5.8.8/DBM_Filter/utf8.pm
> >/usr/share/perl/5.8.8/utf8.pm
> >% dlocate /usr/share/perl/5.8.8/utf8.pm
> >perl-base: /usr/share/perl/5.8.8/utf8.pm
> >
> >seems to be from perl, at least from debian's perl pa
On Sat, 7 Jun 2008, Matus UHLAR - fantomas wrote:
% locate utf8.pm
/usr/share/perl/5.8.8/DBM_Filter/utf8.pm
/usr/share/perl/5.8.8/utf8.pm
% dlocate /usr/share/perl/5.8.8/utf8.pm
perl-base: /usr/share/perl/5.8.8/utf8.pm
seems to be from perl, at least from debian's perl package... Which perl
ver
> > spamassassin 3.2.4-2, debian package. I'm getting
> > occasional errors about missing utf8.pl file:
> >
> > plugin: eval failed: Can't locate utf8.pm in @INC (@INC
> > contains: /usr/share/perl5 /etc/perl
> > /usr/local/lib/perl/5.8.8 /usr/loca
> spamassassin 3.2.4-2, debian package. I'm getting
> occasional errors about missing utf8.pl file:
>
> plugin: eval failed: Can't locate utf8.pm in @INC (@INC
> contains: /usr/share/perl5 /etc/perl
> /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8
> /usr/l
spamassassin 3.2.4-2, debian package. I'm getting occasional errors about
missing utf8.pl file:
plugin: eval failed: Can't locate utf8.pm in @INC (@INC contains:
/usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/lib/perl/5.8
/usr/
> -Original Message-
> From: Jean-Paul Natola [mailto:[EMAIL PROTECTED]
> Sent: Friday, 14 March 2008 12:09 p.m.
> To: SpamAssassin
> Subject: Plugin eval failed
>
> Hi all,
>
> I upgraded to sa 3.2.4
>
> And I've been restarting spamd every 15
At 18:38 13-03-2008, Jean-Paul Natola wrote:
1.We have a sitewide config
2.Startup parameters are
command_args="-d --min-children=2 --max-children=10 --min-spare=2
--max-spare=3 --max-conn-per-child=100 -r ${pidfile}"
3.I do not scan messages over 250 k
4.We process roughly 5k messages daily
Jean-Paul Natola wrote:
> > 1) Reduce max-children to 8 or less. (Use 6 if you can).
> When I go lower, I get "server has reaacehd max children, consider
> raising it"
It is normal to receive this message from time to time. It just means
that all of your spamd processes are busy. If you have en
hen , if
clean
and spam free it goes right to our exchange server
-Original Message-
From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 8:44 PM
Cc: SpamAssassin
Subject: Re: Plugin eval failed
On 13/03/200
not "hold" any mail , it process it, then , if clean
and spam free it goes right to our exchange server
-Original Message-
From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 8:44 PM
Cc: SpamAssassin
Subject: Re: Plugin eval failed
On 13
day, March 13, 2008 8:44 PM
Cc: SpamAssassin
Subject: Re: Plugin eval failed
On 13/03/2008 8:02 PM, Jean-Paul Natola wrote:
> What other info should I post?
The output of vmstat while this is happening.
A definition of "constantly". Every message, some % of messages? For
some common
On 13/03/2008 8:02 PM, Jean-Paul Natola wrote:
> What other info should I post?
The output of vmstat while this is happening.
A definition of "constantly". Every message, some % of messages? For
some common size of messages? Whether it happens when scanning mail for
a subset of users or for al
What other info should I post?
-Original Message-
From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 7:16 PM
To: Jean-Paul Natola
Cc: SpamAssassin
Subject: Re: Plugin eval failed
On 13/03/2008 7:08 PM, Jean-Paul Natola wrote:
> Hi all,
>
>
On 13/03/2008 7:08 PM, Jean-Paul Natola wrote:
> Hi all,
>
> I upgraded to sa 3.2.4
>
> And I've been restarting spamd every 15 minutes just to keep mail coming in,
>
> This is what is constantly coming up in the maillog
>
>
> plugin: eval failed: child p
Hi all,
I upgraded to sa 3.2.4
And I've been restarting spamd every 15 minutes just to keep mail coming in,
This is what is constantly coming up in the maillog
plugin: eval failed: child processing timeout at /usr/local/bin/spamd line
1259.
Any help would be appreciated
Running
Fr
] info: spamd: got connection over
/tmp/spamd.sock
Fri Feb 22 17:19:07 2008 [13045] info: spamd: processing message
<[EMAIL PROTECTED]> for simscan:1013
Fri Feb 22 17:19:07 2008 [13045] warn: plugin: eval failed: can\'t resolve
\"localhost\" to address at /usr/local/lib/perl/5
39 matches
Mail list logo
