Chris schrieb:
On Saturday 27 September 2008 12:23 pm, Matthias Keller wrote:
Chris wrote:
I'm still seeing this:
Hi
You forgot to change check_ixhash to ixhashtest as written in the
email a bit futher up...
Matt
Thanks Matt, that did the trick, works cor
On Saturday 27 September 2008 12:23 pm, Matthias Keller wrote:
> Chris wrote:
> > I'm still seeing this:
> >
>
> Hi
>
> You forgot to change check_ixhash to ixhashtest as written in the
> email a bit futher up...
>
> Matt
Thanks Matt, that did the trick, works correctly now.
--
Chris
KeyID
Chris wrote:
> On Saturday 27 September 2008 4:13 am, Dirk Bonengel wrote:
>
>>> Chris, there were a few errors in the sample config (eval:check vs.
>>> ixhashtest & cytme vs. ctyme). Use this instead:
>>>
>>> body GENERIC_IXHASH eval:ixhashtest('generic.ixhash.net')
>>> describe GE
On Saturday 27 September 2008 4:13 am, Dirk Bonengel wrote:
> Original-Nachricht
> >
> > Chris, there were a few errors in the sample config (eval:check vs.
> > ixhashtest & cytme vs. ctyme). Use this instead:
> >
> > body GENERIC_IXHASH eval:ixhashtest('generic.ixhash.
I've been trying out ixhash today. It seems to be quite accurate on spam, but
adds no increment to the spam already identified by sa. It just runs up the
score:
egrep -i 'spam\,.*(ixhash)' /var/log/maillog | awk '{print $12}' | less
score=33.423
score=25.893
score=28.28
score=24.472
score=29.4
>
> You expect the same from the other people on this dont you? This issue was
> handled like explained in a normal way. The list was frozen and was
> expected to return. Now that its known to turn out otherwise its removed.
>
> And within a day promoted on SA update.
>
> I still see it listed
Greetings;
I fired off this script, named sa-update.cron, but which has been disabled in
the crontab since someone here said it was a waste of time, and now it seems
to be hung. Running it as root this time.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ball
I am running SA 3.2.5 on NetBSD. I have a cron job to do
/usr/pkg/bin/sa-update --gpgkey 6C6191E3 --channelfile
/usr/pkg/etc/spamassassin/channels.txt
with channels.txt having
updates.spamassassin.org
sought.rules.yerp.org
The updates work, as evidenced by new bits in
/var/spamassassin
>
> ...and I bet there are still commercial anti-spam products using
> dsbl.org because they haven't figured it out either :-)
Wasn't there a standard at one time, return something different (test) if
you queries 2.0.0.127.{dnsblacklist}? If it returned (at least) '127.0.0.2'
and a list of othe
Hi!
So what is your point Raymond?
That we are end users should find out every external subsystem call and
document it and search for and get on lists that may or may not exist let
alone email us if their baby fails and bites the dust?
You expect the same from the other people on this dont
Todd Adamson a écrit :
> If dsbl has been down for awhile, since around June, why hasn't it
> been removed from the configuration via sa-update before now? That's
> one of the purposes of sa-update.
Querying their dns server is certainly a waste of time, but isn't really
a critical issue. At the
Original-Nachricht
> Datum: Fri, 26 Sep 2008 21:07:47 -0700
> Von: Bill Landry <[EMAIL PROTECTED]>
> An: users@spamassassin.apache.org
> Betreff: Re: ixhash - failed to run CYTME_IXHASH test, skipping
> Chris wrote:
> > I've changed the ixhash.cf per Dirk's instructions, the who
12 matches
Mail list logo
