-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Justin Mason wrote:
Michael Parker writes:
Gerard Earley wrote:
I am debating building a logging tool to record the spamassassin scan
results to a MySQL DB.
I've had this on my TODO list for awhile, glad to see someone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
BTW did anything ever come of this? also what do the plots look
like? (I'm sure I saw them at the time, but it'd be nice to
get them on a wiki.)
PS: the ham misclassification constant factor alpha maps to TCR's
lambda I think.
- --j.
Daniel
Robert Menschel writes:
Justin, could you repeat a mass-check and that analysis on this rule,
which I'm willing to sacrifice for the sake of science? Not
necessarily now, but a month or two from now?
headerSARE_SUBJ_MED_USESubject =~ /\w{3}\sused .+ (?:along
Hey folks --
I've come up with an idea to use BuildBot for the fast-turnaround
mass-checking, instead of a mailing list. The writeup is here:
http://wiki.apache.org/spamassassin/RulesProjBuildBot
Please let me know what you think!
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
Justin Mason wrote:
Hey folks --
I've come up with an idea to use BuildBot for the fast-turnaround
mass-checking, instead of a mailing list. The writeup is here:
http://wiki.apache.org/spamassassin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Thielen writes:
Justin Mason wrote:
Daryl C. W. O'Shea writes:
Please let me know what you think!
Sounds good, but I think the limited (and relatively static?) corpus may
be an issue for rule development aimed at catching new spam
So, the first step of the rules project -- the sandbox idea, and the build
scripts that compile code from the sandbox into the rules directory,
is pretty much done, as
http://wiki.apache.org/spamassassin/RulesProjectPlan notes.
If you're running an existing auto-mass-checker or buildbot slave,
jmason so, part of the rules project thing is that it's a different SVN
tree, not tied to the code
jmason (this will allow us to use rules-project stuff with older
releases as well)
jmason but it also means that we had to split the current ruleset into
stuff that was code-tied, dependent on
Loren Wilton writes:
let me know what you all think.
I had a little trouble following this message. Part of the problem is I'm
not positive I know what you mean by compiled rules. (Or I'm positive I
don't know, your choice. :-)
OK, so here's what I've done so far.
Rules files are now
Robert Menschel writes:
Wednesday, October 5, 2005, 6:11:26 PM, you wrote:
JM Daryl C. W. O'Shea writes:
Sounds good, but I think the limited (and relatively static?) corpus may
be an issue for rule development aimed at catching new spam signs.
JM A static-ish ham corpus isn't a big
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey,
yep, this is definitely in flux ;) If you want a working system,
it may be best to stick with 3.1.0 until the buildbot's not
reporting test failures at least.
- --j.
OpenMacNews writes:
hi justin,
re: Re: need to add a new class of
This is a heads-up of an impending change that could cause trouble, coming
soon in svn trunk.
Due to the rules project work, the trunk/rules directory is now no
longer considered a source tree -- instead it's an output directory for
compiled files from rulesrc and rulescode. As such, make clean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
agreed with Sidney to be honest; I myself have run into serious
utf-8 bugs with perl 5.8.0 that do not occur with other versions.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Theo Van Dinter wrote:
So I'd like to make a new list (not sure about name) where we can have
discussions/send announcements/etc that are directly relevent to those
folks. Thoughts/votes? (do we need to vote for a new
for John -- in case you've missed it, buildbot is still reporting failures
in this test, for one buildbot slave only.
http://spamassassin.zones.apache.org:8010/
http://spamassassin.zones.apache.org:8010/t-debian-stable/builds/23/test/0
t/html_utf8.Not found: QUOTE_YOUR =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doc Schneider writes:
I had asked Jason this and he thought I should ask the list.
Also will we (rules project) be getting our own bugzilla? Or, will we
really need that? I currently host the sare list for our own private
rules testing.
as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
You know, I don't know if there'd be a separate bugzilla. good
question... I think the mostly likely thing would be that the rules
project stuff would be under the (existing) Rules component in BZ.
I don't know
attention Theo! ;)
OK, this is odd. I can no longer create a named search in
http://bugzilla.spamassassin.org/query.cgi ... the only options I get at
the bottom of the Advanced Search form are:
Sort results by: [..]
[search button]
x and remember these as my default search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
I was noticing that the previous nightly/weekly run commands I was running:
cd spamassassin-head
rm -f rules/*
svn up
build/mkrules --src rulesrc --out rules
wasn't working anymore since the code rules moved into a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Fri, Oct 14, 2005 at 09:31:29AM -0700, Justin Mason wrote:
OK, this is odd. I can no longer create a named search in
http://bugzilla.spamassassin.org/query.cgi ... the only options I get at
the bottom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Fri, Oct 14, 2005 at 09:51:51AM -0700, Justin Mason wrote:
couldn't/shouldn't you just use make instead of calling build/mkrules
directly? (after all there may be other stuff that make builds.)
I can see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Thu, Oct 13, 2005 at 10:19:03AM -0700, Justin Mason wrote:
By moving the Bugzilla traffic to commits@, we would reduce the volume on
the dev list so that it can be used for that purpose (as well as for the
other
hey --
so, bugzilla is the last remaining service on the
bugzilla.SpamAssassin.org Sonic machine, and (iirc) we had a duplicate
instance pretty much working fine at the ASF.
If this is still the case, why don't we just take the plunge, sync up
one final time, and switch over to the ASF one now?
Theo Van Dinter writes:
So I was prodding around the sandboxes bit, and noticed that mkrules doesn't
copy \d.+\.(?:cf|pm)$ to the rules dir... So it seems that if I wanted some
rules to be put in for testing, I have to name them word.cf or something,
and then they get copied. But if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sun, Oct 16, 2005 at 12:29:35PM -0700, Justin Mason wrote:
If this is still the case, why don't we just take the plunge, sync up
one final time, and switch over to the ASF one now? If there are bugs,
well, we're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Mason writes:
A thought may be that we should do all this stuff at ApacheCon US 2005.
A bunch of the infra guys will be there, as will I (that's the plan anyway),
so it should be easy to get this stuff done if we just sat down
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
Some random comments:
So the idea is that the source code for all rules (apart from the legacy
core and lang sets) remains in the sandbox dirs; in other words, there's
no need to cut and paste and move around rules when
it works very nicely! try it out:
http://buildbot.spamassassin.org:8011/
it isn't yet pushing the results through to the rule-QA user interface at
http://buildbot.spamassassin.org/ruleqa/ , but in the meantime you can see
how fast it is by triggering a build and watching it mass-check 5300
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
agreed. +1 to remove those 2 lines.
- --j.
Daniel Quinlan writes:
Hmmm... why do we strip whitespace from the keys?
This routine is so frequently called, extra work is bad.
Daniel
# Store or retrieve headers from a given MIME object
#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
testing again
hi! this was sent via email. I want to see if it bounces...
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDXTjxMJF5cimLx9ARApcsAKCVA55LThzj4CXUQttxBXuZUoUfqQCffF0z
just to remind everyone -- don't reply by email to bugs sent by
bugzilla-daemon, it's still broken at the moment.
http://issues.apache.org/jira/browse/INFRA-589
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Wed, Oct 26, 2005 at 01:24:30AM -, [EMAIL PROTECTED] wrote:
Author: duncf
Date: Tue Oct 25 18:24:28 2005
New Revision: 328517
URL: http://svn.apache.org/viewcvs?rev=328517view=rev
Log:
Fix typo (Debian
So, this is coming along nicely. ;)
STORY SO FAR:
http://spamassassin.zones.apache.org:8011/ is the main UI -- each time a
checkin occurs in SVN, a set of mass-checks are triggered.
There are 4 mass-checks at the moment: mc-fast, mc-med, mc-slow and
mc-slower. The idea is that the fast one
...are now implemented. see, for example, the changing hitrates for
T_URI_HTML_ONLY in the preflight corpora:
http://buildbot.spamassassin.org/ruleqa/ruleqa?daterev=20051028%2Fr328993rule=T_URI_HTML_ONLYs_detail=1s_graph=over_time
For other rules, click on a rule in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
Hum. Is there any way to configure some default colors for the graph? On a
PC it seems Quicktime prints the thing out, and it is near unreadable. I
see a black square with a straight yellow line in the center and some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton writes:
OK, I think I've fixed that now -- take a look:
Oh yes, MUCH nicer! QT doesn't mess up this display format for me! :-)
- - Different colour lines, are different mass-checks; so by looking at the
locations and sizes
again:
Can anyone provide corpora for the preflight mass-checker?
--j.
It's only myself, daf and bzoetekouw submitting results afaics.
BTW, that new rule-hits-over-time graph is *cool*. Check out these
graphs!
DSBL hit-rate over time:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
Justin Mason wrote:
again:
Can anyone provide corpora for the preflight mass-checker?
--j.
I could provide about 100 messages/day, in an mbox file, scored over 15
without checking them first. If that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Sat, Oct 29, 2005 at 07:28:09PM -0700, Justin Mason wrote:
It's only myself, daf and bzoetekouw submitting results afaics.
BTW, that new rule-hits-over-time graph is *cool*. Check out these
graphs!
What do
Justin Mason writes:
What do the different colours represent? (Could you provide a legend?)
See prev mail on dev -- each mass-checker is a different colour.
I'm hoping to provide a legend, but GD::Graph isn't making it easy ;)
OK, it has one now -- I had to drop GD::Graph, it wasn't up
There's a number of new improvements -- take a look!
http://buildbot.spamassassin.org/ruleqa/ruleqa?daterev=20051030-r329543rule=HTML_MISSING_CTYPEs_detail=1s_g_over_time=1#over_time_anchor
The big one: with urging from Daniel, there's now a smoothed trend curve,
so you can see what the overall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Sun, Oct 30, 2005 at 11:14:29AM -0800, Justin Mason wrote:
Yep, as noted here a few days ago, you need to run
perl Makefile.PL /dev/null
make
as well, in your script, in the main checked-out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rod Begbie writes:
In the last month, I've started using qpsmtpd and I'm rejecting
high-scoring spam at the SMTP transaction, so my spamtraps only
receive spam that scored less than 20 (I figure that's the stuff that
really needs fed into Razor,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Perkel writes:
I added a testimonials page.
http://wiki.apache.org/spamassassin/Testimonials
Made a lot of changes to the Wiki. Hope everyone likes it and hope you
don't all freak out. I did some similar mass edits to the wikis of Exim
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
[Updating /home/corpus/SA/spamassassin-corpora] WARNING:
MY_SERVERS_FOUND: renamed as T_MY_SERVERS_FOUND due to missing T_ =
prefix WARNING: BOUNCE_MESSAGE: renamed as T_BOUNCE_MESSAGE due to
missing T_ pref= ix WARNING:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Mon, Nov 07, 2005 at 01:02:06PM -0800, Justin Mason wrote:
are you using make or running mkrules yourself? because make
takes care of this by passing the name of the MANIFEST file.
make is the better option. ;)
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
it's the same eval call, but a different rule name, and in the
sandbox file only.
I must be missing something. No where in my sandbox do I reference
MPART_ALT_DIFF.
Ah, I had totally the wrong end of the stick, I thought
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
Could someone please outline the process I would go through to propose
rules for testing? (*cough* jmason *cough*) ;-)
I assume it's like this. (In MoinMoin format, suitable for someone to
paste into the Wiki.)
ok, to
hey all --
The next feature needed for the rule-QA app is a visible display of
whether or not a rule hits the promotion criteria (see wiki). We haven't
yet fully defined this, but now's a good time!
Could you all take a look at
http://wiki.apache.org/spamassassin/RulesProjPromotion and followup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey all -- the mass-checks by mail part of the preflight mass-check
system is now up and running!
Documentation here:
http://wiki.apache.org/spamassassin/PreflightByMail
If you'd like to be able to run mass-checks against the preflight corpora,
Dallas L. Engelken writes:
Really? I can reproduce this by putting in the single line:
meta SARE_OBFU_OBLIGATION 0
'meta RULE 0' does not lint, whereas 'meta RULE ()' does. so maybe
that's the quickest fix. are these zero'd metas just left in the
ruleset for backwards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Mon, Nov 21, 2005 at 09:27:52AM -0800, Justin Mason wrote:
Either way though, I do see the problem -- could someone open a bug at the
BZ so we can decide what the correct way to do this should be
and possibly add
for [EMAIL PROTECTED]; Wed, 16 Nov 2005 17:49:39 + (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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander K. Seewald writes:
I've tested just training the NB model within SA, and
to some extent it works, but it is unclear how far you can go with
that... at some point it is likely to break down, and rule weight
have to be adapted.
By the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Mon, Nov 21, 2005 at 01:02:13PM -0500, Dallas Engelken wrote:
an easy solution would be to change the code from:
if (my $result = ( $self-{'tests_already_hit'}-{'__HTML_LENGTH_384'}
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenMacNews writes:
Theo Van Dinter wrote:
On Mon, Nov 21, 2005 at 10:38:28PM -0500, Theo Van Dinter wrote:
It could very well be something perl-version related. My FC machine is
5.8.5,
OSX is 5.8.6. I can reproduce it on 5.8.3.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
On 11/22/05 5:14 PM, Loren Wilton wrote:
I believe the claim was that it produced
reasonable scoring with less effort than the normal method
The less effort is in the procedure to gather the scoring copora from a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doc Schneider writes:
Theo Van Dinter wrote:
On Mon, Nov 21, 2005 at 08:38:05PM -0800, Justin Mason wrote:
well, it's more than that. with a small number of corpora, the
scores will be over-optimised for those people. It's a tricky
problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warren Togami writes:
All patches are now in the 3.0.x branch and the majority of it has been
in real-world testing pushed to Fedora Updates since November 10th. I
think this is good enough testing for a 3.0.5 release.
Normally we'd do at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
for what it's worth, it'd be cleaner to handle this with a plugin
in spamassassin/rules/trunk/sandbox/felicity/ratware.pm --
if you feel like it ;)
- --j.
[EMAIL PROTECTED] writes:
Author: felicity
Date: Tue Nov 29 20:09:08 2005
New Revision:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Monnerie writes:
On Dienstag, 22. November 2005 06:44 Theo Van Dinter wrote:
So basically Justin is 34%, I'm 31%, and everyone else combined is
35%.
I could send you my hand sorted SPAM, if you like. It's only ~3000
SPAMs, but maybe
. Theo noted the relative corpus
sizes in 3.1.0 as a potential issue (nearly 2/3rds is made up of my and
Theo's mail alone).
- --j.
Cheers,
Henry
Justin Mason wrote:
Actually, the problem that Theo is highlighting is not that we don't have
any contributors for rescoring mass-checks using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doc Schneider writes:
I grabbed the tarball for 3.0.5 and when I do 'make test' it gets one
error having to do with SPF.
I've got the latest Net::DNS and Net::SPF::Query
Perl 5.8.6
Yeah, I've been seeing similar in make test here, too; I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Monnerie writes:
On Donnerstag, 1. Dezember 2005 19:21 Justin Mason wrote:
I think if we limit each corpora to a certain max percentage of the
total, we could do this -- e.g. if a corpus makes up more than (100 /
num_contributors
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: felicity
Date: Sun Dec 4 20:46:43 2005
New Revision: 353986
URL: http://svn.apache.org/viewcvs?rev=353986view=rev
Log:
when evaltests move to plugins, the object reference is not what it once was
oh crap. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Mon, Dec 05, 2005 at 11:06:50AM -0800, Justin Mason wrote:
when evaltests move to plugins, the object reference is not what it once
was
oh crap. This may be a bad thing.
Should we define a new API
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Dec 06, 2005 at 12:52:23AM -, [EMAIL PROTECTED] wrote:
- if (-e $entry-{t}) {
+ # jm: we always want to update the output file in case the input
+ # has been changed!
+ if (0 -e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
Some recent checkin seems to have broken the build.
If someone doesn't jump in with a quick fix I'll open this as a bug report.
probably a good idea.
I think it's a bug that's now being exposed by the first plugin file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(NOTE: this is a maintainance release of the 3.0.x branch. If you are
already running the more up-to-date, stable 3.1.0, pay no attention!
This is only for people who are stuck on 3.0.x for some reason.)
We got enough votes for those tarballs we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hack Hawk writes:
Hello,
I've searched google, and the email list archives, but can not find an
answer to these simple questions.
1) Is there a simple rule to determine if there are multiple lines
(CRLF) in the Subject Header? I'd like to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidney Markowitz writes:
When working with Mail::SpamAssassin-new is there support for setting
configuration options directly in code instead of by editing configuration
files? For example, is there a documented way to enable or disable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
Author: dos
Date: Thu Dec 8 19:49:24 2005
New Revision: 355352
URL: http://svn.apache.org/viewcvs?rev=355352view=rev
Log:
today somebody asked me why we thought O came between S and S, everybody's a
critic
ha!
According to the new script build/listpromotable -- should I just
go ahead and promote these?
## --
## Promotable rule: T_GEO_QUERY_STRING
## so=1.000 spc=2.433 hpc=0.000
## rulesrc/sandbox/dos/20_uri.cf
##
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Thu, Dec 08, 2005 at 10:06:12PM -0800, Justin Mason wrote:
According to the new script build/listpromotable -- should I just
go ahead and promote these?
Well, we come back to the original issue I had (which is why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
On 09/12/2005 4:48 PM, Theo Van Dinter wrote:
On Fri, Dec 09, 2005 at 01:40:03PM -0800, Justin Mason wrote:
I do think it's worth promoting them *somewhere*, btw, instead of leaving
them to moulder in the sandboxes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
On 09/12/2005 6:01 PM, Justin Mason wrote:
well, to my mind, I'd prefer to have them sit somewhere that means these
are ready to go, but not yet in a release tarball. There are people
running SVN trunk, for example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
It looks like the pre-flight buildbots are stuck again.
wtf. it looks like python/twisted and solaris don't get on :(
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
On 09/12/2005 6:57 PM, Justin Mason wrote:
Daryl C. W. O'Shea writes:
It looks like the pre-flight buildbots are stuck again.
wtf. it looks like python/twisted and solaris don't get on :(
Solaris must
Hey,
so we're talking over the rule promotion situation, and how sa-update will
work, and we've come to an agreement that having committers manually cut and
paste rules really won't scale, and is too much work.
As a result, here's some notes from a whiteboard session where we're
planning out how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Mason writes:
Hey,
so we're talking over the rule promotion situation, and how sa-update will
work, and we've come to an agreement that having committers manually cut and
paste rules really won't scale, and is too much work.
As a result
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warren Togami writes:
Justin Mason wrote:
PACKAGING (CENTRALISED):
input: SVN, the active set only
output: packages
- TODO: need a password-less method to sign packages
- automated test suite for packages before they're
good news -- make test and make disttest are now passing enough
that http://buildbot.spamassassin.org:8010/ has no failures again.
--j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Myers writes:
Sorry, I was too fast in bumping the minimum version for HTML::Parser to
3.46 and broke the buildbots. I've reverted the change for now.
Could folks please update the buildbots and other trunk-using processes
so that they use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Tue, Dec 13, 2005 at 03:49:44PM -0500, Warren Togami wrote:
Duncan Findlay wrote:
The only problem I see with the above, is that no script should be
overwriting rules that are distributed in a package. So if I
distribute
So we have these requirements:
1. use /var for updates, instead of /etc or /usr
2. sa-update updates must not overwrite any packaged files
3. the user shouldn't have to choose at package-install time whether
they want to use packaged rules, or sa-update rules. (although
conversely,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenMacNews writes:
Justin Mason wrote:
So we have these requirements:
...
I think this should work for everyone?
i presume we'll still have directory override ? i.e., sa-update uses
dirs def'd at configure time, and/or at sa-update time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
On Thu, Dec 15, 2005 at 10:06:36AM -0500, Thomas Schulz wrote:
Just checking on various operating systems. /var/lib seems to exist on
Linux, but not on Solaris, HP-UX or AIX. There is a /var/opt on Solaris
and HP-UX,
Duncan Findlay writes:
On Wed, Dec 14, 2005 at 04:54:54PM -0800, Justin Mason wrote:
So we have these requirements:
1. use /var for updates, instead of /etc or /usr
2. sa-update updates must not overwrite any packaged files
3. the user shouldn't have to choose at package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Myers writes:
The ruleqa site isn't very forthcoming about data on the two existing
rules __FRAUD_DBI and INTERRUPTUS that I'm trying to get rules promoted
to replace. They both show up with zero timing and hit counts.
I suspect you may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Mason writes:
/FRAUD_DBI (without quotes) is what you want, no trailing slash.
e.g.:
http://buildbot.spamassassin.org/ruleqa?daterev=20051214-r356657-ns_defcorpus=onrule=%2FFRAUD_DBIs_zero=ons_detail=checked+g=Change
For some reason
a question that Henry put to me -- should sa-updates of the main ruleset
mandate that GPG verification be used?
Otherwise an attacker that rooted the download server (or a mirror) could
put out faked updates, which would be automatically downloaded by
thousands of servers.
I'm tempted to say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
I see this change locally on the zones box, but not in svn ... If you
need to change things, please edit the spamassassin/dns files in svn,
then do an svn update in /var/named on the zones box.
I'm leaving the change
An issue --
each time an update tarball is created, the zone serial number for the
top level spamassassin.org SOA needs to be incremented.
I'd prefer to avoid this, but I can't really see a way to do so, unless we
explicitly set up updates.spamassassin.org. as a separate zone with a
separate SOA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Mon, Dec 19, 2005 at 07:07:32PM -0800, Justin Mason wrote:
each time an update tarball is created, the zone serial number for the
top level spamassassin.org SOA needs to be incremented.
I'd prefer to avoid
[for the record. let me know if you see anything iffy. based on
http://www.stillhq.com/extracted/gnupg-api/doc/faq.html#q4.13 btw.]
[compile and install gpg 1.4.2 into /local/gnupg-1.4.2]
sudo mkdir /home/updatesd/key
[chown, make writable etc]
/local/gnupg-1.4.2/bin/gpg --homedir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
Err.
On Tue, Dec 20, 2005 at 10:52:54AM -0800, Justin Mason wrote:
[results:]
pub 4096R/5244EC45 2005-12-20
Key fingerprint = 5E54 1DC9 59CB 8BAC 7C78 DFDC 4056 A61A 5244 EC45
uid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Dec 20, 2005 at 12:01:44PM -0800, Justin Mason wrote:
We can still do that, but we'd need to decide how that works. I think
that'd mean:
- 1. edit the main signing key, remove passphrase, move
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
On Tue, Dec 20, 2005 at 03:38:54PM -0800, Kelsey Cummings wrote:
I'd say that future proofing it by using a dedicated zone was the way to go
- no point in locking into something because it looks easy today. It's
really
So, on this issue -- a good way to do this would be to use the MIRRORED.BY
file. Right now, any lines that don't start with http: are ignored, so
we could add something like
gpg-signed 4598349584 http://url/of/GPG.KEYS
ie. a keyid that must be present on the files for the update to be
301 - 400 of 1307 matches
Mail list logo
