-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Mon, Aug 30, 2004 at 10:58:45PM -0400, Theo Van Dinter wrote:
I was really hoping rc2 would be it, but I'm thinking with the 3735 fix
we should do an rc3 for good measure. If so, I'd like to get it out on
Wednesday
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
All tests pass.
+1 for release
+1.
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD4DBQFBL65pQTcbUG5Y7woRAkdtAJwK85zFvoE4XeWytYGK3Xzv2CEmQgCWNB4V
/IvksO613A7/VgL5LTk3OQ==
=SzXY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Menschel writes:
Tuesday, August 24, 2004, 7:02:00 PM, you wrote:
JM That's the main issue that we had in the past with external
JM rulesets -- most of those were developed without measuring accuracy,
JM and once tested they don't come out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
- this would probably focus on non-heavyweight, cleanly designed,
high-accuracy, etc. rule sets
BTW, I think you guys (SARE that is) are using mass-check to measure
accuracy, right?
That's the main issue that we had in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth Porter writes:
--On Tuesday, August 24, 2004 5:23 PM -0700 Daniel Quinlan
[EMAIL PROTECTED] wrote:
2. under updates, mkdir 3.0.0/rules/
3. initial filename creation/convention:
70_testing.cf - test rules, gets tested nightly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Lars, MARC web guy (that's what it says! ;),
Just a quick note -- we have moved the SpamAssassin lists as follows:
- SpamAssassin-announce =at= lists.sf.net
= replaced by announce =at= SpamAssassin.apache.org
- SpamAssassin-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hank Leininger writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 22 Aug 2004, Justin Mason wrote:
Hi Lars, MARC web guy (that's what it says! ;),
;)
Just a quick note -- we have moved the SpamAssassin lists as follows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Laurie writes:
Justin Mason wrote:
Hi infrastructure team --
A question (sorry if this isn't the right forum, it's the nearest thing I
could find ;).
To date in SpamAssassin, we've used a role account, namely a user called
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelsey Cummings writes:
FYI, the trap box isn't accepting traffic due to disk space issues.
If someone could resolve it - that'd be great. I could also take it down
and add more disk if it'd help.
fixed...
- --j.
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sun, Aug 15, 2004 at 10:42:51PM -0700, Dan Quinlan wrote:
fixed for -rc1, but could wait in a pinch), so I propose that we issue
release candidate #1.
+1
+1.
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Sun Aug 15 23:44:13 2004
New Revision: 36456
Modified:
spamassassin/trunk/build/3.0.0_change_summary
Log:
revise the release highlights, note: removing hashcash - sorry, it
doesn't make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
It's a new feature we added for 3.0.0 -- it's definitely something a
lot of people have asked about, and are interested in. I think it
should stay in.
The highlights should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sat, Aug 14, 2004 at 05:24:48AM -0400, Christian Rauh wrote:
I hope I haven't left anyone out in this reply. My new update can be
seen at:
http://rauh.net/jobs/spamassassin/logo5.1.png
Thanks for the update! :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Walter Kobylanski writes:
Ups !!! !!!
Well, we could send another update tomorrow if this is true.
We will be expecting your awnser.
yes, he's right ;) capital S, capital A, preferably in
one word...
- --j.
-BEGIN PGP SIGNATURE-
Hi folks --
Thanks for the great logos! *Too* good, in fact ;), because we're now in
a situation where the following three logo proposals are tied in first
place: http://wiki.apache.org/spamassassin/LogoContestTiebreaker
So, since at least one of you has noted that it was a draft, we're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Chris Santerre [EMAIL PROTECTED] writes:
But 1.0.3 is the only one with any kind of Assassin like qualities. And
the center of the star being an '@' is a very cool touch.
Just my opinion here, but the '@' sign in your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
I would like to clean up a confusing point in the documentation about
trusted_networks and internal networks.
I know people who end up with FPs on DUL rules because they have their
outgoing relays and MX relays all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SpamAssassin is a mail filter which uses advanced statistical
and heuristic tests to identify spam (also known as unsolicited
commercial/bulk email).
Downloading
- ---
Pick it up from:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
I just did an update and make test and I see the following... This is
right after I committed my patch, but it doesn't seem like anything that
has to do with it... Probably some fat fingering on my part but I have
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Next time around, why don't we use C-T-R for masses/ and
rules/50_scores.cf when we're in this phase of development? Only switch
to full-tree R-T-C after the scores are in the tree.
It seems C-T-R is more appropriate for
Hi infrastructure team --
A question (sorry if this isn't the right forum, it's the nearest thing I
could find ;).
To date in SpamAssassin, we've used a role account, namely a user called
release, to build releases. Our build procedure relies on using a role
account in order to insulate itself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hold on -- I'm -1 on this change (the sa-learn part that is).
in my opinion, it's more important that the documentation be usable, than
that the normal ordering of the sections be preserved.
I'm happy to have the first three be NAME, SYNOPSIS,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Erenkrantz writes:
--On Wednesday, August 4, 2004 11:52 AM -0700 Justin Mason [EMAIL
PROTECTED]
wrote:
Is the release role account concept used in the ASF at all?
What would you all suggest?
What httpd does is to have a set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Aug 03, 2004 at 06:14:48PM +0800, Yusuf Goolamabbas wrote:
As soon as I started spamd via spamd -Lx -p 7830. I get the following
displayed in the terminal
6166c359a351a9ad990c05334ea520ec
From: [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
bug 3599: Removed -Wall from the CFLAGS for now to make it compile
with non-GCC compilers. The file configure.in is currently broken and
needs some love for 3.1.
-1 the cure is worse than the disease
I think this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all!
This mail is to announce that we're starting the mass-check runs for
rescoring score sets 2 and 3, for the 3.0.0 release. Here's the
procedure you'll need to follow, if you wish to submit data for the
rescoring run.
Instructions:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Friday 23 July 2004 01:36 CET [EMAIL PROTECTED]
wrote:
Date: 2004-07-22T16:36:57
Editor: JustinMason [EMAIL PROTECTED]
Wiki: SpamAssassin Wiki
Page: Spam
URL:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Date: 2004-07-23T11:47:59
Editor: MalteStretz [EMAIL PROTECTED]
Wiki: SpamAssassin Wiki
Page: LogoContestEntries
URL: http://wiki.apache.org/spamassassin/LogoContestEntries
rm'd one of the images as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Fri, Jul 23, 2004 at 10:29:30AM -0700, Daniel Quinlan wrote:
I suggest we roll a pre4 release and allow people to submit mass-check
logs with either pre3 or pre4 (recommending pre4).
+1
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
I believe that is correct, yes. And that's as far as we go in 3.0
(if I replace the = with =3D):
http://penistone=2eopoloveok=2ecom/3/
This bothers me. As best I recall reading the discussions, it turned out
that a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Jul 20, 2004 at 11:18:50AM -0700, Dan Quinlan wrote:
I agree: 1,2,3. Why? I think TCR of 50 is probably still too low, so
I'm looking more at the FP rates.
Ditto on 1, 2, 3. For set0, the FP rate is the main
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes russek writes:
hi ye guys,
i'm sorry, i found DMZS-sa-learn right now :)
hm, but it calls sa-learn and therefore runs two instances of perl.
isnt that senseless?
what about making Mail::SpamAssassin::CmdLearn avaible as perl object?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Chan writes:
Would whoever is editing 3621 please finish so I can add a
comment? I've been blocked since it first came out
Jeff, in that case, just override and put your comment in.
They'll be notified (if they ever commit the comment).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Santerre writes:
-Original Message-
From: Theo Van Dinter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 10:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Debug info WAS: RE: [Bug 3620] SpamAssassin takes a *very*
long time to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelsey Cummings writes:
Sorry to ask this question but I haven't been following the dev list too
well lately. I'm trying to do some schedualing for a SA upgrade at sonic
and I'm curious if there is a rough estimate for the release of 3.0
Kelsey
I can't recall what the consensus was on this, but if I recall correctly
we vaguely agreed that it'd be a good idea, but never anything
particularly concrete. So, SpamAssassin committers: please vote on this
proposal:
Proposal: create a new mailing list, committers at
:
Reporter: Justin Mason
Created: Mon, 19 Jul 2004 11:09 AM
Updated: Mon, 19 Jul 2004 11:09 AM
Description:
(Creating a JIRA issue to track this request.)
Now that SpamAssassin has graduated, we need to move its existing
mailing lists out of the incubator, and into the TLP's domain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Fri, Jul 16, 2004 at 08:33:20AM -, [EMAIL PROTECTED] wrote:
Author: quinlan
Date: Fri Jul 16 01:33:20 2004
New Revision: 22962
-sub get_mbox_seperator {
+sub get_mbox_separator {
return
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
1. Shouldn't we have Return-Path: higher up on the list of envelope
sender headers that are checked in get_envelope_from() ?
Hmm. Well, the idea is:
1. if the unusual headers (X-Envelope-From, Envelope-Sender,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Theo Van Dinter [EMAIL PROTECTED] writes:
FYI: I reverted the change. r22977.
I would have reverted the change if asked and I was anticipating a vote
rather than being reverted. I don't think we need to revert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
Hmm. Well, the idea is:
1. if the unusual headers (X-Envelope-From, Envelope-Sender, X-Sender)
are present and trustworthy, use them
2. fall back to the RFC-2822 std
Hi all!
This mail is to announce that we're starting the mass-check runs for
rescoring score sets 0 and 1, for the 3.0.0 release. Here's the
procedure you'll need to follow, if you wish to submit data for the
rescoring run.
Instructions: http://wiki.apache.org/spamassassin/RescoreSet01Details
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Darryl Bleau writes:
The SA Public Corpus at spamassassin.org/publiccorpus has been a great
help to myself and others who like to use a standard corpus of mail to
evaluate new anti-spam ideas and current techniques.
However, it's now quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would hope that editing the t/config file would be done only in
unusual circumstances. The regression tests should be a sanity check for
everything that is built. The network tests are tricky, since it makes
sense to build SpamAssassin with the
All the pre2 blocker bugs are now cleared up. We're ready for another
pre-release as far as I can see!
everyone +1 on that?
--j.
hey all --
I've just updated http://wiki.apache.org/spamassassin/IncubatorToDo .
I was going to get the lists migrated, but since I'm off to the east
coast for the next 6 days I didn't want to break everything and
disappear ;)
If anyone else wants to run with that, feel free.
I have some code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
OK, I'm planning to change the way the SpamAssassin website operates a
little; instead of its current CVS backing, I want to use SVN.
OK, this is all set up now and could even be made
early bird registrations finish up today, so worth booking if
you're planning to go. (I've just booked ;)
--j.
ok, the website looks good. things left to do there:
- adapt our release style to the www.apache.org/dist/ system
- figure out how to do nightly build tarballs there, given
that as far as I know cron jobs are frowned on (Sander?)
- release 3.0.0 ;) so it has some software on it
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
Ok, so I'm confused...
Why don't we just switch to using spamassassin.apache.org ? Aim the
devel/release dirs at the old site/servers...
There's a bunch of stuff we still need to update on the main site, so
I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sun, Jun 27, 2004 at 08:09:51PM -0400, Theo Van Dinter wrote:
I did look for a (tm) html entity but didn't see one listed. I'll go
change them to do something appropriate then.
Ok, it's now (tm) in small
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I'm planning to change the way the SpamAssassin website operates a
little; instead of its current CVS backing, I want to use SVN.
Specifically, I was planning to check the contents into
https://svn.apache.org/repos/asf/spamassassin/ somewhere. :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
So, +1 for requiring Digest::SHA1.
+1 from me, too.
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFA4FOcQTcbUG5Y7woRAtBfAKDSzjHuxO02+r9h2gxhQrzFNGm+SQCdEHsu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
How about a slight modification?
Migrate data from older version/non DB_File based databases
I don't think there's going to be a real solution for the short doc line,
but the larger section below in the docs can explain it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Malte S. Stretz wrote:
spamasassin.org - spamcop.com :-(
That's a nasty one.
IANAL, and would not want to be mistaken for one, but this article holds
out some hope for remedy under US law:
Domain Name with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] writes:
forgot hashcash in the change announcement mail
I think we should deactivate hashcash by default or remove it. I think
spammers have more CPU than me, this is just asking for some spammer to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Fri, Jun 25, 2004 at 07:28:21PM +0200, Sander Striker wrote:
Hi,
I'd like to move 'spamassassin' from
http[s]://svn.apache.org/repos/asf/incubator/spamassassin/
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Menschel writes:
I've had experience with bylaws creation and maintenance with quite a
few organizations. I find them fun to work with, almost as much fun as
working with computer applications. I'd like to be involved in the
creation of these
:
Theo van Dinter [EMAIL PROTECTED]
Duncan Findlay [EMAIL PROTECTED]
Justin Mason [EMAIL PROTECTED]
Daniel Quinlan [EMAIL PROTECTED]
Malte S. Stretz [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kang , Joseph S. writes:
Not sure how the mailing lists via Apache.org work, but does this mean that
the SA e-mail lists will be moving servers too (i.e., new list addresses)?
Yeah, shortly. we'll let you all know when that happens ;) we should
guys!
Henry
-Original Message-
From: Justin Mason [mailto:[EMAIL PROTECTED]
Sent: June 22, 2004 3:42 AM
To: [EMAIL PROTECTED]
Subject: interesting paper on SpamAssassin (fwd)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://plg.uwaterloo.ca/~gvcormac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Bob Menschel [EMAIL PROTECTED] writes:
I can see the reason for most of Daniel's suggestions, and while I
think 12 months is too short a period for ham (I'd favor 18 or 24
months), I could live with that.
I might be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
Yes, I agree -- this is the problem with older ham. (esp. the SPF
problem. SPF is very brittle on this point.)
How's about putting stricter limits on the net check corpora
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+0.9 on those proposed changes.
Only 1 change: I would suggest that legit bounce messages, where you (the
user) sends a ham (obviously ;) mail and it bounces, should be retained in
the ham corpus where they occur.
- --j.
Daniel Quinlan writes:
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To clarify: I'm +1 on moving to Jira, -1 on using the ASF BZ, and +1 on
using our own BZ, *if* that's OK with the ASF and Theo maintains it. ;)
- --j.
Theo Van Dinter writes:
On Tue, Jun 22, 2004 at 10:55:47AM +1200, Sidney Markowitz wrote:
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://plg.uwaterloo.ca/~gvcormac/spamcormack.html
A good study comparing SpamAssassin (in several configurations) and
several other spam filtering systems, over the course of 8 months (Aug
2003 to Mar 2004). The measurements and methodology are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sat, Jun 19, 2004 at 06:08:40PM -0700, Justin Mason wrote:
/home/corpus-rsync/Obsolete takes up about a gig, and we need that
room ;) anyone mind if I copy that down and nuke it?
I have a solution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
Oh, and I just noticed that apparently we did the move from Craig's
box to the Sonic.net box on 6/21/2003, so happy 1 year anniversary SA
Bugzilla! :)
which brings up another question ;)
Post-incubator-graduation, do we
We're out of disk space.
/home/corpus-rsync/Obsolete takes up about a gig, and we need that
room ;) anyone mind if I copy that down and nuke it?
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Saturday 19 June 2004 23:15 CET Daniel Quinlan wrote:
Michael Parker [EMAIL PROTECTED] writes:
Yes, I think we should do one ASAP. Do we need permission from the
incubator for pre-releases?
No, we just need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Friday 18 June 2004 20:52 CET Michael Parker wrote:
I don't think it's that big of a deal, but I had to do a make clean
after updating to this rev. [...]
We could add a dependency on version.h to the spamc target
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
I propose we do the first pre-release since all of our criteria have
been met. That would be -pre1, I suppose. Three +1 votes are needed.
+1 let's do it
+1 AOL
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien --
You need to set the LANG environment variable from within the script
that starts up SpamAssassin. btw, -users is actually the more appropriate
list, sorry. the other person who sent you to -dev was incorrect ;)
- --j.
Julien V. writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff -- sounds great!
one thing though -- any chance you could make the returned msg a little
more machine-readable? ie. instead of
Blocked, areyoureallysatisfied.biz on sc, ws lists, See:
http://www.surbl.org/lists.html
something like:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
eh, why drop the FP/FN from the summary line? and it's missing
a newline ;)
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Thu Jun 10 17:30:15 2004
New Revision: 21041
Modified:
incubator/spamassassin/trunk/masses/logs-to-c
Log:
more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
eh, why drop the FP/FN from the summary line? and it's missing a
newline ;)
Because those FP and FN numbers are the ones relative to the total
number of messages rather than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bear in mind, the TCR figure that's output to the user in
fp-fn-statistics output is mostly useful to compare against published
algorithms, since it's the de-facto std of effectiveness in the academic
lit on spam-filtering.
But we shouldn't use it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
perfect timing :( bugzilla mail is being *really* slow:
Received: from [64.142.3.173] (HELO bugzilla.spamassassin.org) (64.142.3.173)
by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 07 Jun 2004 19:57:11 -0700
Received: by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sat, Jun 05, 2004 at 07:41:33PM -0700, Justin Mason wrote:
Just looking at the schedule. I think our current set of bugs wouldn't
block either a pre1 release or a set-0 mass-check. ;)
I have a feeling we could spend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm getting all passes with 20559, using perl 5.8.3 on debian unstable,
default PREFIX and SYSCONFDIR.
- --j.
Malte S. Stretz writes:
This is what 'make test' gives me:
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
3. I propose we enter Review-then-Commit mode for HEAD on Monday morning
at 0900 UTC. That should be enough time to cycle everything out of
70_testing.cf, including some network tests that I need to add (NJABL
I occasionally get failures in 'make test' due to a spamd process failing
to exit after a test completes; the next spamd test then fails, because
there's already a spamd running.
Is anyone else getting this, or is it just me? It happens about once every
3 make test's.
I'm worried that this'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
I occasionally get failures in 'make test' due to a spamd process failing
to exit after a test completes; the next spamd test then fails, because
there's already a spamd running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henry Stern writes:
Henry Stern, Justin Mason and Michael Shepherd. A linguistics-based
attack on personalised statistical e-mail classifiers.
Abstract:
We present a potential vulnerability of personalised anti-spam filters
where an attacker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
Moin,
I'd like to kick some parts of the codebase, especially spamc and spamd,
through a reformatter so the style gets consistent and better to
understand. The coding style was discussed some weeks ago, I'll update the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
It seems like a huge improvement across the board. There are a few
small slips, but do we care?
It does look very nice to me.
Would it be possible to have *both*? Namely one set of rules (with
high scores) for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
I'd suggest a further tweak, BTW: for the masses scripts that DAF is
talking about putting into a -tools pkg, I suggest we rename them to
use an sa- prefix. e.g. sa-mass-check, sa-hit-frequencies, et al.
This helps to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warren, sign me up. Duncan, you should have told me ;) I'm signed up
now.
Anyone else fancy signing up to either?
(It's a pity we can't just feed reports automatically from the FC/deb
trackers to the upstream.)
- --j.
Warren Togami writes:
Any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Chris Thielen [EMAIL PROTECTED] writes:
Second, where is the appropriate place for discussion of FPs?
Bugzilla, sa-dev or elsewhere?
If it's a question your mail, I'd say sa-dev. If it's a rule you think
could be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hmm:
May 14 01:20:58 dogma postfix/smtpd[19816]: connect from
hermes.apache.org[209.237.227.199]
May 14 01:20:59 dogma postfix/smtpd[19816]: 1BF58310253:
client=hermes.apache.org[209.237.227.199]
May 14 01:20:59 dogma postfix/cleanup[9961]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Wed, May 12, 2004 at 11:57:40PM +0800, Yusuf Goolamabbas wrote:
Hi, Can I add arbitrary headers from a plugin into a message
I tried doing the following
$permsgstatus-get_message()-header(X-Something, $value);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
I'm not sure what we should do about failures. This might be a case
where we have to avoid using the GA and go with human set scores,
initially very low until SPF is more generally reliable.
Or just hint perceptron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sabat writes:
Did this patch get rejected? Don't see any evidence of it in CVS. :-(
I'm not sure if it made it into the 3.0.0 queue -- was there a bug
for it? (it's very hard to keep track of stuff that isn't in bugzilla.)
However, 3.0.0 now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Fri, May 07, 2004 at 04:36:43AM -, [EMAIL PROTECTED] wrote:
+ # remove www.fakehostname.com@ username part
+ $host =~ s/[EMAIL PROTECTED]@//gs;
IMO, get_uri_list shouldn't remove that, that should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dallas L. Engelken writes:
I have sent via fax machine CLA and sent email about this.
This was realy long
time ago. But bugzilla still show red cross after by name.
ditto here...
Hi guys --
yeah, we haven't got a good way to track these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Menschel writes:
And then, there's a whole universe of rules which are not included in
SA's distribution rule set, and which should NOT be included in SA's
distribution rule set. An example from my 70_sare_genlsubj3.cf:
# OVERALL% SPAM%
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
... is now in SpamAssassin SVN trunk. it uses quite a lot of data
from the SURBL list of TLDs and their subdomains, btw, thanks! ;)
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doc Schneider writes:
I am on my days off and hope to get some type of stats gathering ditty
going. But not sure what stats folks want to see. I had some
conversations with Chris The Big Evil One and he had some ideas.
Am just not sure what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doc Schneider writes:
We recently added some additional stats output to spamd in SpamAssassin
3.0.0. This should improve the accessibility of info about rules
being used during scanning for tools to summarise.
So in SA 3.0 there will be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
promote SENDERBASE_NEW_BULK (hits about 8% of spam real-time)
excellent -- I think this'll be interesting ;)
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
1 - 100 of 241 matches
Mail list logo
