In debugging some Spamassassin configuration problems, I've found lots of
Botnet-plugin-related errors in my logs -
" Use of uninitialized value in string eq at
/var/spamassassin/local/Botnet.pm line 564."
I found a January 17th, 2007 post on this @
http://archives.devshed.com/forums/networkin
Thanks for the prompt reply.
> What makes you believe that SA has hung and isn't actually doing
> something? Without any indication that SA has actually hung I would
> suspect that a bayes auto expiry is taking place. If you prefer, you
> could disable bayes_auto_expire and run expiries via
Daryl C. W. O'Shea wrote:
It's a bug in the test suite. Just do a force install.
Ok, force installed and it's working -- thanks. But am getting this perl
error trying to feed it spam:
Command:
sudo sa-learn --spam -C /etc/mail/spamassassin --showdots --dir /spam
Error:
Can't use string ("Ma
On Sunday June 24 2007 19:30:32 OliverScott wrote:
> Though BotNet is VERY effective in catching SPAM, the default score of 5 is
> way too high IMHO.
I fully agree, 5 is way too high.
> With a well trained BAYES, using a selected list of RBLs and URIBLs for
> scoring, the SARE rules, and some cus
Randall Perry wrote:
> I've currently got 3.2.0 running ok with perl 5.8.6 under Mac OS 10.
>
> On trying to install 3.2.1 via CPAN I get the errors below (these are
> the only failed tests -- the rest passed or were skipped). I've
> installed/updated all required and most optional modules, excepti
It's a bug in the test suite. Just do a force install.
Daryl
Randall Perry wrote:
I've currently got 3.2.0 running ok with perl 5.8.6 under Mac OS 10.
On trying to install 3.2.1 via CPAN I get the errors below (these are
the only failed tests -- the rest passed or were skipped). I've
insta
I've currently got 3.2.0 running ok with perl 5.8.6 under Mac OS 10.
On trying to install 3.2.1 via CPAN I get the errors below (these are
the only failed tests -- the rest passed or were skipped). I've
installed/updated all required and most optional modules, excepting
Net::Ident and IO::So
... you're usually OK ... debug might tell you why ... might be able to
tell you why ... it probably did.
Haha. Now that we've cleared THAT up ;-)
Kidding aside ... I understand.
Thanks,
JTDeLys
JT DeLys wrote:
One comment that I'll share: After reading the list, wiki, general web,
etc I got the clear message that lint+debug-ing is a wise/necessary step.
It wasn't immediately clear to me that these 'failures' weren't real
problems (that's why I'm asking here, of course). Is there s
This is normal, some regexes can't be optimized. They're still used
though.
> What do I do about these?
Nothing.
That's good. And, thanks.
(Re-enabling loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody now).
One comment that I'll share: After reading the list, wiki, general web, etc
I go
JT DeLys wrote:
I've installed Spamassassin version 3.2.1, and have enabled
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
in 'init.pre'.
After downloading the latest rule updates using sa-update, when I
compile the rules using
sa-compile --sudo -D
It finishes "correctly" at
C
Though BotNet is VERY effective in catching SPAM, the default score of 5 is
way too high IMHO.
With a well trained BAYES, using a selected list of RBLs and URIBLs for
scoring, the SARE rules, and some custom rules of my own I am confident that
I am catching well over 90% of the SPAM hitting my se
On Sun, 24 Jun 2007, Marc Perkel wrote:
> One thing that spammers can't spoof is RDNS. So if the RNDS of an
> IP is xxx.xxx.amd.com then we know the email is ham.
...unless, for instance, an AMD corporate box gets pwned.
> A query comes in to a specially written DNS server where the RNDS
> is lo
OK - here's an idea I'm rolling around in my brain and thinking this
could work to massively automatically generate white lists of IP
addresses from companies that generate no spam at all. This could be
used not only to greatly reduce false positives, but also you reduce
system load. Any IP lis
14 matches
Mail list logo
