You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2004/08/05 05:48:56 UTC

SpamAssassin 3.0.0-pre4 is released!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

SpamAssassin is a mail filter which uses advanced statistical
and heuristic tests to identify spam (also known as unsolicited
commercial/bulk email).

Downloading
- -----------

Pick it up from:

  http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.tar.gz
  http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.tar.bz2
  http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.zip

md5sum of archive files:
ffbc9664affc3e316eb78fb83820f9bf  Mail-SpamAssassin-3.0.0-pre4.tar.bz2
8af807ea2e16b929d6ea6f7516a99b80  Mail-SpamAssassin-3.0.0-pre4.tar.gz
678220a15cdc4c377caee2c3ee3168f5  Mail-SpamAssassin-3.0.0-pre4.zip
sha1sum of archive files:
71285d1e46cefbc29c246933bf1b5680fdbae4c2  Mail-SpamAssassin-3.0.0-pre4.tar.bz2
616373af46ddfe780622921e55cdaab4b33fa19a  Mail-SpamAssassin-3.0.0-pre4.tar.gz
a78c8670b39e1928de800e339aedbd3d601ca3fe  Mail-SpamAssassin-3.0.0-pre4.zip

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 keyserver, as well as
http://www.spamassassin.org/released/GPG-SIGNING-KEY

The key information is:

pub  1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <re...@spamassassin.org>
    Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24  F6D7 DEE0 1987 265F A05B

Summary of major changes since 3.0.0-pre3
- -----------------------------------------

  - Security fix prevents a denial of service attack open to certain
    malformed messages; this DoS affects all SpamAssassin 2.5x,
    2.6x and 3.0.0-prex versions to date. 

  - new score-generation code to perform statistical validation testing
    against scores.

  - don't add -Wall to CFLAGS unless we believe GCC is being used.

  - spamc: fix declaration of size_t var that should have been ssize_t,
    use int instead of ssize_t, test for timeout before test for newline.

  - spamd: fixed bug in SQL use with no "User:" header.

  - fixed rewrite_header bug with using parentheses in headers.

  - Update build and test instructions for spamc under Windows.

  - bug 3651: if calling compile_now(), the available Bayes DB will remain
    tied.  a warning will then pop up (sanity_check_untie) before
    untieing.  fixed.

  - masses scripts updated to fix various bugs.

  - Bug 3656: Fix broken sa-learn --backup.

  - bug 3658: disable SenderBase rules.

  - updated copyright and license texts.

  - updated German translations.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFBEa4nQTcbUG5Y7woRAsUmAJ9/GWA6RkDqJ4S9xKY7U3FfNvXtiwCeLolh
Q/J18mYXoXZKFfrbk1tQ334=
=1voa
-----END PGP SIGNATURE-----


Re: SpamAssassin 3.0.0-pre4 - Load Problems

Posted by Michael Parker <pa...@pobox.com>.
On Thu, Aug 05, 2004 at 08:26:37AM -0400, Jeff Koch wrote:
> 
> I just installed this development release on one of our mailservers. It has 
> some great new features but it almost killed the machine. The load average 
> tripled, CPU usage went way up, time to scan a message went from an average 
> of 3 to 20 seconds, swap usage went to 500MB, etc.
> 

Not much to go on, but I do have a theory.  In cases like this
interactive debugging is often better, if you are still having
problems log into IRC later and ask for help.

Are you using a sitewide bayes db? or do you have individual user dbs?

My theory is that SA is trying to upgrade your bayes db(s) all at
once.  You can force this manually (see UPGRADE) for each bayes db and
then restart and things may be just fine.

If you wanted to test the theory quickly with little to no work, just
set use_bayes to 0 in your local.cf file and restart 3.0 processing.
If you have load problems then that probably wasn't it.

Here is an untested tip for doing this on a running system:
1) Install 3.0
1) Set use_bayes_rules to 0 in local.cf
2) Set bayes_auto_learn to 0 in local.cf
3) Start/restart spamd
4) Run sa-learn --sync on all of you bayes dbs
5) Unset the user_bayes_rules and bayes_auto_learn settings.
6) Start/restart spamd

If it turns out that this solves the problem, can you let me know, I
might want to beef up the UPGRADE documentation a little to help other
folks.


Michael


Re: SpamAssassin 3.0.0-pre4 - Load Problems

Posted by Michael Parker <pa...@pobox.com>.
On Thu, Aug 05, 2004 at 10:36:56AM -0400, Jeff Koch wrote:
> 
> We tried the new Bayes SQL DB system (with new empty tables) and the load 
> was high. Then we tried using the site-wide Bayes DB that had been built by 
> 2.63 and the load was high. We also tried it with Bayes off completely with 
> no change so we turned that back on. Scans were taking as much as 30 to 40 
> seconds. Server load averaged around 6.00. Now that we're back on 2.64 
> scans are taking the more normal 1 to 2 seconds and the server load is 
> under 1.00.

