Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Theo Van Dinter wrote on Sun, 19 Jun 2005 13:28:29 -0400: Which module are you talking about? I'm assuming the Mail::DomainKeys module. If so, you need to install that from CPAN, it's not part of SA. I'm adding that to the list of optional modules in the INSTALL doc. Yes, Mail::DomainKeys. It seems there is a mixture of plugins that are commented out, some are included in the distribution, some are not. So, there's no way to know from the v310.pre file if that particular plugin is included or not. I think this is confusing. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de http://msie.winware.org
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
wrote on Mon, 20 Jun 2005 15:40:13 -0700: Where's that warning coming from? Perhaps the ä? Yes, thanks for the hint. I removed the file with the German descriptions and all is well. Those custom-language environments are a real trap. I prefer to have it all in en-us on my own server systems, except for the time, but that's usually not administered by me. The interesting part concerning sa is that the warnings only appeared *after* I commented out the hashcash plugin. Unexpected, isn't it? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de http://msie.winware.org
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Theo Van Dinter writes: On Tue, Jun 21, 2005 at 02:32:07PM +0200, Kai Schaetzl wrote: The interesting part concerning sa is that the warnings only appeared *after* I commented out the hashcash plugin. Unexpected, isn't it? The problem is that the translation files don't use the ifplugin bits to correctly limit the descriptions to when the plugin is in use. Can you open a ticket about this? We'll need to fix it before release. BTW I'd be +1 to remove the lint warning about this, replacing it with something (possibly an external script?) that is only run for developer sanity tests. Descriptions being set for non-existent rules is a thoroughly minor issue and hardly has any effect, and scattering ifplugin lines throughout all the translation files will be quite a bit harder to maintain... - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCuETbMJF5cimLx9ARAjfIAKCPHMYID52B7rScF9Wm3vFwV7MBzQCgot9i 5cqjvvInd9cyZqM2muPQnmY= =OXCB -END PGP SIGNATURE-
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Tue, Jun 21, 2005 at 09:48:28AM -0700, Justin Mason wrote: Descriptions being set for non-existent rules is a thoroughly minor issue and hardly has any effect, and scattering ifplugin lines Well, yes, it's minor, but the message only occurs when running --lint. This is something worth noting via --lint, but not any other time. throughout all the translation files will be quite a bit harder to maintain... Yes and no. First, we haphazardly get translations now, so I don't think it'll be harder to deal with. Second, we could put the translation version in the plugin rule file (25_uribl, etc,) and that way there's only 1 section to worry about. -- Randomly Generated Tagline: Bender to Zoidberg: You're looking less nuts, crabby. pgpl2jtHJZhFZ.pgp Description: PGP signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Kai Schaetzl wrote: Theo Van Dinter wrote on Sun, 19 Jun 2005 13:28:29 -0400: Which module are you talking about? I'm assuming the Mail::DomainKeys module. If so, you need to install that from CPAN, it's not part of SA. I'm adding that to the list of optional modules in the INSTALL doc. Yes, Mail::DomainKeys. It seems there is a mixture of plugins that are commented out, some are included in the distribution, some are not. So, there's no way to know from the v310.pre file if that particular plugin is included or not. I think this is confusing. Kai Every single one of the plugins in init.pre and v310.pre are included in the tarball. The plugins are all located in the lib/Mail/SpamAssassin/Plugin directory. Some plugins are commented out by default for licensing or other reasons, but they're all included. Module dependencies aren't included, but that's nothing new, nor non-standard. Daryl
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
I get 139 errors regarding the 70_sare_whitelist.cf entries. from 3.1pre. Has the syntax for whitelist_from_rcvd changed? Ben
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
Larry Rosenman ler@lerctr.org wrote on 06/19/2005 01:46:41 PM: Another one you might want to add to that list: Crypt::OpenSSL::Bignum The pre-req chain for Mail::DomainKeys doesn't req it, but apparently SA 3.1.0pre1 does. LER Yep, ditto here. This was with the last SVN build though. Crypt::OpenSSL::RSA version is 0.21 Jun 15 17:05:32 python spamassassin[16041]: Can't locate Crypt/OpenSSL/Bignum.pm in @INC (@INC contains: ../lib /usr/local/li b/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl/5.8.6/mach /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.6/B SDPAN /usr/local/lib/perl5/5.8.6/mach /usr/local/lib/perl5/5.8.6) at /usr/local/lib/perl5/site_perl/5.8.6/mach/Crypt/OpenSSL/ RSA.pm line 29. Andy
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Mon, Jun 20, 2005 at 09:43:05AM +0200, Bart Verwilst wrote: Does SA 3.1.0 have support for expiring bayes and AWL data? SA 3.0 just keeps filling the mysql databases containing this data endlessly.. My db has a couple of million entries now and still growing, and there is no way to clean em reliably.. Bayes tokens has had expiry since day 1. If that's not expiring, you need to run some debug and find out what's going on. Bayes seen and AWL do not have expiry, though you should be able to delete the seen DB now if you want. -- Randomly Generated Tagline: I love deadlines. I like the whooshing sound they make as they fly by. - Douglas Adams pgpBUTAZmOk7G.pgp Description: PGP signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Ben Hanson wrote: I get 139 errors regarding the 70_sare_whitelist.cf entries. from 3.1pre. Has the syntax for whitelist_from_rcvd changed? Ben This is due to the comments Bob had at the end of each entry, without a # before them. He was going to correct this prior to the 3.1 release. I believe there is an updated version that corrects this available. Daryl
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
The current one from SARE works fine :) And, the latest RDJ has support for all the SARE rules. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US -Original Message- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Monday, June 20, 2005 6:23 PM To: Ben Hanson Cc: users@spamassassin.apache.org Subject: Re: SpamAssassin 3.1.0pre1 PRERELEASE available! Ben Hanson wrote: I get 139 errors regarding the 70_sare_whitelist.cf entries. from 3.1pre. Has the syntax for whitelist_from_rcvd changed? Ben This is due to the comments Bob had at the end of each entry, without a # before them. He was going to correct this prior to the 3.1 release. I believe there is an updated version that corrects this available. Daryl
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
I installed on CentOS which I have never done before. Everything is okay
except for one thing. I get
[28414] warn: config: warning: description exists for non-existent rule
HASHCASH_HIGH
+ 7 ever HASHCASH rule warnings in --lint
all the other output is exactly like on my other non-CentOS systems.
Hashcash is disabled and there's no such rule in /etc/mail/spamassassin.
grep in /usr/share/spamassassin shows the following output which seems to
be quite ok:
25_hashcash.cf:header HASHCASH_HIGH
eval:check_hashcash_value('26', '')
25_hashcash.cf:tflags HASHCASH_HIGH nice userconf
25_hashcash.cf:describe HASHCASH_HIGHContains valid Hashcash token
(25 bits)
30_text_de.cf:lang de describe HASHCASH_HIGH Enthält korrekte
Hashcash-Kennzeichnung ( 25 bits)
50_scores.cf:score HASHCASH_HIGH -5.000
Where's that warning coming from?
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de http://msie.winware.org
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
Kai Schaetzl wrote:
30_text_de.cf:lang de describe HASHCASH_HIGH Enthält korrekte
Hashcash-Kennzeichnung ( 25 bits)
50_scores.cf:score HASHCASH_HIGH -5.000
Where's that warning coming from?
Perhaps the ä?
--
Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -emap{y/a-z/l-za-k/;print}shift Jjhi pcdiwtg Ptga wprztg,
Re[2]: SpamAssassin 3.1.0pre1 PRERELEASE available!
Hello Ben, Monday, June 20, 2005, 6:50:46 AM, you wrote: BH I get 139 errors regarding the 70_sare_whitelist.cf entries. from BH 3.1pre. Has the syntax for whitelist_from_rcvd changed? BH Ben Which version of 70_sare_whitelist.cf? What are the errors? Yes, the syntax for whitelist_from_rcvd changed (has tightened up some), but the file that has been published since early June should be in the new format. Bob Menschel
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Justin Mason wrote on Sat, 18 Jun 2005 15:33:25 -0700: Kai, are you sure it's reading the same init.pre file you think it is?run with -D and check. note that if you run SpamAssassin from the build dir, it'll pick up the init.pre file in rules rather than your system one, I think. You are right, it grabs the one from /etc/... and then continues in ./rules. I overlooked that when I saw that it was getting all the other files from the right locations. I did a make install now. I have it running with a MailScanner setup of a few months ago. I enabled DomainKeys and found that this module isn't included. Is this only for this pre-release? If not, I suggest adding that information to all modules mentioned in v310.pre but are not included. Kai -- Kai Schtzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de http://msie.winware.org
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Justin Mason wrote: 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. Thanks for this Justin. I cannot find where to put the dcc user options like dcc_dccifd_path. If I leave them in sysconfdir/local.cf, I get info messages about skipping dcc. Thanks, Alex
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Sun, Jun 19, 2005 at 10:11:43AM -0500, Alex S Moore wrote: I cannot find where to put the dcc user options like dcc_dccifd_path. If I leave them in sysconfdir/local.cf, I get info messages about skipping dcc. Did you enable the DCC plugin? Due to license issues with DCC, we had to disable the plugin by default. -- Randomly Generated Tagline: They were printing out the damn bible ... Jesus Christ! - Matt pgpHmySfAYmTQ.pgp Description: PGP signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Sun, Jun 19, 2005 at 11:32:05AM +0200, Kai Schaetzl wrote: I did a make install now. I have it running with a MailScanner setup of a few months ago. I enabled DomainKeys and found that this module isn't included. Is this only for this pre-release? If not, I suggest adding that information to all modules mentioned in v310.pre but are not included. Which module are you talking about? I'm assuming the Mail::DomainKeys module. If so, you need to install that from CPAN, it's not part of SA. I'm adding that to the list of optional modules in the INSTALL doc. -- Randomly Generated Tagline: Mac - A computer with training wheels you can't take off. pgpn7gjMF5df0.pgp Description: PGP signature
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
Another one you might want to add to that list: Crypt::OpenSSL::Bignum The pre-req chain for Mail::DomainKeys doesn't req it, but apparently SA 3.1.0pre1 does. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US -Original Message- From: Theo Van Dinter [mailto:[EMAIL PROTECTED] Sent: Sunday, June 19, 2005 1:28 PM To: users@spamassassin.apache.org Subject: Re: SpamAssassin 3.1.0pre1 PRERELEASE available! On Sun, Jun 19, 2005 at 11:32:05AM +0200, Kai Schaetzl wrote: I did a make install now. I have it running with a MailScanner setup of a few months ago. I enabled DomainKeys and found that this module isn't included. Is this only for this pre-release? If not, I suggest adding that information to all modules mentioned in v310.pre but are not included. Which module are you talking about? I'm assuming the Mail::DomainKeys module. If so, you need to install that from CPAN, it's not part of SA. I'm adding that to the list of optional modules in the INSTALL doc. -- Randomly Generated Tagline: Mac - A computer with training wheels you can't take off.
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Sun, Jun 19, 2005 at 04:02:11PM -0400, Larry Rosenman wrote:
It showed up when I enabled Mail::DomainKeys, so it may be that
In the way SA is using it, FWIW.
Doing some digging, DK uses Crypt::OpenSSL::RSA, which has in it:
BEGIN { eval { require Crypt::OpenSSL::Bignum; }; }
All I can say is that RSA 0.18 doesn't complain that I don't have Bignum
installed on my box.
--
Randomly Generated Tagline:
Six simple words: I'm not gay, but I'll learn.
-- Homer Simpson
I Love Lisa
pgpV9ADJV2W3l.pgp
Description: PGP signature
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
Theo Van Dinter wrote:
On Sun, Jun 19, 2005 at 04:02:11PM -0400, Larry Rosenman wrote:
It showed up when I enabled Mail::DomainKeys, so it may be that In
the way SA is using it, FWIW.
Doing some digging, DK uses Crypt::OpenSSL::RSA, which has in it:
BEGIN { eval { require Crypt::OpenSSL::Bignum; }; }
All I can say is that RSA 0.18 doesn't complain that I don't have
Bignum installed on my box.
$ grep Bignum /var/log/maillog
Jun 19 13:35:55 lerami.lerctr.org spamassassin[13366]: Can't locate
Crypt/OpenSSL/Bignum.pm in @INC (@INC contains: lib ../lib
/opt/lib/perl5/site_perl/5.8.3/i386-unixware-thread-multi
/opt/lib/perl5/site_perl/5.8.3
/opt/lib/perl5/5.8.3/i386-unixware-thread-multi /opt/lib/perl5/5.8.3
/opt/lib/perl5/site_perl/5.8.0/i386-unixware-thread-multi
/opt/lib/perl5/site_perl/5.8.0 /opt/lib/perl5/site_perl) at
/opt/lib/perl5/site_perl/5.8.3/i386-unixware-thread-multi/Crypt/OpenSSL/RSA.
pm line 29.
$
Is what tripped me to it :(
Spamassassin --lint did **NOT** complain :(
FWIW.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Sun, Jun 19, 2005 at 05:03:27PM -0500, Alex S Moore wrote: I cannot find where to put the dcc user options like dcc_dccifd_path. If I leave them in sysconfdir/local.cf, I get info messages about skipping dcc. Yes, I did enable the DCC plugin. Running spamassassin with the debug option shows that DCC cannot be found. I understand and agree with your choice to disable by default. The problem is that I do not know where to define critical options to run DCC. local.cf is still the place to specify options. What exactly is shown when running in debug mode? If you run spamassassin -D --lint, you should see something like: [...] [29738] dbg: config: read file /etc/mail/spamassassin/v310.pre [...] [29751] dbg: plugin: loading Mail::SpamAssassin::Plugin::DCC from @INC [29751] dbg: dcc: network tests on, registering DCC [29751] dbg: plugin: registered Mail::SpamAssassin::Plugin::DCC=HASH(0x1eb74f0) If there are actual errors, I'd look to make sure the install was completed successfully, permissions are set right, etc. -- Randomly Generated Tagline: Energizer Bunny Arrested -- Charged with Battery. pgpFMICRvkYZF.pgp Description: PGP signature
RE: SpamAssassin 3.1.0pre1 PRERELEASE available!
Theo Van Dinter wrote:
On Sun, Jun 19, 2005 at 04:02:11PM -0400, Larry Rosenman wrote:
It showed up when I enabled Mail::DomainKeys, so it may be that In
the way SA is using it, FWIW.
Doing some digging, DK uses Crypt::OpenSSL::RSA, which has in it:
BEGIN { eval { require Crypt::OpenSSL::Bignum; }; }
All I can say is that RSA 0.18 doesn't complain that I don't have
Bignum installed on my box.
Seems I have Crypt::OpenSSL::RSA 0.21.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Fri, Jun 17, 2005 at 10:05:09PM -0700, Kenneth Porter wrote: --On Friday, June 17, 2005 7:56 PM -0700 Justin Mason [EMAIL PROTECTED] wrote: URL: http://SpamAssassin.apache.org/devel/ How about including a link on the regular download page to the devel page? I usually go there first when looking for a new version. It should probably go near the end, but before Old releases. Well, arguably, if you're not on one of the mailing lists, you shouldn't be installing this. :-) Please don't use the pre-release on a production server (obviously). Since the scores haven't been adjusted, you will likely get FPs or FNs beyond what you would usually expect. -- Duncan Findlay signature.asc Description: Digital signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Fri, Jun 17, 2005 at 07:56:29PM -0700, Justin Mason wrote: 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 really appreciate it if you could take this for a spin and (possibly) spot any issues... It should be *quite* stable, but it hasn't seen much action in really large sites yet, so a little caution is advisable. URL: http://SpamAssassin.apache.org/devel/ you may have to wait for a mirror update before the files appear, it seems! md5sum of archive files: 64ec405b8ac4c49209fe2be199c9adcf Mail-SpamAssassin-3.1.0pre1.tar.bz2 612987472203c85b34ac0f9715fe4dd0 Mail-SpamAssassin-3.1.0pre1.tar.gz 726bad32f42715c2256ef4ab90747641 Mail-SpamAssassin-3.1.0pre1.zip sha1sum of archive files: 00c05495f146e0fcfaecad29a86d83be4e34c8ce Mail-SpamAssassin-3.1.0pre1.tar.bz2 a9bd82d9eeb92e127e14a1f0066699004544923b Mail-SpamAssassin-3.1.0pre1.tar.gz fce976b6ff153de29b45639538e5fab65d0474c1 Mail-SpamAssassin-3.1.0pre1.zip (ps: also, if you're planning to submit mass-check results, now's the time to start getting those corpora in order! details on the wiki.) (pps: devs, I left the IS_DEVEL_BUILD line uncommented deliberately. it is one. ;) --j. Any new tests available? -- Member - Liberal International This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] God Queen and country! Beware Anti-Christ rising! nk.ca started 1 June 1995
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Friday 17 June 2005 19:56, Justin Mason wrote: We'd really appreciate it if you could take this for a spin and (possibly) spot any issues... Didn't actually take it for a spin yet but noticed the following in running makefile on a RH 7.2 server: checking module dependencies and their versions... Net::Ident::_export_hooks() called too early to check prototype at /usr/lib/perl5/site_perl/5.8.1/Net/Ident.pm line 29. The tests for Net::Ident 1.20 produced the same result. The only reference I could find regarding this error is that the module hasn't been updated since 1999 and the tests fail as a result. Don't know if it's the age of my os or what just yet Also one other question why does make test skip t/bayessql by default? I have a working bayes sql data base. Ed . . . . . . . . . . . . . . . Randomly generated quote: The old believe everything, the middle-aged suspect everything, the young know everything. -Oscar Wilde
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Failure!! It does not work with milter-spamc older version. THAT needs to be fixed. I refer to the last milter-spamc which was free. -- Member - Liberal International This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] God Queen and country! Beware Anti-Christ rising! nk.ca started 1 June 1995
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Ok, make test was okay. Before make install I ran a ./spamassassin -D --lint and wonder about the following: - dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash Hashcash is commented out in our init.pre! - warn: config: failed to parse, now a plugin, skipping: ok_languages en de fr en pt how to activate that plugin? - UPGRADE says Note for Users Upgrading from SpamAssassin 3.0.x and then follows a list of hints for upgrading from 2.6 TO 3.0.x. - the score for that lint is quite high (2.351) compared to the score coming from the installed sa (- 1.9). Could this be better once it's actually installed (and /usr/share/spamassassin overwritten with new scores)? With such a high score I'm reluctant to test it in production (though it's only for our own mail on that machine). Kai -- Kai Schtzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de http://msie.winware.org
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Ed Kasky wrote: Also one other question why does make test skip t/bayessql by default? I have a working bayes sql data base. Because not everyone has it set up. See t/config.dist and create a t/config. It will also help avoid having to answer the setup questions each time perl Makefile.PL is run. Michael signature.asc Description: OpenPGP digital signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
The Doctor wrote: Failure!! It does not work with milter-spamc older version. THAT needs to be fixed. I refer to the last milter-spamc which was free. SARCASM Thank you for the very thorough bug report about his problem. It has all of the details needed to diagnose and fix the problem right away. /SARCASM Michael signature.asc Description: OpenPGP digital signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Kai Schaetzl wrote: Ok, make test was okay. Before make install I ran a ./spamassassin -D --lint and wonder about the following: - dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash Hashcash is commented out in our init.pre! There is a new .pre file, I think it's v310.pre, you'll need to comment it out of there as well and removing it from init.pre all togther is probably the way to go. This is something that needs to be addressed in the UPGRADE file (see below). - warn: config: failed to parse, now a plugin, skipping: ok_languages en de fr en pt how to activate that plugin? See v310.pre and uncomment. - UPGRADE says Note for Users Upgrading from SpamAssassin 3.0.x and then follows a list of hints for upgrading from 2.6 TO 3.0.x. The UPGRADE file still needs some work. In fact, if someone wanted to start a wiki page or even better open a bug and start providing items/patches for UPGRADE that would be VERY helpful. - the score for that lint is quite high (2.351) compared to the score coming from the installed sa (- 1.9). Could this be better once it's actually installed (and /usr/share/spamassassin overwritten with new scores)? With such a high score I'm reluctant to test it in production (though it's only for our own mail on that machine). 3.1 has not had a scoring run yet, that is coming soon, so scores are likely to be a little wonky for a bit. Michael signature.asc Description: OpenPGP digital signature
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
On Sat, 18 Jun 2005, Michael Parker wrote: Ed Kasky wrote: Also one other question why does make test skip t/bayessql by default? I have a working bayes sql data base. Because not everyone has it set up. See t/config.dist and create a t/config. It will also help avoid having to answer the setup questions each time perl Makefile.PL is run. Now that's just way too obvious That worked for testing the sql bayes. Thanks. t/bayessql..ok I am stil lost on the Net::Ident error though. Any idea if it's anything to worry about if I am not utilizing SSL between spamc and spamd? Ed . . . . . . . . . . . . . . . Randomly generated quote: Everyone has a right to be stupid. Some just abuse the privilege.
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
Duncan Findlay [EMAIL PROTECTED] writes: Please don't use the pre-release on a production server (obviously). Since the scores haven't been adjusted, you will likely get FPs or FNs beyond what you would usually expect. I have to disagree with you on this one, Duncan. I haven't run the test yet for 3.1, but FP/FN rate has always been *better* than the old release even *before* running the perceptron to optimize the rules. Running on a production server takes some guts, though, but most of the SA developers have been using it on their own personal email servers for months. ;-) Daniel -- Daniel Quinlan http://www.pathname.com/~quinlan/
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ed Kasky writes: On Sat, 18 Jun 2005, Michael Parker wrote: Ed Kasky wrote: Also one other question why does make test skip t/bayessql by default? I have a working bayes sql data base. Because not everyone has it set up. See t/config.dist and create a t/config. It will also help avoid having to answer the setup questions each time perl Makefile.PL is run. Now that's just way too obvious That worked for testing the sql bayes. Thanks. t/bayessql..ok I am stil lost on the Net::Ident error though. Any idea if it's anything to worry about if I am not utilizing SSL between spamc and spamd? totally harmless, only occurs with --lint, and we can't fix it; it's a bug in Net::Ident. - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCtKDwMJF5cimLx9ARAn0WAKC4AsrL+8apPvIGGLv0DCIb4ABvJACdF8xo myrHqWQ11hMKka6yKO67gwo= =1Z1B -END PGP SIGNATURE-
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Parker writes: Kai Schaetzl wrote: Ok, make test was okay. Before make install I ran a ./spamassassin -D --lint and wonder about the following: - dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash Hashcash is commented out in our init.pre! There is a new .pre file, I think it's v310.pre, you'll need to comment it out of there as well and removing it from init.pre all togther is probably the way to go. This is something that needs to be addressed in the UPGRADE file (see below). actually it's only in init.pre, not in v310.pre (because it wasn't a new plugin in 3.1.0). Kai, are you sure it's reading the same init.pre file you think it is?run with -D and check. note that if you run SpamAssassin from the build dir, it'll pick up the init.pre file in rules rather than your system one, I think. - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCtKE1MJF5cimLx9ARAlXNAKChgTGsgxKwMxDZezawNY7XG0Gt+QCgq54X V4iaOSjyoG302XhvtU1P3IU= =Sqgz -END PGP SIGNATURE-
SpamAssassin 3.1.0pre1 PRERELEASE available!
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 really appreciate it if you could take this for a spin and (possibly) spot any issues... It should be *quite* stable, but it hasn't seen much action in really large sites yet, so a little caution is advisable. URL: http://SpamAssassin.apache.org/devel/ you may have to wait for a mirror update before the files appear, it seems! md5sum of archive files: 64ec405b8ac4c49209fe2be199c9adcf Mail-SpamAssassin-3.1.0pre1.tar.bz2 612987472203c85b34ac0f9715fe4dd0 Mail-SpamAssassin-3.1.0pre1.tar.gz 726bad32f42715c2256ef4ab90747641 Mail-SpamAssassin-3.1.0pre1.zip sha1sum of archive files: 00c05495f146e0fcfaecad29a86d83be4e34c8ce Mail-SpamAssassin-3.1.0pre1.tar.bz2 a9bd82d9eeb92e127e14a1f0066699004544923b Mail-SpamAssassin-3.1.0pre1.tar.gz fce976b6ff153de29b45639538e5fab65d0474c1 Mail-SpamAssassin-3.1.0pre1.zip (ps: also, if you're planning to submit mass-check results, now's the time to start getting those corpora in order! details on the wiki.) (pps: devs, I left the IS_DEVEL_BUILD line uncommented deliberately. it is one. ;) --j.
Re: SpamAssassin 3.1.0pre1 PRERELEASE available!
--On Friday, June 17, 2005 7:56 PM -0700 Justin Mason [EMAIL PROTECTED] wrote: URL: http://SpamAssassin.apache.org/devel/ How about including a link on the regular download page to the devel page? I usually go there first when looking for a new version. It should probably go near the end, but before Old releases. (I liken this to Mozilla's Releases page http://www.mozilla.org/releases/ where betas are listed after the current release.)
