-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yitzchak Scott-Thoennes writes:
On Tue, Feb 15, 2005 at 12:40:50PM -0800, Justin Mason wrote:
FWIW, this looks like it'd be excellent for SpamAssassin ;)
Maybe somebody with SpamAssassin could do some benchmarks?
I'm a little concerned it might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would suggest just running perl parse-rules-for-masses -d $(RULES) -s
$(SCORESET) directly, just in case make dependencies make things
go haywire.
- --j.
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Tue Feb 15 15:10:09 2005
New Revision:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[de-cc'ing p5p on this one since it's just sa-related.]
demerphq writes:
Incidentally I did notice that many of the patterns used could be
reworked to be more efficient assuming the patch is applied. Also I
was kinda wondering about the code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Daniel Quinlan wrote:
We support nmake?
That's the Microsoft nmake, not to be confused with any other make
program of the same name. It's what is available on Windows. For
compatibility we have to put all the fancy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Michael Parker [EMAIL PROTECTED] writes:
Now you're adding in a whole other subsystem. Using this logic, it is
pretty easy to argue that everything should be in one executable, and
not split out. A little cross use
the signed content. So I
don't think this is a good idea.
Hope this helps and isn't too rambling.
-Jim
Mark Delany wrote:
On Fri, Feb 11, 2005 at 04:18:01PM -0800, Justin Mason allegedly wrote:
Mark, Jim --
hi, Justin Mason here from SpamAssassin. I have a quick question
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Justin Mason [EMAIL PROTECTED] writes:
On another aspect --- I like Michael's idea of leaving the
spamassassin script's UI intact as it is now for a few 3.x
releases. There is a lot of third-party code that hooks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
I fixed the test failure in t/debug.t checking in to r155617.
The test was just missing a new dbg message tag, replacetags, so I added
it to the list.
I'm less sure about what is the correct thing to do for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason wrote:
According to the SPF people, we shouldn't
be using -all on a domain that may possible emit mail
Even if, as I think, ~all is correct if you can enumerate all legal
senders for the domain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
Sidney Markowitz wrote:
Justin Mason wrote:
According to the SPF people, we shouldn't
be using -all on a domain that may possible emit mail. So I changed
the record...
snip
If you can list all sending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] writes:
plugins can now set tags to subroutine references, to return dynamic
data easily
Excellent.
Could/should we require them to be named starting with PLUGIN_ ?
in my opinion, no -- it'd mean
Hey all --
looking at users@ traffic recently, there's been a *lot* of reports of
people running into various problems with DB_File: spamd memory usage
ballooning, deep recursion errors, hangs, etc.
I'm thinking we should rewrite some of our doco for 3.1.0 to suggest that
most sites running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Finch writes:
On Thu, 10 Mar 2005, Daniel Quinlan wrote:
Tony Finch [EMAIL PROTECTED] writes:
Is anyone planning to implement CSA for SpamAssassin?
http://mipassoc.org/csv/
I have not heard of any plans to implement Comma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Mon, Mar 21, 2005 at 01:18:48AM +0100, Malte S. Stretz wrote:
On Friday 18 March 2005 08:46 CET [EMAIL PROTECTED] wrote:
Author: parker
Date: Thu Mar 17 23:46:45 2005
New Revision: 158029
URL:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Mar 22, 2005 at 06:00:36AM -, [EMAIL PROTECTED] wrote:
bug 3409: modify header ordering for DomainKeys compatibility, by placing
markup headers at the top of the message
Hrm. I don't think we want our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malte S. Stretz writes:
On Tuesday 22 March 2005 19:15 CET Justin Mason wrote:
Theo Van Dinter writes:
On Tue, Mar 22, 2005 at 06:00:36AM -, [EMAIL PROTECTED] wrote:
bug 3409: modify header ordering for DomainKeys compatibility
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Daryl C. W. O'Shea [EMAIL PROTECTED] writes:
Should I remove this from trunk? I'm indifferent on the option... I
just saw the open bug and finished the code someone at one time
apparently thought was a good idea.
On Mon, Apr 04, 2005 at 12:35:34AM -0700, Daniel Quinlan wrote:
We only have about 40 bugs remaining, a large number of which can be
moved forward to 3.2.0, 3.1.1, or Future. I whacked about a dozen
bugs over the weekend. ;-)
A few open issues and questions:
* History plugin: I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
I'm cleaning up the fault-handling in mass-check a bit for some of my
own scripting. My main question: should ArchiveIterator return a fatal
error (that would propagate up) if a target is not accessible? All of
those
BTW, I think we should try to get the code that relies on
Storable out of SpamAssassin for 3.1.0. why?
Because as far as I can see we still have a lot of users reporting
problems with spamd hanging, and (last I heard) it looked like Storable
was the issue.
We've hacked around it with some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Thu, Apr 14, 2005 at 12:07:00PM -0700, Justin Mason wrote:
On top of that, I don't see exactly *why* Storable is required to
implement what it's doing (keeping a copy of the basic system-wide Conf
object's data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Matt Sergeant wrote:
I didn't think you could do that because in newer versions of Net::DNS
the id is a lexical variable. The only way to reinitialise it is to
reload the module.
If I remember it correctly, Justin's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Apr 26, 2005 at 12:34:20PM -0700, Justin Mason wrote:
I have a hard time figuring out how Net::DNS could be using the same
counter value, since it just uses rand() to seed it and counts
consecutively from
-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-4390-1114614472-0001-2
Content-Type: text/plain; charset=us-ascii
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Theo Van Dinter [EMAIL PROTECTED] writes:
Arguably, then, shouldn't we do a new score generation run for 3.0.3?
As long as hell has frozen over, I have no problem with that.
yeah, I think we can afford a shortcut here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 -- both look good to me.
- --j.
Michael Parker writes:
Howdy,
I've generated the tarballs for the 3.0.3 release. Please download
and test for release. Once we have three +1s I'll move the files over
to dist and upload to CPAN, then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Wed, Apr 27, 2005 at 06:24:40PM -0500, Michael Parker wrote:
There actually have been 3 +1s, quinlan's just hasn't made it to the
list yet. I've already moved the files over to dist.
So yeah, this is what happened
-0700, Justin Mason wrote:
And strongly +1 on votes on the list *only*. The IRC channel is
nice, but we're not all there ;)
I think it's a shame that IRC has become less useful for developers.
It used to be a very good tool for everyone. Evidently Daniel hasn't
been able to send his
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Thu, Apr 28, 2005 at 11:41:16AM -0400, Theo Van Dinter wrote:
But otherwise, I agree with Warren completely. I wanted to get the patch
in for 3.0.3 because it was trivial and the release wasn't complete at
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
On Thu, Apr 28, 2005 at 10:17:07AM -0700, Justin Mason wrote:
I'm with Theo on this one -- I by no means consider 4287 a worthwhile
reason to go to the bother of cutting a 3.0.4. and it *is* a bother!
4287 can get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Do we actually use the Mail-SpamAssassin-current* files? If not, do
they serve any other purpose?
check out the links in the build/README doc -- they're recommended there
by an ASF document on how /dist should be laid out.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
165354 jm if (sysopen ($tmpfile, $reportfile,
O_RDWR|O_CREAT|O_EXCL, 0600))
165354 jm {
165354 jm last;
165354 jm }
last can't be used in a do, at least according to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
This needs PMC votes to change it from draft to official status and make
what it says policy. No reason to do this PMC vote out of the public
view, though.
http://wiki.apache.org/spamassassin/ReleasePolicy
I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
OK, I do not agree with this. in my opinion, a release number is only
burned in stone once the file is announced, uploaded to CPAN, etc.
I'd prefer to avoid burning too early
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes:
see my other mail; -0.5 right now.
Still?
+1 now ;)
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: quinlan
Date: Tue May 3 19:31:07 2005
New Revision: 168050
...
don't allow _ since that's not allowed in hostnames
I'm wondering if this is a good idea?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
don't allow _ since that's not allowed in hostnames
[EMAIL PROTECTED] (Justin Mason) writes:
I'm wondering if this is a good idea?
Well, it's not allowed in the RFC and SURBL doesn't contain a single _
hostname
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Fred wrote:
There was similar work being done in the past to identify rules to be
grouped into new meta rules, this (w|c)ould achieve similar results.
http://bugzilla.spamassassin.org/show_bug.cgi?id=1363
I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Santerre writes:
- change the domain code in SA to consider the domain a registry like
eu.org or demon.co.uk (let us know and we'll change our code as long
as it makes sense ;-). This means we don't expect blacklist the
entire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
there's been quite a bit of research into N-gram bayesian phrases;
I'd recommend reading the spambayes list archives, the bogofilter
archives, and I think Gordon Cormack covered its accuracy too.
summary: you'll massively expand database size for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Gardiner Myers writes:
Daniel Quinlan wrote:
We can't just add them willy-nilly.
Why not? Treat them like .us -- do two queries.
we don't currently do that. but that may be a good option, actually!
allow url_to_domain to return 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Chan writes:
On Thursday, May 5, 2005, 11:41:11 AM, Justin Mason wrote:
That list does currently have some non-country code domains like:
eu.org
au.com
br.com
cn.com
de.com
de.net
eu.com
[...]
Is SpamAssassin using that list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, can we discuss this?
what is the difference between info() and dbg() with this change?
is there a UI in spamd to enable info() output without dbg() messages?
is warn() still the only way to output if debug is off?
if so, what's the point of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Does anyone have any objection to my checking in the following change? It
makes the code in Dns.pm independent of the format of the key that is used
to check the reply packets so that it will be easier to play with using
... not failures (although they prob should be):
t/spf...[4635] warn: plugin: eval failed: Not an ARRAY
reference at ../blib/lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 207.
t/spf...ok 2/8[4638] warn: plugin: eval failed: Not an
ARRAY reference at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
- if (eval { ( =~ m{$re}); 1; }) {
+ my $evalstr = '( =~ ' . $re . '); 1;';
+ if (eval $evalstr) {
return 1;
}
that's not going to work -- it has to be an interpolation of a var inside
the pattern, as in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] writes:
- if (eval { ( =~ m{$re}); 1; }) {
+ my $evalstr = '( =~ ' . $re . '); 1;';
+ if (eval $evalstr) {
return 1;
}
[EMAIL PROTECTED] (Justin Mason) writes:
that's not going
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason wrote:
Are there tests in the test suite for the redirector usage case btw?
Excuse me if I'm misunderstanding the question in my fog-before-first-coffee
of the morning...
The redirector patterns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Daryl C W O'Shea [EMAIL PROTECTED] writes:
So you'd rather not qr// the regexp (in Conf.pm) and do an eval in PMS
instead? This would allow for modifiers to be included but will be a
little slower.
I'm fine with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Thu, May 12, 2005 at 03:11:49PM +1200, Sidney Markowitz wrote:
I've been seeing that with varying regularity depending on which network
I'm on. It's pretty consistently bad on my home DSL, but works if I run
it again
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
This barfs on /test//
The last version included Quinlan's eval to catch that.
thanks -- reinstated some of your code to fix that ;)
It also barfs on .* (anything without delimiters). The regexp has
to have
due to the addition of spamc.h as a file generated by configure, you need
to do make distclean; perl Makefile.PL; make to rebuild any automatic
checkouts of svn trunk; simply make will not rebuild, as it doesn't
handle dependency info for the configure-generated files, and therefore
won't be able
I'm moving the buildbot master from bugzilla onto our new Solaris zone at
spamassassin.zones.apache.org.
This means that, if you're running a Buildbot slave, you'll need to change
its configuration to use that hostname instead of
bugzilla.spamassassin.org. The easiest way to do this is just to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cliff Stanford writes:
I remember finding something in Bugzilla about version 3 not being
thread-safe currently with a fix pending. I now can't find it.
Anyone know if the current version of Mail::SpamAssassin is thread-safe?
if I recall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
t/regexp_valid..ok 12/24config: invalid regexp for rule test:
foo(bar: Unmatched ( in regex; marked by -- HERE in m/foo( -- HERE bar/
config: invalid regexp for rule test: foo(?{1})bar: Eval-group not allowed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
Just upgraded to the latest trunk (170072) and now I get these:
[14805] info: config: failed to parse line, skipping: use_auto_whitelist 0
[14805] info: config: failed to parse line, skipping: use_pyzor 0
[14805] info:
OK, the hostname has changed again -- please use
buildbot.SpamAssassin.org. if you've already changed them to
SpamAssassin.zones.apache.org, you can leave it at that, since
it's the same host anyway. ;)
--j.
Quick question for anyone who may know -- is a .po (gettext-style)
file more usable for translators out there?
In particular, Ubuntu's Rosetta -- https://launchpad.ubuntu.com/rosetta/
-- uses this format. That looks cool, but I'm curious about other
tools that can be used to edit .po files as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Theo Van Dinter [EMAIL PROTECTED] writes:
Since we've already overloaded the add_facilities() function to also
change level w/ info, we could change it so that one can override
for all the levels. That would make it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 looks good to me!
- --j.
Michael Parker writes:
Howdy, as I've written previously, the LEARN and COLLABREPORT commands
are being replaced by a single TELL command. Here is the latest diff
that implements the TELL command. I'm pretty happy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
I think this is too broad, AWL should work with multiple different db
modules, SDBM_File is in the list of usable ones. I think the better
fix would be to figure out why it isn't picking that up and using it.
-1 for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Here is a quick benchmark to illustrate my point, spamc.old was the revision
immediately before the conf patch, spamc.new is the conf patch revision:
Benchmark: timing 1 iterations of spamc.new, spamc.old...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
+my $fh = IO::File-new_tmpfile();
+open(LOGERR, .fileno($fh)) || die Cannot create LOGERR temp file;
should be I think.
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
I think it's the line that looks for a prefix in Logger.pm.
e.g.
warn foo: bar
will probably get through, but
warn bar
probably will not. untested, just a hunch,
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
@@ -145,11 +145,20 @@
return if $self-{no_resolver};
$self-{sock}-close() if $self-{sock};
- $self-{sock} = IO::Socket::INET-new (
-Proto = 'udp',
-Type = SOCK_DGRAM,
- );
+ my $sock;
+ # find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Does anyone know if we should be able to use the latest version of
Buildbot, 0.6.5 with buildbot.spamassassin.org? I know that I could just
try it, but I don't want to spend time trying to get it to work only to
find that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Justin Mason said:
afaik you can.
Ok, I'll try it. First I'll confirm that I can get the 0.6.2 that I have
installed running again, as I've had it down for a while.
Another question -- Can we have a way of enabling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
I got past the setuid problem but now I don't see my slave appearing in
http://buildbot.spamassassin.org:8010/
I'm trying to run trunk-sidney-cygwin
It got the message from master: attached and then said it was doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Mon, May 23, 2005 at 06:45:12PM -0500, [EMAIL PROTECTED] wrote:
Here's the algorithm:
1 Decode any URL-encoding in the message
2 Un-MIME the message
Wrong order?
3 Scan all parts of the message for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --- Forwarded Message
Date:Mon, 23 May 2005 17:14:57 -0700
From:Brian Warner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Buildbot-devel] buildbot-0.6.6 released
I've just released buildbot-0.6.6, it's available on the
looks like it's related to a recent change on the spamc config
front.
http://buildbot.spamassassin.org:8010/t-solaris-10/builds/6/test/0
failures
http://buildbot.spamassassin.org:8010/t-solaris-10/builds/6/test_3/0
passes, from make disttest when t/data/spamc_blank.cf was NON-existent.
--j.
has returned to the trunk. ;) All buildbots that are online --
t-red-hat-73t-debian-stable t-585thrt-solaris-10
t-sol10-561 t-sidney-fedora3
are now reporting successful builds, make test and make disttest.
http://buildbot.spamassassin.org:8010/
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dale Luck writes:
This is a multi-part message in MIME format.
--_=_NextPart_001_01C5660E.C78170A6
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
SPF has a mode whereby a lookup could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Wed, Jun 01, 2005 at 04:30:31AM -, [EMAIL PROTECTED] wrote:
+if (Mail::SpamAssassin::Util::am_running_on_windows()) {
+ binmode(STDIN); # bug 4363
+ binmode(STDOUT);
+}
Since this is the default on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't think this is random. I *do* see it in your log though ;)
naturally I'm not seeing that on the other build slaves (or here).
why is it picking up debugs in t/spamd_allow_user_rules.t in the first
place? that test does not use -D.
also,
can anyone think of good SpamAssassin projects for this?
I'm a bit stumped ;)
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
[EMAIL PROTECTED] writes:
if (open (IN, .$path)) {
$txt .= join ('', IN);
This seems like memory bloat. Why don't we just stream this into the
configuration parser?
that'd be nice, but I don't think we have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Mon, Jun 13, 2005 at 10:09:16AM -0400, Theo Van Dinter wrote:
On Mon, Jun 13, 2005 at 04:08:00AM -, [EMAIL PROTECTED] wrote:
Hi! This is the ezmlm program. I'm managing the
[EMAIL PROTECTED] mailing list.
Are we ready for a prerelease?Here's all that's remaining in
the 3.1.0 queue:
2307maj P4 TRACKER_ID is no good with foreign (ie. non-English)
lang...
4347maj P4 many config options are not validated
4346maj P5 sa-learn: massive memory usage on large
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
is this some kind of NAT problem? I notice it's affecting Sidney and
Michael's bots only.
Possibly, but it's also some sort of SVN is really down problem.
There also seems to be a mailer problem, multiple copies of
hi all --
it's time to broaden the pool of 3.1.0 testing -- so here's a prerelease.
It's functionally quite close to what 3.1.0 will be, although we haven't
yet done the rescoring mass-checks and Perceptron run, and there
may be one or two more patches going in before the full release.
We'd
how's about moving those over to the Solaris zone soon, before
the mass-checks? get more stuff transitioned off bugzilla.
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
actually, I'd prefer to keep it since 3.0.0 started -- there's a gzipped
old changelog in the distro which lists all changes up to 3.0.0,
so listing from 3.0.0 on in Changes keeps continuity.
- --j.
[EMAIL PROTECTED] writes:
Author: felicity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
64ec405b8ac4c49209fe2be199c9adcf Mail-SpamAssassin-3.1.0pre1.tar.bz2
One question: how did the '-' between '0' and 'p' get left out?
I've always used that formatting for prereleases... if there's another
way, it should
let's get this properly underway... how's about this.
- today to Mon, 2005-06-27:
clean up our corpora, get ready for mass-checking, try out
mass-check to spot any big memory leaks or whatnot.
- Mon, 2005-06-27 to Wed, 2005-07-06:
mass-checks; move to C-T-R?
- Wed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One problem is that we've already added something for those mails in 3.1.0 --
but from the other direction ;)
Namely, Theo wrote a plugin which allows rules to be written which
are then translated into more complex rules, that match the variety
of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, a redo after a little chat -- with an extra optional week at the end.
- - today to Mon, 2005-06-27:
clean up our corpora, get ready for mass-checking, try out mass-check to
spot any big memory leaks or whatnot.
- - Mon, 2005-06-27 to Wed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Tue, Jun 21, 2005 at 07:40:59PM -0700, Justin Mason wrote:
CEAS is on this year on July 21st and 22nd. I'm planning to arrive
Wed evening (the 20th), and leave on Sat (the 23rd)...
Daniel was suggesting a brief
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
me too.
Michael Parker writes:
Theo Van Dinter wrote:
So this brings up the question of: who's planning to goto CEAS?
I keep going back and forth about going, currently leaning towards
not going but ...
I'll be there.
Michael
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Thu, Jun 23, 2005 at 03:26:20PM -0700, Dale Luck wrote:
It appears to me that the link on the website for the spamassassin
download for 3.0.4 in tar.gz format is actual to a tar file instead
of a gzipped tar file.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey -- I presume we won't be going ahead with this schedule, since
nobody's voted, explicitly given a thumbs-up, or updated the
details on how mass-checks now work in 3.1.0...
- --j.
Daniel Quinlan writes:
[EMAIL PROTECTED] (Justin Mason) writes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mads Toftum writes:
On Sat, Jun 25, 2005 at 01:40:38PM -0400, Theo Van Dinter wrote:
As for named, the rc script I wrote up and the symlinks I made in rc3.d are
gone. I recreated them, and named is now back up as well.
I don't think anyone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all --
we're going to be starting the mass-checks for 3.1.0 RSN. These will be
used to generate an up-to-date score set for that release.
If you have a hand-classified set of mail corpora [1], and are able and
willing to run mass-check over
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nix writes:
On Sun, 26 Jun 2005, Theo Van Dinter spake:
On Sat, Jun 25, 2005 at 06:29:44PM -0700, Justin Mason wrote:
Hey -- I presume we won't be going ahead with this schedule, since
nobody's voted, explicitly given a thumbs-up, or updated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sun, Jun 26, 2005 at 03:03:27PM -0700, Justin Mason wrote:
any FPs or FNs you may have missed. Also, request an rsync account
if you haven't already got one.
FYI:
I copied over the nightly accounts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doc Schneider writes:
Theo Van Dinter wrote:
On Tue, Jun 28, 2005 at 07:08:58PM -0700, Justin Mason wrote:
are there different accounts for nightly vs rescoring mass-checks? I
thought they were all the same accounts.
Yes, they're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
strchr() should be fine -- I haven't seen a system that didn't support it,
either. Regarding autoheader et al -- I have no idea why it wants to get
rid of HAVE_LIBSSL, but iirc autoscan is destructive, and only suitable as
a first try which you're
http://freshmeat.net/projects/amavisd-new/?branch_id=41554release_id=200273
'The program is ready for the coming version 3.1 of SpamAssassin.'
which is nice ;)
--j.
OK, for the mass-checks, we need to cut another prerelease, pre2.
I also think we should go R-T-C on the tree. Please vote.
- Vote for the cutting of pre2, a tarball to do mass-checks with.
- Vote to go R-T-C on svn trunk.
(I'm +1 on both)
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Justin Mason wrote:
OK, for the mass-checks, we need to cut another prerelease, pre2.
I also think we should go R-T-C on the tree. Please vote.
- Vote for the cutting of pre2, a tarball to do mass-checks
101 - 200 of 1307 matches
Mail list logo
