|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
|
|
[vote] proposed 3.3.0-alpha1 releaseHi guys -- I've cut tarballs for the alpha. Here goes! Please give me a few
votes for a public release of these (my vote: +1 of course). Here's the proposed announcement... To: users, dev, announce Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available Apache SpamAssassin 3.3.0-alpha1 is now available for testing. Downloads are available from: http://people.apache.org/~jm/devel/ md5sum of archive files: 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip 3cb55fc1bd84bc93013638f9f8fa88c0 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz sha1sum of archive files: f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 de65e1d5f29b954b2c60d58f10a6dc710a8a3629 Mail-SpamAssassin-3.3.0-alpha1.tar.gz cc0c7531f666e48e1593054cfa2bb70336ca2f13 Mail-SpamAssassin-3.3.0-alpha1.zip 83b0559399a1849063cfcf209be9d23eab1f8267 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz The release files also have a .asc accompanying them. The file serves as an external GPG signature for the given release file. The signing key is available via the wwwkeys.pgp.net key server, as well as http://spamassassin.apache.org/released/GPG-SIGNING-KEY The key information is: pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@...> Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B See the INSTALL and UPGRADE files in the distribution for important installation notes. Summary of major changes since 3.2.6 ------------------------------------ Changes to the core code: [TODO: write changes list] |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseJustin Mason wrote:
> Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a few > votes for a public release of these (my vote: +1 of course). Here's the > proposed announcement... > > > To: users, dev, announce > Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available > > Apache SpamAssassin 3.3.0-alpha1 is now available for testing. > > Downloads are available from: > http://people.apache.org/~jm/devel/ > > md5sum of archive files: > > 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 > 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz > c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip > 3cb55fc1bd84bc93013638f9f8fa88c0 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz > > sha1sum of archive files: > > f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 > de65e1d5f29b954b2c60d58f10a6dc710a8a3629 Mail-SpamAssassin-3.3.0-alpha1.tar.gz > cc0c7531f666e48e1593054cfa2bb70336ca2f13 Mail-SpamAssassin-3.3.0-alpha1.zip > 83b0559399a1849063cfcf209be9d23eab1f8267 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz > > > The release files also have a .asc accompanying them. The file serves > as an external GPG signature for the given release file. The signing > key is available via the wwwkeys.pgp.net key server, as well as > http://spamassassin.apache.org/released/GPG-SIGNING-KEY > > The key information is: > > pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@...> > Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B > > See the INSTALL and UPGRADE files in the distribution for important > installation notes. > > Summary of major changes since 3.2.6 > ------------------------------------ > > Changes to the core code: > > [TODO: write changes list] > +1 from me. And it builds and tests fine for me on various OS's. -- -Doc Penguins: Do it on the ice. Cairns: Do it underground |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseI'm running long tests and net tests and getting a lot of failures in the
DKIM area. I'm running 0.28. Is this a known issue? Should I upgrade DKIM and try again which would like make me suggest a higher version requirement for the makefile. Regards,KAM t/dkim2......................... Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 1 in t/SATest.pm at line 707 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 2 in t/SATest.pm at line 707 fail #2 Output can be examined in: log/d.dkim/1 t/dkim2.........................NOK 1# Failed test 3 in t/dkim2.t at line 50 # t/dkim2.t line 50 is: ok ok_all_patterns(); t/dkim2.........................NOK 3 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 4 in t/SATest.pm at line 707 fail #3 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 4# Failed test 5 in t/SATest.pm at line 707 fail #4 Output can be examined in: log/d.dkim/4 # Failed test 6 in t/dkim2.t at line 50 fail #2 t/dkim2.........................NOK 6 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 7 in t/SATest.pm at line 707 fail #5 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 7# Failed test 8 in t/SATest.pm at line 707 fail #6 Output can be examined in: log/d.dkim/7 # Failed test 9 in t/dkim2.t at line 50 fail #3 t/dkim2.........................NOK 9 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 10 in t/SATest.pm at line 707 fail #7 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 10# Failed test 11 in t/SATest.pm at line 707 fail #8 Output can be examined in: log/d.dkim/10 # Failed test 12 in t/dkim2.t at line 50 fail #4 t/dkim2.........................NOK 12 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 13 in t/SATest.pm at line 707 fail #9 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 13# Failed test 14 in t/SATest.pm at line 707 fail #10 Output can be examined in: log/d.dkim/13 # Failed test 15 in t/dkim2.t at line 50 fail #5 t/dkim2.........................NOK 15 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 16 in t/SATest.pm at line 707 fail #11 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 17 in t/SATest.pm at line 707 fail #12 t/dkim2.........................NOK 16Output can be examined in: log/d.dkim/16 # Failed test 18 in t/dkim2.t at line 50 fail #6 t/dkim2.........................NOK 18 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 19 in t/SATest.pm at line 707 fail #13 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 19# Failed test 20 in t/SATest.pm at line 707 fail #14 Output can be examined in: log/d.dkim/19 # Failed test 21 in t/dkim2.t at line 50 fail #7 t/dkim2.........................NOK 21 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 22 in t/SATest.pm at line 707 fail #15 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 22# Failed test 23 in t/SATest.pm at line 707 fail #16 Output can be examined in: log/d.dkim/22 # Failed test 24 in t/dkim2.t at line 50 fail #8 t/dkim2.........................NOK 24 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 25 in t/SATest.pm at line 707 fail #17 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 26 in t/SATest.pm at line 707 fail #18 t/dkim2.........................NOK 25Output can be examined in: log/d.dkim/25 # Failed test 27 in t/dkim2.t at line 50 fail #9 t/dkim2.........................NOK 27 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 28 in t/SATest.pm at line 707 fail #19 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 29 in t/SATest.pm at line 707 fail #20 t/dkim2.........................NOK 28Output can be examined in: log/d.dkim/28 # Failed test 30 in t/dkim2.t at line 50 fail #10 t/dkim2.........................NOK 30 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 31 in t/SATest.pm at line 707 fail #21 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 31# Failed test 32 in t/SATest.pm at line 707 fail #22 Output can be examined in: log/d.dkim/31 # Failed test 33 in t/dkim2.t at line 50 fail #11 t/dkim2.........................NOK 33 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 34 in t/SATest.pm at line 707 fail #23 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 34# Failed test 35 in t/SATest.pm at line 707 fail #24 Output can be examined in: log/d.dkim/34 # Failed test 36 in t/dkim2.t at line 50 fail #12 t/dkim2.........................NOK 36 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 37 in t/SATest.pm at line 707 fail #25 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 37# Failed test 38 in t/SATest.pm at line 707 fail #26 Output can be examined in: log/d.dkim/37 # Failed test 39 in t/dkim2.t at line 50 fail #13 t/dkim2.........................NOK 39 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 40 in t/SATest.pm at line 707 fail #27 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 40# Failed test 41 in t/SATest.pm at line 707 fail #28 Output can be examined in: log/d.dkim/40 # Failed test 42 in t/dkim2.t at line 50 fail #14 t/dkim2.........................NOK 42 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 43 in t/SATest.pm at line 707 fail #29 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 44 in t/SATest.pm at line 707 fail #30 t/dkim2.........................NOK 43Output can be examined in: log/d.dkim/43 # Failed test 45 in t/dkim2.t at line 50 fail #15 t/dkim2.........................NOK 45 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 46 in t/SATest.pm at line 707 fail #31 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. t/dkim2.........................NOK 46# Failed test 47 in t/SATest.pm at line 707 fail #32 Output can be examined in: log/d.dkim/46 # Failed test 48 in t/dkim2.t at line 50 fail #16 t/dkim2.........................NOK 48 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 49 in t/SATest.pm at line 707 fail #33 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 50 in t/SATest.pm at line 707 fail #34 t/dkim2.........................NOK 49Output can be examined in: log/d.dkim/49 # Failed test 51 in t/dkim2.t at line 50 fail #17 t/dkim2.........................NOK 51 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 52 in t/SATest.pm at line 707 fail #35 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 53 in t/SATest.pm at line 707 fail #36 t/dkim2.........................NOK 52Output can be examined in: log/d.dkim/52 # Failed test 54 in t/dkim2.t at line 50 fail #18 t/dkim2.........................NOK 54 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 55 in t/SATest.pm at line 707 fail #37 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 56 in t/SATest.pm at line 707 fail #38 t/dkim2.........................NOK 55Output can be examined in: log/d.dkim/55 # Failed test 57 in t/dkim2.t at line 50 fail #19 t/dkim2.........................ok 58/80 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 60 in t/SATest.pm at line 707 fail #39 Output can be examined in: log/d.dkim/60 t/dkim2.........................NOK 60# Failed test 62 in t/dkim2.t at line 72 # t/dkim2.t line 72 is: ok ok_all_patterns(); t/dkim2.........................NOK 62 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 63 in t/SATest.pm at line 707 fail #40 Output can be examined in: log/d.dkim/63 t/dkim2.........................NOK 63# Failed test 65 in t/dkim2.t at line 72 fail #2 t/dkim2.........................NOK 65 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 66 in t/SATest.pm at line 707 fail #41 Output can be examined in: log/d.dkim/66 t/dkim2.........................NOK 66# Failed test 68 in t/dkim2.t at line 72 fail #3 t/dkim2.........................NOK 68 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 69 in t/SATest.pm at line 707 fail #42 t/dkim2.........................NOK 69Output can be examined in: log/d.dkim/69 # Failed test 71 in t/dkim2.t at line 72 fail #4 t/dkim2.........................NOK 71 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 72 in t/SATest.pm at line 707 fail #43 Output can be examined in: log/d.dkim/72 t/dkim2.........................NOK 72# Failed test 74 in t/dkim2.t at line 72 fail #5 t/dkim2.........................NOK 74 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 75 in t/SATest.pm at line 707 fail #44 Output can be examined in: log/d.dkim/75 t/dkim2.........................NOK 75# Failed test 77 in t/dkim2.t at line 72 fail #6 t/dkim2.........................NOK 77 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 78 in t/SATest.pm at line 707 fail #45 t/dkim2.........................NOK 78Output can be examined in: log/d.dkim/78 # Failed test 80 in t/dkim2.t at line 72 fail #7 t/dkim2.........................FAILED tests 1-57, 60, 62-63, 65-66, 68-69, 71-72, 74-75, 77-78, 80 Failed 71/80 tests, 11.25% okay ----- Original Message ----- From: "Justin Mason" <jm@...> To: <dev@...> Sent: Wednesday, July 01, 2009 5:34 PM Subject: [vote] proposed 3.3.0-alpha1 release > Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a > few > votes for a public release of these (my vote: +1 of course). Here's the > proposed announcement... > > > To: users, dev, announce > Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available > > Apache SpamAssassin 3.3.0-alpha1 is now available for testing. > > Downloads are available from: > http://people.apache.org/~jm/devel/ > > md5sum of archive files: > > 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 > 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz > c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip > 3cb55fc1bd84bc93013638f9f8fa88c0 > Mail-SpamAssassin-rules-3.3.0-alpha1.tgz > > sha1sum of archive files: > > f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd > Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 > de65e1d5f29b954b2c60d58f10a6dc710a8a3629 > Mail-SpamAssassin-3.3.0-alpha1.tar.gz > cc0c7531f666e48e1593054cfa2bb70336ca2f13 > Mail-SpamAssassin-3.3.0-alpha1.zip > 83b0559399a1849063cfcf209be9d23eab1f8267 > Mail-SpamAssassin-rules-3.3.0-alpha1.tgz > > > The release files also have a .asc accompanying them. The file serves > as an external GPG signature for the given release file. The signing > key is available via the wwwkeys.pgp.net key server, as well as > http://spamassassin.apache.org/released/GPG-SIGNING-KEY > > The key information is: > > pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key > <release@...> > Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B > > See the INSTALL and UPGRADE files in the distribution for important > installation notes. > > Summary of major changes since 3.2.6 > ------------------------------------ > > Changes to the core code: > > [TODO: write changes list] > > |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseBTW, don't forget. If you "make install" this, you need to either run
"sa-update" immediately, or download the rules .tgz and "sa-update --install" it, as 3.3.0 doesn't come with any rules bundled by default. Anyone planning to give another +1 so Mark can talk about it tomorrow? ;) --j. On Wed, Jul 1, 2009 at 22:34, Justin Mason<jm@...> wrote: > Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a few > votes for a public release of these (my vote: +1 of course). Here's the > proposed announcement... > > > To: users, dev, announce > Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available > > Apache SpamAssassin 3.3.0-alpha1 is now available for testing. > > Downloads are available from: > http://people.apache.org/~jm/devel/ > > md5sum of archive files: > > 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 > 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz > c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip > 3cb55fc1bd84bc93013638f9f8fa88c0 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz > > sha1sum of archive files: > > f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 > de65e1d5f29b954b2c60d58f10a6dc710a8a3629 Mail-SpamAssassin-3.3.0-alpha1.tar.gz > cc0c7531f666e48e1593054cfa2bb70336ca2f13 Mail-SpamAssassin-3.3.0-alpha1.zip > 83b0559399a1849063cfcf209be9d23eab1f8267 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz > > > The release files also have a .asc accompanying them. The file serves > as an external GPG signature for the given release file. The signing > key is available via the wwwkeys.pgp.net key server, as well as > http://spamassassin.apache.org/released/GPG-SIGNING-KEY > > The key information is: > > pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@...> > Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B > > See the INSTALL and UPGRADE files in the distribution for important > installation notes. > > Summary of major changes since 3.2.6 > ------------------------------------ > > Changes to the core code: > > [TODO: write changes list] > > > |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseOn 7/2/2009 11:40 AM, Justin Mason wrote:
> BTW, don't forget. If you "make install" this, you need to either run > "sa-update" immediately, or download the rules .tgz and "sa-update > --install" it, as 3.3.0 doesn't come with any rules bundled by > default. > > Anyone planning to give another +1 so Mark can talk about it tomorrow? ;) AXB sez +1 (booting a VM to install <blush>) > > On Wed, Jul 1, 2009 at 22:34, Justin Mason<jm@...> wrote: >> Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a few >> votes for a public release of these (my vote: +1 of course). Here's the >> proposed announcement... >> >> >> To: users, dev, announce >> Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available >> >> Apache SpamAssassin 3.3.0-alpha1 is now available for testing. >> >> Downloads are available from: >> http://people.apache.org/~jm/devel/ >> >> md5sum of archive files: >> >> 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >> 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz >> c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip >> 3cb55fc1bd84bc93013638f9f8fa88c0 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >> >> sha1sum of archive files: >> >> f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >> de65e1d5f29b954b2c60d58f10a6dc710a8a3629 Mail-SpamAssassin-3.3.0-alpha1.tar.gz >> cc0c7531f666e48e1593054cfa2bb70336ca2f13 Mail-SpamAssassin-3.3.0-alpha1.zip >> 83b0559399a1849063cfcf209be9d23eab1f8267 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >> >> >> The release files also have a .asc accompanying them. The file serves >> as an external GPG signature for the given release file. The signing >> key is available via the wwwkeys.pgp.net key server, as well as >> http://spamassassin.apache.org/released/GPG-SIGNING-KEY >> >> The key information is: >> >> pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@...> >> Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B >> >> See the INSTALL and UPGRADE files in the distribution for important >> installation notes. >> >> Summary of major changes since 3.2.6 >> ------------------------------------ >> >> Changes to the core code: >> >> [TODO: write changes list] >> >> >> |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseOn Thu, 02 Jul 2009 00:13:52 +0200, Kevin A. McGrail <kmcgrail@...>
wrote: > I'm running long tests and net tests and getting a lot of failures in > the DKIM area. I'm running 0.28. > > Is this a known issue? Should I upgrade DKIM and try again which would > like make me suggest a higher version requirement for the makefile. Don't know, it passes all tests for me. Does it happen to others too? Is the plugin enabled at all? I would expect at least the tests for a presence of a signature (the DKIM_SIGNED) should work regardless of the version of Mail::DKIM. The DKIM_VALID would probably fail in some tests with older version on Mail::DKIM, but most of them should still pass. Please do try with Mail::DKIM 0.36, to see if that helps. Btw, you could run the following one-liner, giving it on stdin each of the 'pass' sample messages int/data/dkim/ : perl -MMail::DKIM::Verifier -ne ' BEGIN{$dkim=Mail::DKIM::Verifier->new_object}; s/\r?\n\z/\015\012/; $dkim->PRINT($_); END{$dkim->CLOSE; printf("%s\n",$_->result_detail) for $dkim->signatures}' < t/data/dkim/test-pass-19.msg Mark |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseI'll vote +1 so he can talk about it. With sa-update now we required, we
should add Archive::Tar as a requirement to the Makefile.PL, yes? # also see CURRENT_PM below 'PREREQ_PM' => { 'Digest::SHA1' => 0, # 2.0 is oldest tested version 'File::Spec' => 0.8, # older versions lack some routines we need 'File::Copy' => 2.02, # this version is shipped with 5.005_03, the oldest version known to work 'Pod::Usage' => 1.10, # all versions prior to this do seem to be buggy 'HTML::Parser' => 3.43, # the HTML code is based on this parser, older versions have utf-8 bugs 'Net::DNS' => (RUNNING_ON_WINDOWS ? 0.46 : 0.34), # bugs in older revs 'NetAddr::IP' => 0, 'Sys::Hostname' => 0, 'Time::HiRes' => 0, 'Time::Local' => 0, 'Errno' => 0, }, Regards, KAM ----- Original Message ----- From: "Justin Mason" <jm@...> To: <dev@...> Sent: Thursday, July 02, 2009 5:40 AM Subject: Re: [vote] proposed 3.3.0-alpha1 release > BTW, don't forget. If you "make install" this, you need to either run > "sa-update" immediately, or download the rules .tgz and "sa-update > --install" it, as 3.3.0 doesn't come with any rules bundled by > default. > > Anyone planning to give another +1 so Mark can talk about it tomorrow? ;) > > --j. > > On Wed, Jul 1, 2009 at 22:34, Justin Mason<jm@...> wrote: >> Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a >> few >> votes for a public release of these (my vote: +1 of course). Here's the >> proposed announcement... >> >> >> To: users, dev, announce >> Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available >> >> Apache SpamAssassin 3.3.0-alpha1 is now available for testing. >> >> Downloads are available from: >> http://people.apache.org/~jm/devel/ >> >> md5sum of archive files: >> >> 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >> 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz >> c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip >> 3cb55fc1bd84bc93013638f9f8fa88c0 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >> >> sha1sum of archive files: >> >> f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd >> Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >> de65e1d5f29b954b2c60d58f10a6dc710a8a3629 >> Mail-SpamAssassin-3.3.0-alpha1.tar.gz >> cc0c7531f666e48e1593054cfa2bb70336ca2f13 >> Mail-SpamAssassin-3.3.0-alpha1.zip >> 83b0559399a1849063cfcf209be9d23eab1f8267 >> Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >> >> >> The release files also have a .asc accompanying them. The file serves >> as an external GPG signature for the given release file. The signing >> key is available via the wwwkeys.pgp.net key server, as well as >> http://spamassassin.apache.org/released/GPG-SIGNING-KEY >> >> The key information is: >> >> pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key >> <release@...> >> Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B >> >> See the INSTALL and UPGRADE files in the distribution for important >> installation notes. >> >> Summary of major changes since 3.2.6 >> ------------------------------------ >> >> Changes to the core code: >> >> [TODO: write changes list] |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseAnd/or edit the Mail::SpamAssassin::Util::DependencyInfo as well.
----- Original Message ----- From: "Kevin A. McGrail" <kmcgrail@...> To: "Justin Mason" <jm@...>; <dev@...> Sent: Thursday, July 02, 2009 8:57 AM Subject: Re: [vote] proposed 3.3.0-alpha1 release > I'll vote +1 so he can talk about it. With sa-update now we required, we > should add Archive::Tar as a requirement to the Makefile.PL, yes? > > # also see CURRENT_PM below > 'PREREQ_PM' => { > 'Digest::SHA1' => 0, # 2.0 is oldest tested version > 'File::Spec' => 0.8, # older versions lack some > routines we need > 'File::Copy' => 2.02, # this version is shipped with > 5.005_03, the oldest version known to work > 'Pod::Usage' => 1.10, # all versions prior to this do > seem to be buggy > 'HTML::Parser' => 3.43, # the HTML code is based on this > parser, older versions have utf-8 bugs > 'Net::DNS' => (RUNNING_ON_WINDOWS ? 0.46 : 0.34), # bugs in > older revs > 'NetAddr::IP' => 0, > 'Sys::Hostname' => 0, > 'Time::HiRes' => 0, > 'Time::Local' => 0, > 'Errno' => 0, > }, > Regards, > KAM > ----- Original Message ----- > From: "Justin Mason" <jm@...> > To: <dev@...> > Sent: Thursday, July 02, 2009 5:40 AM > Subject: Re: [vote] proposed 3.3.0-alpha1 release > > >> BTW, don't forget. If you "make install" this, you need to either run >> "sa-update" immediately, or download the rules .tgz and "sa-update >> --install" it, as 3.3.0 doesn't come with any rules bundled by >> default. >> >> Anyone planning to give another +1 so Mark can talk about it tomorrow? ;) >> >> --j. >> >> On Wed, Jul 1, 2009 at 22:34, Justin Mason<jm@...> wrote: >>> Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a >>> few >>> votes for a public release of these (my vote: +1 of course). Here's the >>> proposed announcement... >>> >>> >>> To: users, dev, announce >>> Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available >>> >>> Apache SpamAssassin 3.3.0-alpha1 is now available for testing. >>> >>> Downloads are available from: >>> http://people.apache.org/~jm/devel/ >>> >>> md5sum of archive files: >>> >>> 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >>> 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz >>> c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip >>> 3cb55fc1bd84bc93013638f9f8fa88c0 >>> Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >>> >>> sha1sum of archive files: >>> >>> f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd >>> Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >>> de65e1d5f29b954b2c60d58f10a6dc710a8a3629 >>> Mail-SpamAssassin-3.3.0-alpha1.tar.gz >>> cc0c7531f666e48e1593054cfa2bb70336ca2f13 >>> Mail-SpamAssassin-3.3.0-alpha1.zip >>> 83b0559399a1849063cfcf209be9d23eab1f8267 >>> Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >>> >>> >>> The release files also have a .asc accompanying them. The file serves >>> as an external GPG signature for the given release file. The signing >>> key is available via the wwwkeys.pgp.net key server, as well as >>> http://spamassassin.apache.org/released/GPG-SIGNING-KEY >>> >>> The key information is: >>> >>> pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key >>> <release@...> >>> Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B >>> >>> See the INSTALL and UPGRADE files in the distribution for important >>> installation notes. >>> >>> Summary of major changes since 3.2.6 >>> ------------------------------------ >>> >>> Changes to the core code: >>> >>> [TODO: write changes list] > |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseHi Mark,
First, your requested CLI yields: perl -MMail::DKIM::Verifier -ne ' BEGIN{$dkim=Mail::DKIM::Verifier->new_object}; s/\r?\n\z/\015\012/; $dkim->PRINT($_); END{$dkim->CLOSE; printf("%s\n",$_->result_detail) for $dkim->signatures}' < t/data/dkim/test-pass-19.msg pass Second, I'm not sure if the plugin is "enabled". I'm working with an untarred version and running make test. I then enabled long tests and net tests in t/config.dist. I've edited nothing else. However, 0.36 yields similar issues: t/debug.........................ok t/desc_wrap.....................ok t/dkim..........................skipped all skipped: no reason given t/dkim2......................... Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 1 in t/SATest.pm at line 707 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 2 in t/SATest.pm at line 707 fail #2 t/dkim2.........................NOK 1Output can be examined in: log/d.dkim/1 # Failed test 3 in t/dkim2.t at line 50 # t/dkim2.t line 50 is: ok ok_all_patterns(); t/dkim2.........................NOK 3 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 4 in t/SATest.pm at line 707 fail #3 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 5 in t/SATest.pm at line 707 fail #4 t/dkim2.........................NOK 4Output can be examined in: log/d.dkim/4 # Failed test 6 in t/dkim2.t at line 50 fail #2 t/dkim2.........................NOK 6 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 7 in t/SATest.pm at line 707 fail #5 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 8 in t/SATest.pm at line 707 fail #6 t/dkim2.........................NOK 7Output can be examined in: log/d.dkim/7 # Failed test 9 in t/dkim2.t at line 50 fail #3 t/dkim2.........................NOK 9 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 10 in t/SATest.pm at line 707 fail #7 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 11 in t/SATest.pm at line 707 fail #8 t/dkim2.........................NOK 10Output can be examined in: log/d.dkim/10 # Failed test 12 in t/dkim2.t at line 50 fail #4 t/dkim2.........................NOK 12 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 13 in t/SATest.pm at line 707 fail #9 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 14 in t/SATest.pm at line 707 fail #10 t/dkim2.........................NOK 13Output can be examined in: log/d.dkim/13 # Failed test 15 in t/dkim2.t at line 50 fail #5 t/dkim2.........................NOK 15 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 16 in t/SATest.pm at line 707 fail #11 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 17 in t/SATest.pm at line 707 fail #12 t/dkim2.........................NOK 16Output can be examined in: log/d.dkim/16 # Failed test 18 in t/dkim2.t at line 50 fail #6 t/dkim2.........................NOK 18 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 19 in t/SATest.pm at line 707 fail #13 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 20 in t/SATest.pm at line 707 fail #14 t/dkim2.........................NOK 19Output can be examined in: log/d.dkim/19 # Failed test 21 in t/dkim2.t at line 50 fail #7 t/dkim2.........................NOK 21 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 22 in t/SATest.pm at line 707 fail #15 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 23 in t/SATest.pm at line 707 fail #16 t/dkim2.........................NOK 22Output can be examined in: log/d.dkim/22 # Failed test 24 in t/dkim2.t at line 50 fail #8 t/dkim2.........................NOK 24 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 25 in t/SATest.pm at line 707 fail #17 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 26 in t/SATest.pm at line 707 fail #18 t/dkim2.........................NOK 25Output can be examined in: log/d.dkim/25 # Failed test 27 in t/dkim2.t at line 50 fail #9 t/dkim2.........................NOK 27 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 28 in t/SATest.pm at line 707 fail #19 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 29 in t/SATest.pm at line 707 fail #20 t/dkim2.........................NOK 28Output can be examined in: log/d.dkim/28 # Failed test 30 in t/dkim2.t at line 50 fail #10 t/dkim2.........................NOK 30 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 31 in t/SATest.pm at line 707 fail #21 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 32 in t/SATest.pm at line 707 fail #22 t/dkim2.........................NOK 31Output can be examined in: log/d.dkim/31 # Failed test 33 in t/dkim2.t at line 50 fail #11 t/dkim2.........................NOK 33 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 34 in t/SATest.pm at line 707 fail #23 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 35 in t/SATest.pm at line 707 fail #24 t/dkim2.........................NOK 34Output can be examined in: log/d.dkim/34 # Failed test 36 in t/dkim2.t at line 50 fail #12 t/dkim2.........................NOK 36 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 37 in t/SATest.pm at line 707 fail #25 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 38 in t/SATest.pm at line 707 fail #26 t/dkim2.........................NOK 37Output can be examined in: log/d.dkim/37 # Failed test 39 in t/dkim2.t at line 50 fail #13 t/dkim2.........................NOK 39 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 40 in t/SATest.pm at line 707 fail #27 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 41 in t/SATest.pm at line 707 fail #28 t/dkim2.........................NOK 40Output can be examined in: log/d.dkim/40 # Failed test 42 in t/dkim2.t at line 50 fail #14 t/dkim2.........................NOK 42 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 43 in t/SATest.pm at line 707 fail #29 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 44 in t/SATest.pm at line 707 fail #30 t/dkim2.........................NOK 43Output can be examined in: log/d.dkim/43 # Failed test 45 in t/dkim2.t at line 50 fail #15 t/dkim2.........................NOK 45 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 46 in t/SATest.pm at line 707 fail #31 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 47 in t/SATest.pm at line 707 fail #32 t/dkim2.........................NOK 46Output can be examined in: log/d.dkim/46 # Failed test 48 in t/dkim2.t at line 50 fail #16 t/dkim2.........................NOK 48 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 49 in t/SATest.pm at line 707 fail #33 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 50 in t/SATest.pm at line 707 fail #34 t/dkim2.........................NOK 49Output can be examined in: log/d.dkim/49 # Failed test 51 in t/dkim2.t at line 50 fail #17 t/dkim2.........................NOK 51 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 52 in t/SATest.pm at line 707 fail #35 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 53 in t/SATest.pm at line 707 fail #36 t/dkim2.........................NOK 52Output can be examined in: log/d.dkim/52 # Failed test 54 in t/dkim2.t at line 50 fail #18 t/dkim2.........................NOK 54 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 50. # Failed test 55 in t/SATest.pm at line 707 fail #37 Not found: DKIM_VALID = DKIM_VALID at t/dkim2.t line 50. # Failed test 56 in t/SATest.pm at line 707 fail #38 t/dkim2.........................NOK 55Output can be examined in: log/d.dkim/55 # Failed test 57 in t/dkim2.t at line 50 fail #19 t/dkim2.........................ok 58/80 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 60 in t/SATest.pm at line 707 fail #39 Output can be examined in: log/d.dkim/60 t/dkim2.........................NOK 60# Failed test 62 in t/dkim2.t at line 72 # t/dkim2.t line 72 is: ok ok_all_patterns(); t/dkim2.........................NOK 62 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 63 in t/SATest.pm at line 707 fail #40 Output can be examined in: log/d.dkim/63 t/dkim2.........................NOK 63# Failed test 65 in t/dkim2.t at line 72 fail #2 t/dkim2.........................NOK 65 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 66 in t/SATest.pm at line 707 fail #41 Output can be examined in: log/d.dkim/66 t/dkim2.........................NOK 66# Failed test 68 in t/dkim2.t at line 72 fail #3 t/dkim2.........................NOK 68 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 69 in t/SATest.pm at line 707 fail #42 Output can be examined in: log/d.dkim/69 t/dkim2.........................NOK 69# Failed test 71 in t/dkim2.t at line 72 fail #4 t/dkim2.........................NOK 71 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 72 in t/SATest.pm at line 707 fail #43 Output can be examined in: log/d.dkim/72 t/dkim2.........................NOK 72# Failed test 74 in t/dkim2.t at line 72 fail #5 t/dkim2.........................NOK 74 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 75 in t/SATest.pm at line 707 fail #44 Output can be examined in: log/d.dkim/75 t/dkim2.........................NOK 75# Failed test 77 in t/dkim2.t at line 72 fail #6 t/dkim2.........................NOK 77 Not found: DKIM_SIGNED = DKIM_SIGNED at t/dkim2.t line 72. # Failed test 78 in t/SATest.pm at line 707 fail #45 Output can be examined in: log/d.dkim/78 t/dkim2.........................NOK 78# Failed test 80 in t/dkim2.t at line 72 fail #7 t/dkim2.........................FAILED tests 1-57, 60, 62-63, 65-66, 68-69, 71-72, 74-75, 77-78, 80 Failed 71/80 tests, 11.25% okay t/dnsbl.........................ok t/dnsbl_sc_meta.................ok t/duplicates....................ok t/get_all_headers...............ok t/get_headers...................ok t/gtube.........................ok t/hashcash......................ok t/html_colors...................ok Regards, KAM ----- Original Message ----- From: "Mark Martinec" <Mark.Martinec+sa@...> To: <dev@...> Sent: Thursday, July 02, 2009 6:53 AM Subject: Re: [vote] proposed 3.3.0-alpha1 release > On Thu, 02 Jul 2009 00:13:52 +0200, Kevin A. McGrail <kmcgrail@...> > wrote: > >> I'm running long tests and net tests and getting a lot of failures in >> the DKIM area. I'm running 0.28. >> >> Is this a known issue? Should I upgrade DKIM and try again which would >> like make me suggest a higher version requirement for the makefile. > > Don't know, it passes all tests for me. > Does it happen to others too? > > Is the plugin enabled at all? > I would expect at least the tests for a presence of a signature > (the DKIM_SIGNED) should work regardless of the version of Mail::DKIM. > > The DKIM_VALID would probably fail in some tests with older > version on Mail::DKIM, but most of them should still pass. > > Please do try with Mail::DKIM 0.36, to see if that helps. > > Btw, you could run the following one-liner, giving it on stdin > each of the 'pass' sample messages int/data/dkim/ : > > > perl -MMail::DKIM::Verifier -ne ' > BEGIN{$dkim=Mail::DKIM::Verifier->new_object}; > s/\r?\n\z/\015\012/; $dkim->PRINT($_); END{$dkim->CLOSE; > printf("%s\n",$_->result_detail) for $dkim->signatures}' > < t/data/dkim/test-pass-19.msg > |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseOn Thu, Jul 2, 2009 at 13:57, Kevin A. McGrail<kmcgrail@...> wrote:
> I'll vote +1 so he can talk about it. With sa-update now we required, we > should add Archive::Tar as a requirement to the Makefile.PL, yes? yes, good catch. https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6145 --j. > # also see CURRENT_PM below > 'PREREQ_PM' => { > 'Digest::SHA1' => 0, # 2.0 is oldest tested version > 'File::Spec' => 0.8, # older versions lack some routines > we need > 'File::Copy' => 2.02, # this version is shipped with > 5.005_03, the oldest version known to work > 'Pod::Usage' => 1.10, # all versions prior to this do seem > to be buggy > 'HTML::Parser' => 3.43, # the HTML code is based on this > parser, older versions have utf-8 bugs > 'Net::DNS' => (RUNNING_ON_WINDOWS ? 0.46 : 0.34), # bugs in older > revs > 'NetAddr::IP' => 0, > 'Sys::Hostname' => 0, > 'Time::HiRes' => 0, > 'Time::Local' => 0, > 'Errno' => 0, > }, > Regards, > KAM > ----- Original Message ----- From: "Justin Mason" <jm@...> > To: <dev@...> > Sent: Thursday, July 02, 2009 5:40 AM > Subject: Re: [vote] proposed 3.3.0-alpha1 release > > >> BTW, don't forget. If you "make install" this, you need to either run >> "sa-update" immediately, or download the rules .tgz and "sa-update >> --install" it, as 3.3.0 doesn't come with any rules bundled by >> default. >> >> Anyone planning to give another +1 so Mark can talk about it tomorrow? ;) >> >> --j. >> >> On Wed, Jul 1, 2009 at 22:34, Justin Mason<jm@...> wrote: >>> >>> Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a >>> few >>> votes for a public release of these (my vote: +1 of course). Here's the >>> proposed announcement... >>> >>> >>> To: users, dev, announce >>> Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available >>> >>> Apache SpamAssassin 3.3.0-alpha1 is now available for testing. >>> >>> Downloads are available from: >>> http://people.apache.org/~jm/devel/ >>> >>> md5sum of archive files: >>> >>> 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >>> 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz >>> c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip >>> 3cb55fc1bd84bc93013638f9f8fa88c0 Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >>> >>> sha1sum of archive files: >>> >>> f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd >>> Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >>> de65e1d5f29b954b2c60d58f10a6dc710a8a3629 >>> Mail-SpamAssassin-3.3.0-alpha1.tar.gz >>> cc0c7531f666e48e1593054cfa2bb70336ca2f13 >>> Mail-SpamAssassin-3.3.0-alpha1.zip >>> 83b0559399a1849063cfcf209be9d23eab1f8267 >>> Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >>> >>> >>> The release files also have a .asc accompanying them. The file serves >>> as an external GPG signature for the given release file. The signing >>> key is available via the wwwkeys.pgp.net key server, as well as >>> http://spamassassin.apache.org/released/GPG-SIGNING-KEY >>> >>> The key information is: >>> >>> pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key >>> <release@...> >>> Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B >>> >>> See the INSTALL and UPGRADE files in the distribution for important >>> installation notes. >>> >>> Summary of major changes since 3.2.6 >>> ------------------------------------ >>> >>> Changes to the core code: >>> >>> [TODO: write changes list] > > |
|
|
Re: [vote] proposed 3.3.0-alpha1 releaseok, that's 4 +1's -- Mark, go ahead and mention those tarballs if you like!
(I'll leave them on /~jm/devel/ ). --j. On Thu, Jul 2, 2009 at 10:49, Yet Another Ninja<sa-list@...> wrote: > On 7/2/2009 11:40 AM, Justin Mason wrote: >> >> BTW, don't forget. If you "make install" this, you need to either run >> "sa-update" immediately, or download the rules .tgz and "sa-update >> --install" it, as 3.3.0 doesn't come with any rules bundled by >> default. >> >> Anyone planning to give another +1 so Mark can talk about it tomorrow? ;) > > > AXB sez +1 > (booting a VM to install <blush>) > > > >> >> On Wed, Jul 1, 2009 at 22:34, Justin Mason<jm@...> wrote: >>> >>> Hi guys -- I've cut tarballs for the alpha. Here goes! Please give me a >>> few >>> votes for a public release of these (my vote: +1 of course). Here's the >>> proposed announcement... >>> >>> >>> To: users, dev, announce >>> Subject: ANNOUNCE: Apache SpamAssassin 3.3.0-alpha1 available >>> >>> Apache SpamAssassin 3.3.0-alpha1 is now available for testing. >>> >>> Downloads are available from: >>> http://people.apache.org/~jm/devel/ >>> >>> md5sum of archive files: >>> >>> 04141392e1f20ea4a91bb63937351c65 Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >>> 1532b02384c37b4fb40ff1244bca3ec5 Mail-SpamAssassin-3.3.0-alpha1.tar.gz >>> c2d80477b20b571b591eae11993dcf03 Mail-SpamAssassin-3.3.0-alpha1.zip >>> 3cb55fc1bd84bc93013638f9f8fa88c0 >>> Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >>> >>> sha1sum of archive files: >>> >>> f8b5236c0ef1de82699b4bf8e29cd3e0f0b18bfd >>> Mail-SpamAssassin-3.3.0-alpha1.tar.bz2 >>> de65e1d5f29b954b2c60d58f10a6dc710a8a3629 >>> Mail-SpamAssassin-3.3.0-alpha1.tar.gz >>> cc0c7531f666e48e1593054cfa2bb70336ca2f13 >>> Mail-SpamAssassin-3.3.0-alpha1.zip >>> 83b0559399a1849063cfcf209be9d23eab1f8267 >>> Mail-SpamAssassin-rules-3.3.0-alpha1.tgz >>> >>> >>> The release files also have a .asc accompanying them. The file serves >>> as an external GPG signature for the given release file. The signing >>> key is available via the wwwkeys.pgp.net key server, as well as >>> http://spamassassin.apache.org/released/GPG-SIGNING-KEY >>> >>> The key information is: >>> >>> pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key >>> <release@...> >>> Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B >>> >>> See the INSTALL and UPGRADE files in the distribution for important >>> installation notes. >>> >>> Summary of major changes since 3.2.6 >>> ------------------------------------ >>> >>> Changes to the core code: >>> >>> [TODO: write changes list] >>> >>> >>> > > |
|
|
Re: [vote] proposed 3.3.0-alpha1 release> ok, that's 4 +1's -- Mark, go ahead and mention those tarballs if you like! (I'll leave them on /~jm/devel/ ).
Thank you guys, and to Justin especially! My presentation on Amavis went well, many people attended, and I spent a couple of minutes on SpamAssassin 3.3, after making an official announcement of the availability of 3.3 alpha! Mark |
| Free embeddable forum powered by Nabble | Forum Help |