Matt Kettler writes:
Daryl C. W. O'Shea wrote:
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time the answer is stop using blacklist.cf and
Justin Mason wrote:
Matt, any chance you could open a bz feature request for this?
Done.. also added to it so there's now 3 warning level options.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5710
--j.
jdow wrote:
From: Matt Kettler [EMAIL PROTECTED]
Sent: Friday, 2007, October 26 20:19
I dono, I think that having some --lint warnings generated when the
overall config is really absurdly large seems useful for this kind of
problem in general. A basic um, dude, that's a lot of config, are
Matt Kettler wrote:
Daniel J McDonald wrote:
On Fri, 2007-10-26 at 08:16 -0400, Matt Kettler wrote:
Justin Mason wrote:
What else can we do?
Add code to generate a lint warning any time a .cf file over 1mb is read
unless a config option is
But people don't read logs, or they would know... I'd suggest die-ing
instead.
On Fri, 26 Oct 2007, Duane Hill wrote:
Why not make it a configurable option in local.cf defaulting to
die. That way for those of us who create custom .cf files that
have the system resources can do so
From: Matt Kettler [EMAIL PROTECTED]
Sent: Friday, 2007, October 26 20:19
Daryl C. W. O'Shea wrote:
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time
Quoting Matt Kettler [EMAIL PROTECTED]:
[18696] dbg: config: read file /etc/mail/spamassassin/blacklist-uri.cf
[18696] dbg: config: read file /etc/mail/spamassassin/blacklist.cf
Ditch blacklist and blacklist-uri. These two are well known ways to
kill spamassassin on all but the absolute
Matt Kettler writes:
I also use RulesDuJour daily to get updated cf files.
From your debug output:
[18696] dbg: config: read file /etc/mail/spamassassin/blacklist-uri.cf
[18696] dbg: config: read file /etc/mail/spamassassin/blacklist.cf
Ditch blacklist and blacklist-uri. These two
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time the answer is stop using blacklist.cf and
blacklist-uri.cf. If 1 person is asking the question,
Quoting Matt Kettler [EMAIL PROTECTED]:
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time the answer is stop using blacklist.cf and
On Fri, 2007-10-26 at 08:16 -0400, Matt Kettler wrote:
Justin Mason wrote:
What else can we do?
Add code to generate a lint warning any time a .cf file over 1mb is read
unless a config option is set to silence it?
But people don't read logs, or they would know... I'd suggest die-ing
Matt Kettler writes:
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time the answer is stop using blacklist.cf and
blacklist-uri.cf. If 1 person is
On Fri, 26 Oct 2007 07:35:13 -0500
Daniel J McDonald [EMAIL PROTECTED] confabulated:
On Fri, 2007-10-26 at 08:16 -0400, Matt Kettler wrote:
Justin Mason wrote:
What else can we do?
Add code to generate a lint warning any time a .cf file over 1mb is
read unless a config option
On Fri, 26 Oct 2007, Duane Hill wrote:
But people don't read logs, or they would know... I'd suggest die-ing
instead.
Why not make it a configurable option in local.cf defaulting to
die. That way for those of us who create custom .cf files that
have the system resources can do so and
On Fri, 26 Oct 2007 09:43:37 -0700 (PPT)
John D. Hardin [EMAIL PROTECTED] confabulated:
On Fri, 26 Oct 2007, Duane Hill wrote:
But people don't read logs, or they would know... I'd suggest
die-ing instead.
Why not make it a configurable option in local.cf defaulting to
die. That
At 04:52 26-10-2007, Justin Mason wrote:
What else can we do?
Add a warning at startup if a sample message takes more than X
seconds to be scanned. Whether people will actually read that
warning is another question.
Regards,
-sm
On Fri, 26 Oct 2007 09:43:37 -0700 (PPT), John D. Hardin
[EMAIL PROTECTED] wrote:
On Fri, 26 Oct 2007, Duane Hill wrote:
But people don't read logs, or they would know... I'd suggest die-ing
instead.
Why not make it a configurable option in local.cf defaulting to
die. That way for those
On Fri, 26 Oct 2007, Nigel Frankcom wrote:
On Fri, 26 Oct 2007 09:43:37 -0700 (PPT), John D. Hardin
[EMAIL PROTECTED] wrote:
On Fri, 26 Oct 2007, Duane Hill wrote:
But people don't read logs, or they would know... I'd suggest die-ing
instead.
Why not make it a configurable
Daniel J McDonald wrote:
On Fri, 2007-10-26 at 08:16 -0400, Matt Kettler wrote:
Justin Mason wrote:
What else can we do?
Add code to generate a lint warning any time a .cf file over 1mb is read
unless a config option is set to silence it?
But people don't read
On 10/26/07 6:59 PM, Matt Kettler [EMAIL PROTECTED] wrote:
Daniel J McDonald wrote:
On Fri, 2007-10-26 at 08:16 -0400, Matt Kettler wrote:
Justin Mason wrote:
What else can we do?
Add code to generate a lint warning any time a .cf file over 1mb is read
unless a
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time the answer is stop using blacklist.cf and
blacklist-uri.cf. If 1 person is asking the question, chances
Daryl C. W. O'Shea wrote:
Justin Mason wrote:
OK, we really need to figure out some way to kill these FAQs off. Every
week, someone asks a question about why SpamAssassin is killing their
server, and most of the time the answer is stop using blacklist.cf and
blacklist-uri.cf. If 1 person is
Add code to generate a lint warning any time a .cf file over 1mb is read
unless a config option is set to silence it?
Simple solution, assuming someone has control of the machine with
blacklist.cf on it:
Replace it with a single blank line.
No complaints about SA stopped working!. Just
Quoting Joey [EMAIL PROTECTED]:
I am currently running SA 3.2.3 compiled from cpan.
I have a situation where CPU is just going through the roof on just a few
messages and I really can't tell what part of SA is the slow down.
[...]
Here is a list of files in each of my SA folders as well as
From: Pedro Correia [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 9:35 AM
To: 'Joey'
Subject: RE: Help figuring our why SA is taking like 1.5 minutes to
filter...
Are you running SA on the same box as the mail server?
I transfered my SA instalation to a dedicated box
First off,
Do an
sa-update -D
as soon as possible.
Cheers,
Phil
--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK
From: Joey [mailto:[EMAIL PROTECTED]
Sent: 25 October 2007 14:24
To:
On Thu, 2007-10-25 at 09:23 -0400, Joey wrote:
I have a situation where CPU is just going through the roof on just a
few messages and I really can’t tell what part of SA is the slow down.
Since this happens for a few messages only, I would start by checking if
these messages got something in
27 matches
Mail list logo
