-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(using dev as a backup channel.)
Hey Fred -- I don't know what's going on here -- looks like your secondary
MX can't talk to the primary? anyway, fyi.
this is an old mail from last week, so can probably be ignored at
this stage anyway ;)
- --j.
- ------- Forwarded Message
Date: Mon, 21 Nov 2005 13:51:03 -0500
From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Returned mail: see transcript for details
This is a MIME-encapsulated message
- --jALGOIge059867.1132599063/mx02.i-is.net
The original message was received at Wed, 16 Nov 2005 13:15:48 -0500 (EST)
from dogma.boxhost.net [195.218.96.101] (may be forged)
----- The following addresses had permanent fatal errors -----
<[EMAIL PROTECTED]>
----- Transcript of session follows -----
<[EMAIL PROTECTED]>... Deferred: Operation timed out with smtp.i-is.com.
Message could not be delivered for 5 days
Message will be deleted from queue
- --jALGOIge059867.1132599063/mx02.i-is.net
Content-Type: message/delivery-status
Reporting-MTA: dns; mx02.i-is.net
Arrival-Date: Wed, 16 Nov 2005 13:15:48 -0500 (EST)
Final-Recipient: RFC822; [EMAIL PROTECTED]
Action: failed
Status: 4.4.7
Last-Attempt-Date: Mon, 21 Nov 2005 13:51:03 -0500 (EST)
- --jALGOIge059867.1132599063/mx02.i-is.net
Content-Type: message/rfc822
Return-Path: <[EMAIL PROTECTED]>
Received: from dogma.boxhost.net (dogma.boxhost.net [195.218.96.101] (may be fo
rged))
by mx02.i-is.net (8.12.11/8.12.11) with ESMTP id jAGIERSo071859
for <[EMAIL PROTECTED]>; Wed, 16 Nov 2005 13:15:48 -0500 (EST)
(envelope-from [EMAIL PROTECTED])
Received: from radish.jmason.org (localhost [127.0.0.1])
by dogma.boxhost.net (Postfix) with ESMTP id DB6DE310016
for <[EMAIL PROTECTED]>; Wed, 16 Nov 2005 17:49:39 +0000 (GMT)
Received: from jmason.org (localhost [127.0.0.1])
by radish.jmason.org (Postfix) with ESMTP id 06C0D59001B;
Wed, 16 Nov 2005 09:48:40 -0800 (PST)
To: "Fred" <[EMAIL PROTECTED]>
Cc: "Justin Mason" <[EMAIL PROTECTED]>
Subject: Re: Request for information on rules sub-project
In-Reply-To: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED] (Justin Mason)
X-Gpg-Key-Fingerprint: 1368 71CE 3627 9CD3 FA1B 0B63 3091 7972 298B C7D0
Date: Wed, 16 Nov 2005 09:48:40 -0800
Sender: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
X-HELO: dogma.boxhost.net
X-HOST: dogma.boxhost.net
X-RELAY: 195.218.96.101
X-Spam-Score: 0.53 () FH_MX02_IIS,FM_SHORTMSG_LINK,IISDATED_11_15_2005
X-Scanned-By: MIMEDefang 2.53 on 66.103.234.5
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fred writes:
> Justin Mason wrote:
> > hi Fred -- good to hear from you!
> >
> > OK, if you're keen to get stuck in, the next step is to get set up as
> > a SpamAssassin committer, in other words get an account so you can
> > check in files into SVN.
> >
> > Let me get started on that end of things for you.
> >
> > (I won't check that rule in btw -- don't want to steal your thunder ;)
>
> Justin,
> Ok I am using Tortousie SVN on Win32, it seems to handle the job for SARE so
> I'm guessing it'll work the same for you folks. Being a committer gives me
> the ability to check in rules to a sandbox or are you talking about allowing
> me access to check in rules in the 70_testing.cf file in the main sources?
Well, we've removed the 70_testing.cf file in the main sources entirely;
that model (of keeping the testing rules in the main source dir) has
become obsolete as part of this rules project stuff, as it just didn't
scale well enough. It's been replaced by the sandboxes idea.
Yep, I think TortoiseSVN should work perfectly; afaik the ASF have people
using that tool on other projects.
> Just curious where this is going, it doesn't matter to me either way. I
> also have a corpus of 190k spam and 10k ham, I know it's kinda lop-sided but
> I'm trying to get more ham in my diet ;) I'm running an automatic
> mass-checking facility with this corpus, it accepts e-mails, mass-checks the
> rules attached and sends an e-mail back with the results. I'm sure you've
> seen Bob's mass-check script..
actually I don't know if I have recently. it'd be handy if I could, since
I was just about to reimplement that wheel... ;)
Anyway, as to where it's going -- if you read the archives of the dev
list, and the wiki pages around RulesProjectPlan, that's where it was all
hashed out over the past couple of months. The current status is, there's
now an auto-mass-check facility at the ASF as described at
PreflightBuildBot. That'll mass-check all rules as they are checked into
SVN, produce freqs charts, measure their performance, overlap, generate
score maps, etc. Then it also runs them against everyone's (much larger)
corpora on a nightly basis, and with --net on a weekly basis.
That's basically working now, and in use.
We still have a couple of todo items though:
- defining our promotion criteria for rules
- mark rules visibly by how they do against our promotion criteria
in the rule-qa app
- a mail-handling script to extract mail-submitted rule attachments
> I have been very active in the rules writing process for the past 2 years,
> it would be my pleasure to contribute directly.
>
> Let me know what my next step is at this point.
> Thanks for your time,
I think the next step is still to get an account. While I'm planning
to get that mass-check-by-email script up adn running soonish,
to be honest I think it's easier to do it via svn anyway.
- - --j.
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDe3D4MJF5cimLx9ARAsRBAJ0VpBeGDKCIPgGKbRHpJT/wkTo4XQCgmrck
5UzVKngzsAnOYJWBWJXWoZk=
=FQ4W
- -----END PGP SIGNATURE-----
- --jALGOIge059867.1132599063/mx02.i-is.net--
- ------- End of Forwarded Message
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDghxEMJF5cimLx9ARAv3jAJ44bfqL2cu/RPZ4ixPy1E9TEZjygQCdGg11
DzG5Sbu3FFujdMZ6tcQWW/M=
=Prx6
-----END PGP SIGNATURE-----
