You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Mark Martinec <Ma...@ijs.si> on 2013/06/22 02:45:12 UTC
Apache SpamAssassin 3.4.0 release candidate 2 - invitation to testers
This is not a formal announcement, but an invitation to a broader
users community to try the release candidate of the coming release
of Apache SpamAssassin version 3.4.0 .
Preliminary release notes and a link to the package was published
in a posting to the dev@spamassassin.apache.org mailing list:
http://article.gmane.org/gmane.mail.spam.spamassassin.devel/69001
The "call for votes" in the message only applies to project members,
but feedback from wider audience of testers is very much welcome.
The Mail-SpamAssassin-3.4.0-rc2 package is available at:
http://people.apache.org/~kmcgrail/devel/
Rules may be downloaded from the same location, but this is rarely
necessary. A normal procedure is to install the software (the usual
CPAN installation procedure should suffice, but this very much depends
on a platform of choice), then run a 'sa-update' command, which will
find and download appropriate rules to a version-specific directory.
Except for some minor details, the 3.4.0 is compatible with 3.3.2 in
its API and in database formats (but uses a separate directory to store
rules), so it should be possible to switch back and forth between both
versions in a test environment, if a need arises. Still, due diligence is
appropriate: have your backups ready before starting to play with
the new software, especially in a production environment.
Nevertheless, this version has been in production use at several sites
for months, so it should be at least as good as 3.3.2 .
It is expected that the final release will follow shortly, so a quick
response would be appreciated.
Mark
Re: Apache SpamAssassin 3.4.0 release candidate 2 - invitation to testers
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
All but one of the errors seems to relate to spawning spamd. I wonder if this is the same issue we have with freebsd on hudson/Jenkins with freebsd?
Regards,
KAM
Mark Martinec <Ma...@ijs.si> wrote:
>On Saturday 22 June 2013 07:06:43 The Doctor wrote:
>
>> Tweaking needed
>
>> Test Summary Report
>> t/bayesdbm_flock.t (Wstat: 0 Tests: 48 Failed: 1)
>> Failed test: 39
>> t/sa_check_spamd.t (Wstat: 0 Tests: 7 Failed: 5)
>> Failed tests: 1, 3-6
>> t/spamc_B.t (Wstat: 0 Tests: 9 Failed: 1)
>> Failed test: 9
>[...]
>> BSD/OS 4.3.1 running perl 5.16.2
>> BSD/OS 4.3 running perl 5.8.8
>
>
>BSD/OS?
>
>Wikipedia:
> BSD/OS was acquired by Wind River Systems in April 2001.
> Wind River discontinued sales of BSD/OS at the end of 2003,
> with support terminated at the end of 2004.
> Working state: Discontinued
> Source model: source-available, proprietary
> For the open source Unix released by Bill Jolitz, see 386BSD
> 386BSD: Latest stable release 1.0 / November 1994; 18 years ago
>
>
>So how can we test on such platform?
>
>
> Mark
Re: Apache SpamAssassin 3.4.0 release candidate 2 - invitation to testers
Posted by Mark Martinec <Ma...@ijs.si>.
On Saturday 22 June 2013 15:15:20 The Doctor wrote:
> > So how can we test on such platform?
>
> 2) NetBSD, FreeBSD and OpenBSD are akin so some testers
> might be available.
It is regularly in use on FreeBSD (7.2, 8.2, and 9.1),
it has been tested on OpenBSD 5.2, and some time ago
on NetBSD (forgot the version).
> 1) Get an account here I can provide
That would be handy. Please contact me privately.
Should I send a public ssh key?
Mark
Re: Apache SpamAssassin 3.4.0 release candidate 2 - invitation to
testers
Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Sat, Jun 22, 2013 at 11:41:38AM +0200, Mark Martinec wrote:
> On Saturday 22 June 2013 07:06:43 The Doctor wrote:
>
> > Tweaking needed
>
> > Test Summary Report
> > t/bayesdbm_flock.t (Wstat: 0 Tests: 48 Failed: 1)
> > Failed test: 39
> > t/sa_check_spamd.t (Wstat: 0 Tests: 7 Failed: 5)
> > Failed tests: 1, 3-6
> > t/spamc_B.t (Wstat: 0 Tests: 9 Failed: 1)
> > Failed test: 9
> [...]
> > BSD/OS 4.3.1 running perl 5.16.2
> > BSD/OS 4.3 running perl 5.8.8
>
>
> BSD/OS?
>
> Wikipedia:
> BSD/OS was acquired by Wind River Systems in April 2001.
> Wind River discontinued sales of BSD/OS at the end of 2003,
> with support terminated at the end of 2004.
> Working state: Discontinued
> Source model: source-available, proprietary
> For the open source Unix released by Bill Jolitz, see 386BSD
> 386BSD: Latest stable release 1.0 / November 1994; 18 years ago
>
>
> So how can we test on such platform?
>
1) Get an account here I can provide
2) NetBSD, FreeBSD and OpenBSD are akin so some testers
might be available.
>
> Mark
>
--
Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
The false churches will conform themselves to this world's demands, seeing as they do not fear and thus do not obey God. - anon
Re: Apache SpamAssassin 3.4.0 release candidate 2 - invitation to testers
Posted by Mark Martinec <Ma...@ijs.si>.
On Saturday 22 June 2013 07:06:43 The Doctor wrote:
> Tweaking needed
> Test Summary Report
> t/bayesdbm_flock.t (Wstat: 0 Tests: 48 Failed: 1)
> Failed test: 39
> t/sa_check_spamd.t (Wstat: 0 Tests: 7 Failed: 5)
> Failed tests: 1, 3-6
> t/spamc_B.t (Wstat: 0 Tests: 9 Failed: 1)
> Failed test: 9
[...]
> BSD/OS 4.3.1 running perl 5.16.2
> BSD/OS 4.3 running perl 5.8.8
BSD/OS?
Wikipedia:
BSD/OS was acquired by Wind River Systems in April 2001.
Wind River discontinued sales of BSD/OS at the end of 2003,
with support terminated at the end of 2004.
Working state: Discontinued
Source model: source-available, proprietary
For the open source Unix released by Bill Jolitz, see 386BSD
386BSD: Latest stable release 1.0 / November 1994; 18 years ago
So how can we test on such platform?
Mark
Re: Apache SpamAssassin 3.4.0 release candidate 2 - invitation to
testers
Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Sat, Jun 22, 2013 at 02:45:12AM +0200, Mark Martinec wrote:
> This is not a formal announcement, but an invitation to a broader
> users community to try the release candidate of the coming release
> of Apache SpamAssassin version 3.4.0 .
>
> Preliminary release notes and a link to the package was published
> in a posting to the dev@spamassassin.apache.org mailing list:
>
> http://article.gmane.org/gmane.mail.spam.spamassassin.devel/69001
>
> The "call for votes" in the message only applies to project members,
> but feedback from wider audience of testers is very much welcome.
>
> The Mail-SpamAssassin-3.4.0-rc2 package is available at:
>
> http://people.apache.org/~kmcgrail/devel/
>
> Rules may be downloaded from the same location, but this is rarely
> necessary. A normal procedure is to install the software (the usual
> CPAN installation procedure should suffice, but this very much depends
> on a platform of choice), then run a 'sa-update' command, which will
> find and download appropriate rules to a version-specific directory.
>
> Except for some minor details, the 3.4.0 is compatible with 3.3.2 in
> its API and in database formats (but uses a separate directory to store
> rules), so it should be possible to switch back and forth between both
> versions in a test environment, if a need arises. Still, due diligence is
> appropriate: have your backups ready before starting to play with
> the new software, especially in a production environment.
> Nevertheless, this version has been in production use at several sites
> for months, so it should be at least as good as 3.3.2 .
>
> It is expected that the final release will follow shortly, so a quick
> response would be appreciated.
Tweaking needed
Test Summary Report
-------------------
t/bayesdbm_flock.t (Wstat: 0 Tests: 48 Failed: 1)
Failed test: 39
t/sa_check_spamd.t (Wstat: 0 Tests: 7 Failed: 5)
Failed tests: 1, 3-6
t/spamc_B.t (Wstat: 0 Tests: 9 Failed: 1)
Failed test: 9
t/spamc_c.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 1
t/spamc_c_stdout_closed.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 1
t/spamc_E.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 2
t/spamc_headers.t (Wstat: 0 Tests: 5 Failed: 2)
Failed tests: 3-4
t/spamc_optC.t (Wstat: 0 Tests: 9 Failed: 4)
Failed tests: 2, 4, 6, 8
t/spamc_optL.t (Wstat: 0 Tests: 16 Failed: 16)
Failed tests: 1-16
t/spamc_x_e.t (Wstat: 0 Tests: 7 Failed: 4)
Failed tests: 1-4
t/spamc_x_E_R.t (Wstat: 0 Tests: 49 Failed: 8)
Failed tests: 1, 4-6, 8, 10-12
t/spamc_z.t (Wstat: 0 Tests: 9 Failed: 5)
Failed tests: 4-5, 7-9
t/spamd.t (Wstat: 0 Tests: 14 Failed: 9)
Failed tests: 1, 5-6, 8-10, 12-14
t/spamd_allow_user_rules.t (Wstat: 0 Tests: 5 Failed: 3)
Failed tests: 1, 3-4
t/spamd_client.t (Wstat: 0 Tests: 52 Failed: 30)
Failed tests: 2, 4-6, 8-16, 18, 32, 35, 37-42, 44, 46-52
t/spamd_hup.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: Bad plan. You planned 110 tests but ran 0.
t/spamd_kill_restart.t (Wstat: 0 Tests: 3 Failed: 1)
Failed test: 3
Parse errors: Bad plan. You planned 93 tests but ran 3.
t/spamd_kill_restart_rr.t (Wstat: 0 Tests: 3 Failed: 1)
Failed test: 3
Parse errors: Bad plan. You planned 93 tests but ran 3.
t/spamd_maxchildren.t (Wstat: 0 Tests: 22 Failed: 12)
Failed tests: 1, 3-7, 17-22
t/spamd_parallel.t (Wstat: 0 Tests: 20 Failed: 10)
Failed tests: 2-6, 16-20
t/spamd_port.t (Wstat: 0 Tests: 4 Failed: 2)
Failed tests: 3-4
t/spamd_protocol_10.t (Wstat: 0 Tests: 8 Failed: 8)
Failed tests: 1-8
Parse errors: Bad plan. You planned 10 tests but ran 8.
t/spamd_report.t (Wstat: 0 Tests: 6 Failed: 5)
Failed tests: 1, 3-6
t/spamd_report_ifspam.t (Wstat: 0 Tests: 10 Failed: 5)
Failed tests: 1, 3-5, 10
t/spamd_stop.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 2
t/spamd_symbols.t (Wstat: 0 Tests: 3 Failed: 2)
Failed tests: 2-3
t/spamd_syslog.t (Wstat: 0 Tests: 7 Failed: 5)
Failed tests: 3-7
t/spamd_unix_and_tcp.t (Wstat: 0 Tests: 10 Failed: 2)
Failed tests: 3, 8
t/spamd_user_rules_leak.t (Wstat: 0 Tests: 28 Failed: 8)
Failed tests: 1, 3-6, 9, 19-20
t/spamd_whitelist_leak.t (Wstat: 0 Tests: 8 Failed: 5)
Failed tests: 1, 3-4, 6, 8
Files=167, Tests=2727, 4969 wallclock secs ( 3.57 usr 4.58 sys + 377.50 cusr 76.75 csys = 462.40 CPU)
Result: FAIL
Failed 30/167 test programs. 158/2727 subtests failed.
*** Error code 255
Stop.
BSD/OS 4.3.1 running perl 5.16.2
Test Summary Report
-------------------
t/bayesdbm_flock.t (Wstat: 0 Tests: 48 Failed: 1)
Failed test: 37
t/sa_check_spamd.t (Wstat: 0 Tests: 7 Failed: 5)
Failed tests: 1, 3-6
t/spamc_B.t (Wstat: 0 Tests: 9 Failed: 1)
Failed test: 9
t/spamc_c.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 1
t/spamc_c_stdout_closed.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 1
t/spamc_E.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 2
t/spamc_headers.t (Wstat: 0 Tests: 5 Failed: 2)
Failed tests: 3-4
t/spamc_optC.t (Wstat: 0 Tests: 9 Failed: 4)
Failed tests: 2, 4, 6, 8
t/spamc_optL.t (Wstat: 0 Tests: 16 Failed: 16)
Failed tests: 1-16
t/spamc_x_e.t (Wstat: 0 Tests: 7 Failed: 4)
Failed tests: 1-4
t/spamc_x_E_R.t (Wstat: 0 Tests: 49 Failed: 8)
Failed tests: 1, 4-6, 8, 10-12
t/spamc_z.t (Wstat: 0 Tests: 9 Failed: 5)
Failed tests: 4-5, 7-9
t/spamd.t (Wstat: 0 Tests: 14 Failed: 9)
Failed tests: 1, 5-6, 8-10, 12-14
t/spamd_allow_user_rules.t (Wstat: 0 Tests: 5 Failed: 3)
Failed tests: 1, 3-4
t/spamd_client.t (Wstat: 0 Tests: 52 Failed: 30)
Failed tests: 2, 4-6, 8-16, 18, 32, 35, 37-42, 44, 46-52
t/spamd_hup.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: Bad plan. You planned 110 tests but ran 0.
t/spamd_kill_restart.t (Wstat: 0 Tests: 3 Failed: 1)
Failed test: 3
Parse errors: Bad plan. You planned 93 tests but ran 3.
t/spamd_kill_restart_rr.t (Wstat: 0 Tests: 3 Failed: 1)
Failed test: 3
Parse errors: Bad plan. You planned 93 tests but ran 3.
t/spamd_maxchildren.t (Wstat: 0 Tests: 22 Failed: 12)
Failed tests: 1, 3-7, 17-22
t/spamd_parallel.t (Wstat: 0 Tests: 20 Failed: 10)
Failed tests: 2-6, 16-20
t/spamd_port.t (Wstat: 0 Tests: 4 Failed: 2)
Failed tests: 3-4
t/spamd_protocol_10.t (Wstat: 0 Tests: 8 Failed: 8)
Failed tests: 1-8
Parse errors: Bad plan. You planned 10 tests but ran 8.
t/spamd_report.t (Wstat: 0 Tests: 6 Failed: 5)
Failed tests: 1, 3-6
t/spamd_report_ifspam.t (Wstat: 0 Tests: 10 Failed: 5)
Failed tests: 1, 3-5, 10
t/spamd_stop.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 2
t/spamd_symbols.t (Wstat: 0 Tests: 3 Failed: 2)
Failed tests: 2-3
t/spamd_syslog.t (Wstat: 0 Tests: 7 Failed: 5)
Failed tests: 3-7
t/spamd_unix_and_tcp.t (Wstat: 0 Tests: 10 Failed: 2)
Failed tests: 3, 8
t/spamd_user_rules_leak.t (Wstat: 0 Tests: 28 Failed: 8)
Failed tests: 1, 3-6, 9, 19-20
t/spamd_whitelist_leak.t (Wstat: 0 Tests: 8 Failed: 5)
Failed tests: 1, 3-4, 6, 8
Files=167, Tests=2727, 5493 wallclock secs ( 5.17 usr 7.72 sys + 465.63 cusr 176.42 csys = 654.93 CPU)
Result: FAIL
Failed 30/167 test programs. 158/2727 subtests failed.
*** Error code 255
Stop.
BSD/OS 4.3 running perl 5.8.8
>
> Mark
--
Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
The false churches will conform themselves to this world's demands, seeing as they do not fear and thus do not obey God. - anon