If you run spamd with -L how do things look?

Note: you can't downgrade your bayes dbs, so once you upgrade them to
version 3 you have to use them only with 3.0.0 and above.  To go back
to 2.64 you'll have to remove your bayes files.

> One thing I noticed was that the maillog showed more detail with 3.0 - it 
> showed all the tests being done. Maybe the SURBL tests take too long or 
> require too much memory. Also, is it possible that SPF is automatically 
> enabled?
> 

If the proper modules are installed then yes SPF will run.  The SURBL
tests will also run if all the right pieces are in place.

I suggest you start turning things off (ie -L, use_bayes 0,
use_auto_whitelist 0, etc) til you figure out what exactly is making
things slow.

My bet was on bayes upgrading the database files, that would explain
the high CPU and memory.  If you wipe out or turn off your bayes and
the CPU/memory requirements go down but you're still slow then I would
put money on a slow DNS server or network in general.

Lots of people have been running the 3.0.0 code in one form or another
for a very long time so it's hard for me to believe it's something
code related  Not that it couldn't happen, but it's important at this
point to do as much debugging as possible to find the primary cause.

Michael

SpamAssassin 3.0.0-pre4 - Load Problems

Posted by Jeff Koch <je...@intersessions.com>.
I just installed this development release on one of our mailservers. It has 
some great new features but it almost killed the machine. The load average 
tripled, CPU usage went way up, time to scan a message went from an average 
of 3 to 20 seconds, swap usage went to 500MB, etc.

We used most of the same local.cf RBL settings and even tried turning off 
all of the DNS/RBL checks including RAZOR2 and but it didn't help much. All 
extra '.cf' files were removed.

Possibly we did something wrong but I need to ask whether the 3.0 version 
is supposed to be faster or maybe the development release includes much 
debugging code that slows everything down.

When we went back to SA 2.64 everything went back to normal.

We used SQL user preferences on both. (We assumed 3.0 could use the 
existing 2.63 tables.)

Here's the spamd start options we used with 3.0

SPAMDOPTIONS="-d -q -c -x -m5 -H"

Any suggestions would be appreciated since we would really like to start 
using the SQL Bayes feature ( - we had this turned off.)



At 11:48 PM 8/4/2004, Justin Mason wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>SpamAssassin is a mail filter which uses advanced statistical
>and heuristic tests to identify spam (also known as unsolicited
>commercial/bulk email).
>
>Downloading
>- -----------
>
>Pick it up from:
>
>   http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.tar.gz
> 
>http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.tar.bz2
>   http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.zip
>
>md5sum of archive files:
>ffbc9664affc3e316eb78fb83820f9bf  Mail-SpamAssassin-3.0.0-pre4.tar.bz2
>8af807ea2e16b929d6ea6f7516a99b80  Mail-SpamAssassin-3.0.0-pre4.tar.gz
>678220a15cdc4c377caee2c3ee3168f5  Mail-SpamAssassin-3.0.0-pre4.zip
>sha1sum of archive files:
>71285d1e46cefbc29c246933bf1b5680fdbae4c2  Mail-SpamAssassin-3.0.0-pre4.tar.bz2
>616373af46ddfe780622921e55cdaab4b33fa19a  Mail-SpamAssassin-3.0.0-pre4.tar.gz
>a78c8670b39e1928de800e339aedbd3d601ca3fe  Mail-SpamAssassin-3.0.0-pre4.zip
>
>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 keyserver, as well as
>http://www.spamassassin.org/released/GPG-SIGNING-KEY
>
>The key information is:
>
>pub  1024D/265FA05B 2003-06-09 SpamAssassin Signing Key 
><re...@spamassassin.org>
>     Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24  F6D7 DEE0 1987 265F A05B
>
>Summary of major changes since 3.0.0-pre3
>- -----------------------------------------
>
>   - Security fix prevents a denial of service attack open to certain
>     malformed messages; this DoS affects all SpamAssassin 2.5x,
>     2.6x and 3.0.0-prex versions to date.
>
>   - new score-generation code to perform statistical validation testing
>     against scores.
>
>   - don't add -Wall to CFLAGS unless we believe GCC is being used.
>
>   - spamc: fix declaration of size_t var that should have been ssize_t,
>     use int instead of ssize_t, test for timeout before test for newline.
>
>   - spamd: fixed bug in SQL use with no "User:" header.
>
>   - fixed rewrite_header bug with using parentheses in headers.
>
>   - Update build and test instructions for spamc under Windows.
>
>   - bug 3651: if calling compile_now(), the available Bayes DB will remain
>     tied.  a warning will then pop up (sanity_check_untie) before
>     untieing.  fixed.
>
>   - masses scripts updated to fix various bugs.
>
>   - Bug 3656: Fix broken sa-learn --backup.
>
>   - bug 3658: disable SenderBase rules.
>
>   - updated copyright and license texts.
>
>   - updated German translations.
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>Comment: Exmh CVS
>
>iD8DBQFBEa4nQTcbUG5Y7woRAsUmAJ9/GWA6RkDqJ4S9xKY7U3FfNvXtiwCeLolh
>Q/J18mYXoXZKFfrbk1tQ334=
>=1voa
>-----END PGP SIGNATURE-----

