-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
Sorry to be a killjoy here.
On Mon, May 09, 2005 at 03:55:07PM -, [EMAIL PROTECTED] wrote:
+ my $redirector_patterns = $self-{conf}-{redirector_patterns};
+ @uris =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
I'm not entirely sure how useful this is -- on one hand, it's
a great way to point to a single configuration setting. OTOH,
it's another thing that can break, so I want to make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
That would be easier to do. Probably a good idea, sth like:
/ref/3.0.x/use_auto_whitelist.html
I'd strongly advocate providing versioned links for the current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Jaspan writes:
The two main things I seem to remember are that perl 5.6.1 fixes a bunch
of bugs from 5.6.0
If anyone can remember what bugs were fixed that affect SpamAssassin, I'd
appreciate it.
if I recall correctly, all of them were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Alan!
Alan Schwartz writes:
Lately, running SA 3.0.0 with no rule or score tuning, I have been
noticing that my false negatives tend to have BAYES_99 matched.
The scores file lists the following scores for Bayes:
50_scores.cf:score
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
+If you use Debian, you can get Storable from the libstorable-perl
+package.
might be better to just have:
Debian: apt-get install libstorable-perl
Fedora: apt-get install perl-Storable
since I can see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't the SYNOPSIS used for spamd's usage message? If so, I
think removing the defaults from that message is a bad thing...
- --j.
[EMAIL PROTECTED] writes:
Author: mss
Date: Fri Sep 10 13:11:49 2004
New Revision: 43688
Modified:
So in thinking about the class cleanup we've been wanting to do for a
while; I think the top items on the list (my list at least) are:
- rename the Mail::SpamAssassin::PerMsgStatus class
- break it up into multiple, smaller classes
So here's what I propose for the first one.
Rename the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
I think it would be better if we did not allow end-of-line comments and
required all comments to match:
/^\s*#/
Then comments don't need to be escaped. I think that would involve less
surprise and also solves the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Justin Mason [EMAIL PROTECTED] writes:
That would be a major change in how our configuration files are parsed,
breaking a documented (although not particularly clearly) convention
that's been there since the project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Sunday 26 September 2004 10:42 CET Daniel Quinlan wrote:
[...]
Do we really need to do this now? This is not going to significantly
help performance, accuracy, or memory usage, is it?
As much as I loved to have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
BTW, this is the rule reliability tflag idea again; basically provide a
way to
hint that this rule is reliable, and this rule should not be considered
reliable
-- no matter what their hit-rates in mass-checks were.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
- (public) message rewriting functionality
rewrite_mail
move code into another class; leave this public API on the ::Scan
object which calls
OK, here's a trick I was thinking about. Currently we have these massive
hashtable refs:
$pms-{conf}-{rbl_evals}
{head_tests}
{body_tests}
{scoreset}-[0,1,2,3]
{tflags}
Each of those is keyed by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
I have no idea how painful linked lists are in Perl (or if they even
exist).
Why are you commenting then???
Because they are very useful, as I pointed out.
They don't exist as a native data structure. Arrays are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As much as I loved to have this thing renamed, why didn't we do this
*before* we released 3.0? Or to quote you from bug 3668: there's *no
way* I'd be happy making any of these changes before 4.0.0 ;)
(Actually, the no way is exaggerated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Wed, Sep 29, 2004 at 10:21:06PM -, [EMAIL PROTECTED] wrote:
+- MIMEDefang: version 2.42 or later.
FWIW, I completely disagree with doing this. A) It will give the
impression that we support these programs (I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
Why I sort that file now and then is because it makes it much easier to see
if a file is already in there or remove one which is gone. Keeping the
MANIFEST up-to-date is already a PITA and an unsorted file makes it even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Thursday 30 September 2004 18:42 CET Justin Mason wrote:
Malte S. Stretz writes:
Why I sort that file now and then is because it makes it much easier to
see if a file is already in there or remove one which is gone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
actually, you're right on both; I just checked with perl -e in perl 5.8.4.
I must have been thinking of java instead of perl ;)
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
A very interesting paper at Toorcon -- the use of bioinformatics
techniques to perform black-box protocol reverse-engineering.
Again, this is likely to be useful for automated discovery of antispam
regexp rules... worth a read:
http://www.baselineresearch.net/PI/PI-Toorcon.pdf
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: mss
Date: Sat Oct 2 08:29:31 2004
New Revision: 51805
Modified:
spamassassin/trunk/Makefile.PL
Log:
Just for fun...
what does this do? could we get some more descriptive commit messages,
and possibly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
BTW, note that plugins *should* be able to push their own entries
onto the $conf-{registered_commands} list. That is, in my opinion,
much cleaner than the current parse_config() API, and may be worthwhile
as a way for future plugins to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelsey Cummings writes:
On Tue, Oct 05, 2004 at 03:25:55AM -0700, Jeff Chan wrote:
4. SURBL query traffic
mostly good if you subtract the blacklisted ones
But any big, as-yet-undetected spam domains can also generate
much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelsey Cummings writes:
On Tue, Oct 05, 2004 at 05:05:18PM -0700, Justin Mason wrote:
Kelsey Cummings writes:
On Tue, Oct 05, 2004 at 03:25:55AM -0700, Jeff Chan wrote:
4. SURBL query traffic
mostly good if you subtract
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
There are currently 5 (of 8) tickets in the 3.0.1 queue in the review
state. One has been in review state since 9-29 (3831) and needs another
+1, 3872 is major (needs another +1), 3741 and 3865 had patch added today,
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason wrote:
The first fix is truncation of the text before passing to TextCat.
Michael, I think you were looking at this? the results are impressive,
if the text is truncated to 32k bytes:
It was me.
oops
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason wrote:
the test should be a no-op without that module did that not work?
This is extracted from output of make test, running under Cygwin with
perl 5.8.5
t/memory_cycles.Can't locate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Thu, Oct 21, 2004 at 12:01:20AM -0400, Theo Van Dinter wrote:
I'd like to get 3.0.1 released in the next few days. There are 2 tickets
left
in the queue: can we get them done up in the next day or so?
+1 on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
I propose we release SpamAssassin 3.0.1. All bugs are closed now.
+1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFBeGTKMJF5cimLx9ARAnavAJ9hJN088VrH7LM1eHiPXr9DJ7xeLACght6V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SpamAssassin 3.0.1 is released! 3.0.1 contains some important
bugfixes, and is recommended.
Highlights:
- excessive memory-usage fixes
- bug fixed which stopped DCC, Pyzor working with amavisd
- deprecate RCVD_IN_RFC_IPWHOIS
- user_prefs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-font-family: verdana,lucida,helvetica,sans-serif;
+font-family: arial,helvetica,sans-serif;
just to reiterate -- I'm -1 on this change. It looks awful
by comparison (where Verdana is available), at least under
Firefox on linux.
Some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Fri, Oct 22, 2004 at 08:09:10PM -0700, Justin Mason wrote:
SpamAssassin 3.0.1 is released! 3.0.1 contains some important
bugfixes, and is recommended.
Another couple of notes about the release. Apparently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
was: Re: [Bug 3931] [review] remove the annoying 'inhibited further
callbacks' debug message
(a) new debug code in 3.1.0 doesn't have higher debug levels
Really? That kind of sucks (although we never really used it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd strongly prefer (I'm probably -1 on creatingh two new options for
this one) to keep opt_j as the number of processes (it parallels make
-j) and add a new option for the temporary file vs. in-memory option.
The temporary file thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Log:
work on the mass-check output a bit, state when scan has ended and
run begins (rough approximation since the run has already begun at
that point), format the lines better, etc.
hey btw are we going to merge Duncan's mods? we really should,
So, we were discussing the rules situation -- ie. that we've been pretty
crap at getting rules into the distro. I proposed this, and I think we're
reasonably into the idea as a way to help out.
We add a web-app somewhere that periodically scrapes bugzilla
for bugs on the rules component which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kurt Humes writes:
I am begining to build a Java Libray to act as a client to spamd, not
using JNI however. Has anyone ever done something similar and if so
what are the roadblocks that you have come across.
Kurt, I'm unaware of anything, but it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
btw, I was thinking of keeping this link around, on the wiki at least, in
case the slides became available... (hint hint ;)
- --j.
[EMAIL PROTECTED] writes:
Date: 2004-11-19T21:55:15
Editor: DanielQuinlan [EMAIL PROTECTED]
Wiki:
this just came up on perl5-porters...
http://www.nntp.perl.org/group/perl.perl5.porters/96100 :
Subject: Re: sharing hash-values
From: btilly[at]gmail.com (Ben Tilly)
...
I forgot who I first saw mention this, possibly gbarr, but the following
variation on %seen seems to be the fastest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
btw, would a name prefix sound like a good idea for a convention to
indicate rules that exist to catch never-seen-in-the-wild spammer
exploits? Something like EVIL or similar?
it'd provide a great way to (a) visually see that those rules not
firing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] writes:
[...]
sub service_unavailable_error {
my ($err) = @_;
my $resp = EX_UNAVAILABLE;
- print $client SPAMD/1.0 $resphash{$resp} Service Unavailable: $err\r\n;
+ syswrite( $client,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Daniel Quinlan wrote:
Please try to use the more standard perl formatting:
Do you see anything wrong other than two of the lines being more than 80
characters? I'll check in an update to fix that as soon as I finish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reminder: do we have a consensus what to do about this? can we reinstate
the functions in the meantime?
- --j.
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Sat Nov 20 00:17:49 2004
New Revision: 105955
Modified:
so we're setting up a distributed build-testing system,
BuildBot (http://buildbot.sourceforge.net/), for now at
http://bugzilla.spamassassin.org:8010/
(that url may change.) it currently has 4 build slaves, building
- trunk using Red Hat 7.3's perl
- trunk using vanilla perl 5.6.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] writes:
What's the probability that I run into an already used port with the
new probably_unused_spamd_port() code? Less than 1 per mill? Ask
Murphy...
The only chance of a collision is if the
looks like it *is* indeed on this year -- http://www.spamconference.org/
CFP ends in 4 days though.
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Finch writes:
perl Build.PL install_base=~
This is different from PREFIX in that its not going to try and guess how
you want things installed based on your system installation. It's just
going to plop things into ~/bin, ~/lib,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Sergeant writes:
On 1 Dec 2004, at 15:13, Malte S. Stretz wrote:
So I'd like to keyword some of the tests as basic (or whatever
keyword) and only those tests are run per default. All other tests
would be used by us devs, people who we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
as a matter of interest -- I guess this is for Daniel -- why is that
debug-area-splitting-and-validation code not part of Mail::SpamAssassin,
anyway?
Looks like it's duplicated in spamd, spamassassin, and sa-learn, which
will result in it getting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
This came up on the list, I considered it trivial enough to just go
ahead and commit it to the 3.0 branch. If there's an issue, let me know.
On Fri, Dec 03, 2004 at 05:23:15PM -, [EMAIL PROTECTED] wrote:
-next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Fri, Dec 03, 2004 at 12:58:24AM -0800, Cron Daemon wrote:
svn: In directory 'nightly_mass_check/rules'
svn: Can't copy
'nightly_mass_check/rules/.svn/tmp/text-base/25_razor2.cf.svn-base'
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yes *please* ;)
- --j.
Tony Finch writes:
I've been doing some DNS-intensive work with ADNS recently, and I was
reminded how fast it is and how easy it is to run bulk jobs with over
10,000 concurrent DNS queries. You only need two sockets! Maybe
.
--- Forwarded Message
Date:Mon, 06 Dec 2004 20:02:16 +
From:Upayavira [EMAIL PROTECTED]
To: Apache Infrastructure [EMAIL PROTECTED]
Subject: Re: Addressing wiki vandalism
Justin Mason wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leo Simons writes:
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Date: 2004-12-08T11:22:11
Editor: MrElvey [EMAIL PROTECTED]
Wiki: SpamAssassin Wiki
Page: CommercialNetworkAppliances
URL: http://wiki.apache.org/spamassassin/CommercialNetworkAppliances
Justin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Mon Dec 13 16:39:58 2004
New Revision: 111767
URL: http://svn.apache.org/viewcvs?view=revrev=111767
Log:
remove Flex Hex rules due to low accuracy
what were the results?
- --j.
Modified:
OK, so on the spamd hang bugs, we have:
- a set of people reporting hangs predominantly (all?) when running spamd
on hyperthreaded CPUs
- not all HT CPUs are acting up
- a hang traced into Storable::dclone() (thanks Dallas!)
so I think we may have run into a perl thread-safety bug, possibly
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Wed, Dec 15, 2004 at 04:25:29PM -0800, Daniel Quinlan wrote:
Bugzilla says we can release 3.0.2 so I therefore propose we release 3.0.2.
+1 for release, all tests pass on several of my machines.
+1, if we're all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
It's moot at this point, and I meant to vote -0.5 and not -1 BTW.
I wanted more of a I'd rather not yet versus NFW. It was more of
a shock of nothing at all for weeks about a release, then suddenly,
the one night I'm not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: felicity
Date: Wed Dec 15 22:25:05 2004
New Revision: 122529
URL: http://svn.apache.org/viewcvs?view=revrev=122529
Log:
got a syntax error doing reporting. also, no point in doing regexp since
we're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Friday 17 December 2004 11:36 CET [EMAIL PROTECTED]
wrote:
The Buildbot has detected a new failure of trunk-debian-stable.
Buildbot URL: http://bugzilla.spamassassin.org:8010/
Build Reason: changes
Build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason wrote:
Sidney, have you tried setting --keepalive=300
I'll try that. What Michael says does make sense. I'm behind a NAT.
Is there a way of setting a port that the slave listens on? I can
configure my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Malte S. Stretz wrote:
Does anybody know what exactly goes wrong? Maybe it could work if we use
port forwarding or stunnel or something to route the traffic to the dynamic
clients over some server with a static IP?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
Well, I think failed svn is something that all build failures produce.
Even if the problem is a bug, rather than an svn timeout...
I think we should remove (a) all of the NATed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
makes sense to me. I'd (a) expand the doco, and (b) use a better
name than verify_user for the method, as it took a while for me
to grok it.
rather than verify_user, how's about service_acl_allows_username or
similar?
- --j.
Michael Parker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Fri, Dec 17, 2004 at 05:38:26PM -0800, Justin Mason wrote:
ok -- service_allowed_for_username -- there's only one service for
each call. ;)
Why put that sort of restriction?
what if I wanted something like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Fri, Dec 17, 2004 at 04:41:51PM -0800, Justin Mason wrote:
makes sense to me. I'd (a) expand the doco, and (b) use a better
name than verify_user for the method, as it took a while for me
to grok it.
rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Fri Jan 7 00:06:07 2005
New Revision: 124477
URL: http://svn.apache.org/viewcvs?view=revrev4477
Log:
promote T_BAD_ISO_CHARSET to MIME_BAD_ISO_CHARSET, but convert it to an
eval function to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
we should really figure out some way to expose those in-body MIME headers
in a new rule type...
I was thinking the same thing.
oh good, so you've changed your mind since
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Rules with the largest RANK drops from 3.0 to now. The body and
Subject: ones probably need the most work. The rest are probably lost
causes.
I suggest we drop them, if their RANK is sufficiently low and nobody steps
up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
First, large ISPs seem to be the origination point for a *lot* of spam.
Large ISPs' outbound relays, or direct from their dynamic pools?
e.g. blueyonder.co.uk list their dyn pools in their SPF record,
which is unfortunate but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Schulz writes:
I would like to suggest that having a Target Milestone of Future for a
bug is harmful. It was probably necessary when you were trying to get
3.0.0 out and you were not sure what the next verson number would be,
but now it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Do we want to fix this for 3.0.3, or just leaving it for 3.1?
I'm okay with backporting, but I think we're nearing the point at which
we buckle down on 3.1 and focus on it. The tree is remarkably stable
right now and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
I'd like to make IP_IN_RESERVED_RANGE go away. In an ideal world, but I
know Justin will object so I won't propose it, I would nuke it. Since
it's possible some poor unsuspecting third-party plugin is using it in
the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
oh good, so you've changed your mind since
http://bugzilla.spamassassin.org/show_bug.cgi?id781#c3 then ;)
Somewhat. I still think it should be a plugin.
There's a problem with plugins I hadn't realized when they were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
I was noticing that the BZ box gets hammered, at the moment due to buildbot:
If we're going to run buildbot on there, it should at least be done in serial
and not parallel.
not sure how easy that is :( we could add some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Actually, can I suggest a different naming convention?
T_bug number_test name
For example,
T_4081_FOO_BAR
Short and easy to look up. Also, does your code handle naming for
new/overlapping/existing predicates
on committing comment 11 to bug 4058:
Internal Error
Bugzilla has suffered an internal error. Please save this page and send it to
dev@spamassassin.apache.org with details of what you were doing at the time
this message appeared.
URL: http://bugzilla.spamassassin.org/process_bug.cgi
undef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Justin, can you change a few things in addition to the names?
- check-in via some role account
asking infrastructure about this...
- don't rename the tests every time - this is maddening
ok, let's see what I can do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Theo Van Dinter [EMAIL PROTECTED] writes:
Yeah, that mostly sums up my feelings. The current RBL information tells
us when a positive lookup occurs, but not when a negative lookup occurs.
True, you have to assume a
So here's a quick look at some DomainKeys rule freqs, from a quick
mass-check of the last ~10k ham and ~10k spam in my corpus (mass-check
--tail -j=8 --net --rules '^DK'):
OVERALL% SPAM% HAM% S/ORANK SCORE NAME
19991 9998 99930.500 0.000.00 (all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
ah, I didn't post examples of what the new formatting looks like --
here it is in report_safe 1:
The example I posted *was* report_safe 1, so the new formatting does
not look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Friday 21 January 2005 04:29 CET [EMAIL PROTECTED] wrote:
Author: jm
Date: Thu Jan 20 19:29:20 2005
New Revision: 125877
URL: http://svn.apache.org/viewcvs?view=revrev5877
Log:
fix desc_wrap.t to deal with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm happy with the sa-check idea, as long as we keep a spamassassin
wrapper that just does an exec(). easy enough, and very sensible.
+1
I think the POD docs from spamassassin should be split into the
sa-check POD and whatever other sa-blah scripts
from a mass-check run I did last night. these are more promising;
12% of ham whitelistable:
19992 99930.500 0.000.00 (all messages)
100.000 50.0150 49.98500.500 0.000.00 (all messages as %)
6.338 0.0500 12.62880.004 1.000.00 DK_SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Raymond Dijkxhoorn [EMAIL PROTECTED] writes:
Please let us know what we should do, cutting out we should announce, the
actual removal is just altering one export script...
Considering that SA hasn't shipped with JP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Menschel writes:
Hello Daniel,
Saturday, January 29, 2005, 9:46:05 PM, you wrote:
- higher accuracy: lower FPs and lower FNs (rules, rules, rules... this
also includes some notion of speeding up the mass-check process)
DQ I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Few things:
1) I thought plugin callss couldn't return values?
actually -- they can. (I think in the config file case, it was the type
of the return value changing frequently that was problematic).
2) I like the Plugin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Sun, Jan 30, 2005 at 10:49:04PM -0800, Justin Mason wrote:
Michael Parker writes:
Few things:
1) I thought plugin callss couldn't return values?
actually -- they can. (I think in the config file case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
This is a MIME-formatted message. If you see this text it means that your
E-mail software does not support MIME-formatted messages.
--=_mail-11561-1107210743-0001-2
Content-Type: text/plain; charset=us-ascii
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Michael Parker wrote:
Which might be ok, but I can promise you that someone is going to go
through and either rm init.pre or comment out every loadplugin line
and then start asking questions about why their system isn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael raised a good point on IRC:
Herk Theo makes a good point on the existing init.pre file, upgrades
aren't going to get the new loadplugin lines added to their init.pre
jmason well, it's exactly analogous to Apache's httpd.conf file
Herk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
+Note: there are no guarantees that the internal data structures of
+SpamAssassin will not change from release to release. In particular to
+this plugin hook, if you modify the rules data structures in a
+third-party
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
... that makes the new plugin API sound quite a bit less useful ;)
what's it being added for?
ReplaceTags.
I hope to eventually clean up the internals and make it okay after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
Ok, here are my thoughts about how to do faster updates. ie: how
to release rules + scores faster, potentially multiple times a day.
I currently only think rules + scores ought to be released this way -- people
aren't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Menschel writes:
TVD Versions are tracked per channel and SpamAssassin version. To check
TVD for updates, do a DNS TXT query ala
TVD z.y.x.updates.spamassassin.org,
TVD where z.y.x refers to the version of SpamAssassin being used, aka:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Malte S. Stretz [EMAIL PROTECTED] writes:
I'll fix this (it needs to be done via the B_FOO (build) and I_FOO
(install) hacks).
Thanks, I sent a few comments in my last message. ;-)
Just to be sure: spamassassin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sander Striker writes:
Subject says it all. Please fix ASAP.
did it get fixed? appears to be working now. the contents are:
Redirect /doc http://spamassassin.apache.org/full/3.0.x/dist/doc
Redirect /downloads.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Menschel writes:
Hello Theo,
Saturday, February 12, 2005, 11:21:16 PM, you wrote:
3) Using channel.cf means that it may or may not come after local.cf.
We should probably use some form of prefix to get it to load beforehand,
but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
demerphq writes:
As you can see, except for the _construct benchmarks, B wins by a
large margin. The _construct tests are designed to see what the
overhead is of constructing the trie for nothing (ie, the match is at
^), and shows that the
1 - 100 of 1307 matches
Mail list logo