Best Regards,

Jeff Koch, Intersessions 



SpamAssassin 3.0.0-pre4 - Load Problems

Posted by Jeff Koch <je...@intersessions.com>.
I just installed this development release on one of our mailservers. It has 
some great new features but it almost killed the machine. The load average 
tripled, CPU usage went way up, time to scan a message went from an average 
of 3 to 20 seconds, swap usage went to 500MB, etc.

We used most of the same local.cf RBL settings and even tried turning off 
all of the DNS/RBL checks including RAZOR2 and but it didn't help much. All 
extra '.cf' files were removed.

Possibly we did something wrong but I need to ask whether the 3.0 version 
is supposed to be faster or maybe the development release includes much 
debugging code that slows everything down.

When we went back to SA 2.64 everything went back to normal.

We used SQL user preferences on both. (We assumed 3.0 could use the 
existing 2.63 tables.)

Here's the spamd start options we used with 3.0

SPAMDOPTIONS="-d -q -c -x -m5 -H"

Any suggestions would be appreciated since we would really like to start 
using the SQL Bayes feature ( - we had this turned off.)



At 11:48 PM 8/4/2004, Justin Mason wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>SpamAssassin is a mail filter which uses advanced statistical
>and heuristic tests to identify spam (also known as unsolicited
>commercial/bulk email).
>
>Downloading
>- -----------
>
>Pick it up from:
>
>   http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.tar.gz
> 
>http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.tar.bz2
>   http://SpamAssassin.apache.org/released/Mail-SpamAssassin-3.0.0-pre4.zip
>
>md5sum of archive files:
>ffbc9664affc3e316eb78fb83820f9bf  Mail-SpamAssassin-3.0.0-pre4.tar.bz2
>8af807ea2e16b929d6ea6f7516a99b80  Mail-SpamAssassin-3.0.0-pre4.tar.gz
>678220a15cdc4c377caee2c3ee3168f5  Mail-SpamAssassin-3.0.0-pre4.zip
>sha1sum of archive files:
>71285d1e46cefbc29c246933bf1b5680fdbae4c2  Mail-SpamAssassin-3.0.0-pre4.tar.bz2
>616373af46ddfe780622921e55cdaab4b33fa19a  Mail-SpamAssassin-3.0.0-pre4.tar.gz
>a78c8670b39e1928de800e339aedbd3d601ca3fe  Mail-SpamAssassin-3.0.0-pre4.zip
>
>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 keyserver, as well as
>http://www.spamassassin.org/released/GPG-SIGNING-KEY
>
>The key information is:
>
>pub  1024D/265FA05B 2003-06-09 SpamAssassin Signing Key 
><re...@spamassassin.org>
>     Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24  F6D7 DEE0 1987 265F A05B
>
>Summary of major changes since 3.0.0-pre3
>- -----------------------------------------
>
>   - Security fix prevents a denial of service attack open to certain
>     malformed messages; this DoS affects all SpamAssassin 2.5x,
>     2.6x and 3.0.0-prex versions to date.
>
>   - new score-generation code to perform statistical validation testing
>     against scores.
>
>   - don't add -Wall to CFLAGS unless we believe GCC is being used.
>
>   - spamc: fix declaration of size_t var that should have been ssize_t,
>     use int instead of ssize_t, test for timeout before test for newline.
>
>   - spamd: fixed bug in SQL use with no "User:" header.
>
>   - fixed rewrite_header bug with using parentheses in headers.
>
>   - Update build and test instructions for spamc under Windows.
>
>   - bug 3651: if calling compile_now(), the available Bayes DB will remain
>     tied.  a warning will then pop up (sanity_check_untie) before
>     untieing.  fixed.
>
>   - masses scripts updated to fix various bugs.
>
>   - Bug 3656: Fix broken sa-learn --backup.
>
>   - bug 3658: disable SenderBase rules.
>
>   - updated copyright and license texts.
>
>   - updated German translations.
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>Comment: Exmh CVS
>
>iD8DBQFBEa4nQTcbUG5Y7woRAsUmAJ9/GWA6RkDqJ4S9xKY7U3FfNvXtiwCeLolh
>Q/J18mYXoXZKFfrbk1tQ334=
>=1voa
>-----END PGP SIGNATURE-----

Best Regards,

Jeff Koch, Intersessions