ANNOUNCE: Apache SpamAssassin 3.2.0 available

[Justin Mason]

Apache SpamAssassin 3.2.0 is now available!  This is the official release,
and contains a significant number of changes and major enhancements --
please use it!

Downloads are available from:
  http://spamassassin.apache.org/downloads.cgi?update=200705021400

md5sum of archive files:
6840e3be132e2c3cbf66298b0227e880  Mail-SpamAssassin-3.2.0.tar.bz2
aed988bb6cf463afc868a64d4cd771a3  Mail-SpamAssassin-3.2.0.tar.gz
484045c69499b2fa59f024179f1f49c2  Mail-SpamAssassin-3.2.0.zip

sha1sum of archive files:
2fb864f01fc1c287e6f6e62fab8338f32cd20fb1  Mail-SpamAssassin-3.2.0.tar.bz2
af3941ab4f9548107d06966780ba71f751ab0216  Mail-SpamAssassin-3.2.0.tar.gz
bf785d7088371ad3beafe6084bf296ee3434038c  Mail-SpamAssassin-3.2.0.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 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.1.8
------------------------------------

Changes to the core code:

 * new behavior for trusted_networks/internal_networks: the 127.* network is now always considered trusted and internal, regardless of configuration.

 * bug 3109: short-circuiting of 'definite ham' or 'definite spam' messages based on individual short-circuit rules using the 'shortcircuit' setting, by Dallas Engelken <dallase /at/ uribl.com>.

 * bug 5305: implement 'msa_networks', for ISPs to specify their Mail Submission Agents, and extend network trust accordingly.

 * bug 4636: Add support for charset normalization, so rules can be written in UTF-8 to match text in other charsets.

 * sa-compile: compilation of SpamAssassin rules into a fast parallel-matching DFA, implemented in native code.

 * "tflags multiple": allow writing of rules that count multiple hits in a single message.

 * bug 4363: if a message uses CRLF for line endings, we should use it as well, otherwise stay with LF as usual; important for Windows users.

 * bug 4515: content preview was omitting first paragraph when no Subject: header was present.

 * The third-party modules used by sa-update are now required by the SpamAssassin package, instead of being optional.

 * Bug 5165: 'sa-update --checkonly' added to check for updates without applying them; thanks to <anomie /at/ users.sourceforge.net>

 * Bugs 4606, 4609: Adjust MIME parsing limits for nested multipart/* and message/rfc822 MIME parts.

 * bug 5295: add 'whitelist_auth', to whitelist addresses that send mail using sender-authorization systems like SPF, Domain Keys, and DKIM

 * Removed dependency on Text::Wrap CPAN module.

 * Received header parsing updates/fixes/additions.

Spamc / spamd:

 * bug 4603: Mail::SpamAssassin::Spamd::Apache2 -- mod_perl2 module, implementing spamd as a mod_perl module, contributed as a Google Summer of Code project by Radoslaw Zielinski.

 * bug 3991: spamd can now listen on UNIX domain, TCP, and SSL sockets simultaneously.  Command-line semantics extended slightly, although fully backwards compatibly; add the --ssl-port switch to allow TCP and SSL listening at the same time.

 * bug 3466: do Bayes expiration, if required, after results have been passed back to the client from spamd; this helps avoid client timeouts.

 * more complete IPv6 support.

 * spamc: Add '-K' switch, to ping spamd.

 * spamc: add '-z' switch, which compresses mails to be scanned using zlib compression; very useful for long-distance use of spamc over the internet.

 * bug 5296: spamc '--headers' switch, which scans messages and transmits back just rewritten headers.  This is more bandwidth-efficient than the normal mode of scanning, but only works for 'report_safe 0'.
 
 * Bump spamd's protocol version to 1.4, to reflect new HEADERS verb used for '--headers'.

Mail::SpamAssassin modules and API:

 * bug 4589: allow M::SA::Message to use IO::File objects to read in message (same as GLOB).

 * bug 4517: rule instrumentation plugin hooks, to measure performance, from John Gardiner Myers <jgmyers /at/ proofpoint.com>.

 * add two features to core rule-parsing code; 1. optional behaviour to recurse through subdirs looking for .cf/.pre's, to support rules compilers working on rulesrc dir.  2. call back into invoking code on lint failure, so rule compiler can detect which rules exactly fail the lint check.

 * bug 5206: detect duplicate rules, and silently merge them internally for greater efficiency.

 * bug 5243: add Plugin::register_method_priority() API, allowing plugins to control the relative ordering of plugin callbacks relative to other plugins' implementations.

 * Reduced memory footprint.

Plugins:

 * bug 5236: Support Mail::SPF replacement for Mail::SPF::Query.

 * bug 5127: allow mimeheader :raw rules to match newlines and folded-header whitespace in MIME header strings.

 * bug 4770: add ASN.pm plugin, contributed by Matthias Leisi <matthias at leisi.net>

 * bug 5271: move ImageInfo ruleset into 3.2.0 core rules, thanks to Dallas Engelken <dallase /at/ uribl.com>.

 * VBounce ruleset and plugin: detect spurious bounce messages sent by broken mail systems in response to spam or viruses.  (Based on Tim Jackson's "bogus-virus-warnings.cf" ruleset.)

 * DomainKeys/DKIM: Mail::DKIM is now preferred over Mail::DomainKeys, since the latter module is no longer actively maintained, and Mail::DKIM can handle both DomainKeys and DKIM signatures.

 * DKIM: separate signature verification from fetching a policy: can save a DNS lookup for each unverified message by setting score to 0 for all policy-related rules (DKIM_POLICY_SIGNALL, DKIM_POLICY_SIGNSOME, and DKIM_POLICY_TESTING). (thanks to Mark Martinec)

 * DKIM: support testing flags in the public key, as well as in the policy record. (thanks to Mark Martinec)

 * DKIM: skip fetching a policy (SSP) if a signature does verify, according to draft-allman-dkim-ssp-02 (thanks to Mark Martinec)

 * Move rule functionality and checking into separate Check plugin, allowing third parties to implement alternative scanner core algorithms.

 * core EvalTests code moved into various plugins.

* Plus lots of miscellaneous bug fixes.


A more detailed change log can be read here:

http://svn.apache.org/repos/asf/spamassassin/tags/spamassassin_release_3_2_0/Changes

[Rick Macdougall-2]

Justin Mason wrote:
> Apache SpamAssassin 3.2.0 is now available!  This is the official release,
> and contains a significant number of changes and major enhancements --
> please use it!

Quick question.

If I use sa-compile, which works very well here btw, do I need to re-run
it after downloading new rules via sa-update ?

Regards,

Rick

[Justin Mason]

Rick Macdougall writes:
> Justin Mason wrote:
> > Apache SpamAssassin 3.2.0 is now available!  This is the official release,
> > and contains a significant number of changes and major enhancements --
> > please use it!
>
> Quick question.
>
> If I use sa-compile, which works very well here btw, do I need to re-run
> it after downloading new rules via sa-update ?

yep.  I do this:

  sudo sa-update && sudo sa-compile && sudo /etc/init.d/spamassassin reload

--j.

[Matt Kettler-3]

Rick Macdougall wrote:

> Justin Mason wrote:
>> Apache SpamAssassin 3.2.0 is now available!  This is the official
>> release,
>> and contains a significant number of changes and major enhancements --
>> please use it!
>
> Quick question.
>
> If I use sa-compile, which works very well here btw, do I need to
> re-run it after downloading new rules via sa-update ?
>

I cannot speak authoritatively, as I'm no expert on sa-compile or
Rule2XSBody.

However, the reading the sa-update script, it does not appear to have
any code to support this, so I'd say you very likely have to re-run
sa-compile.

You could probably tweak the spamd restart sample in the sa-update
manpage into a script that would try sa-update, then sa-compile, then
restart spamd.

[Rick Macdougall-2]

Justin Mason wrote:

> Rick Macdougall writes:
>> Justin Mason wrote:
>>> Apache SpamAssassin 3.2.0 is now available!  This is the official release,
>>> and contains a significant number of changes and major enhancements --
>>> please use it!
>> Quick question.
>>
>> If I use sa-compile, which works very well here btw, do I need to re-run
>> it after downloading new rules via sa-update ?
>
> yep.  I do this:
>
>   sudo sa-update && sudo sa-compile && sudo /etc/init.d/spamassassin reload
>

Perfect, thanks!

Regards,

Rick

[Matthias Schmidt [c]]

Am/On Wed, 2 May 2007 14:11:34 +0100 schrieb/wrote Justin Mason:

>
>Rick Macdougall writes:
>> Justin Mason wrote:
>> > Apache SpamAssassin 3.2.0 is now available!  This is the official
release,

>> > and contains a significant number of changes and major enhancements --
>> > please use it!
>>
>> Quick question.
>>
>> If I use sa-compile, which works very well here btw, do I need to re-run
>> it after downloading new rules via sa-update ?
>
>yep.  I do this:
>
>  sudo sa-update && sudo sa-compile && sudo /etc/init.d/spamassassin reload

and on a Mac OS 10.4.9 System - there is no init.d/spamassassin - ?

Thanks and all the best

Matthias



--
--------------------- [ SECURITY NOTICE ] ---------------------
To: jm@..., users@....
For your security, beta@...
digitally signed this message on 02 May 2007 at 14:04:23 UTC.
Verify this digital signature at http://www.ciphire.com/verify.
---------------- [ CIPHIRE DIGITAL SIGNATURE ] ----------------
Q2lwaGlyZSBTaWcuAjhqbUBqbWFzb24ub3JnLCB1c2Vyc0BzcGFtYXNzYXNzaW4u
YXBhY2hlLm9yZwBiZXRhQGFkbWlsb24ubmV0AGVtYWlsIGJvZHkADAIAAHwAfAAA
AAEAAABnmjhGDAIAAAoCAAIAAgACACD9Ai21V8oDfBQZmyrLTAeiXFHYXrdeSBX/
+DEIczVg3QEADr+4K2c1G+FkDKuvQ5xCTjUVBh0UyHH72UGj6mtz5naGpVqEnAYy
PrMxt+2lvlOxHpMQHaIVCkeKlDAipU5AXe6mzQr7U2lnRW5k
------------------ [ END DIGITAL SIGNATURE ] ------------------

[mariogamito]

Justin Mason wrote:
 > Apache SpamAssassin 3.2.0 is now available!  This is the official
 > release, and contains a significant number of changes and major
 > enhancements
And what are they ?

I'm not very fond of messing around with a very stable server.
I'm using 3.1.8

Regards,
Mário Gamito

[Richard Frovarp]

Mário Gamito wrote:

> Justin Mason wrote:
> > Apache SpamAssassin 3.2.0 is now available!  This is the official
> > release, and contains a significant number of changes and major
> > enhancements
> And what are they ?
>
> I'm not very fond of messing around with a very stable server.
> I'm using 3.1.8
>
> Regards,
> Mário Gamito
>

They were listed at the bottom of the announcement.

[Rose, Bobby]

The ImageInfo packaged with 3.2.0 isn't the latest version from SARE as
it's missing the image_name_regex method.

-=B

[Theo Van Dinter-2]

On Wed, May 02, 2007 at 03:32:31PM -0400, Rose, Bobby wrote:
> The ImageInfo packaged with 3.2.0 isn't the latest version from SARE as
> it's missing the image_name_regex method.

We can only include that which is donated to the project.

--
Randomly Selected Tagline:
First solid fuel we've had since we burned the cats.

[Michael Scheidell]

 

> -----Original Message-----
> From: Justin Mason [mailto:jm@...]
> Sent: Wednesday, May 02, 2007 8:43 AM
> To: users@...;
> dev@...; announce@...
> Subject: ANNOUNCE: Apache SpamAssassin 3.2.0 available
>
> Apache SpamAssassin 3.2.0 is now available!  This is the
> official release, and contains a significant number of
> changes and major enhancements -- please use it!
>
> Downloads are available from:
>   http://spamassassin.apache.org/downloads.cgi?update=200705021400

Still get this on Freebsd, sa-compile SEEMS to run fine, but this
happens

[97520] dbg: rules: compiled one_line_body tests
[97520] dbg: zoom: run_body_fast_scan for body_0 start
/libexec/ld-elf.so.1:
/var/db/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledRe
gexps/body_0/body_0.so: Undefined symbol
"Mail_SpamAssassin_CompiledRegexps_body_0_scan1"

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_________________________________________________________________________

[Craig Carriere]

I receive the exact same error on SLES10 FWIW.

Michael Scheidell wrote:

-----Original Message-----
From: Justin Mason [jm@...] 
Sent: Wednesday, May 02, 2007 8:43 AM
To: users@...; 
dev@...; announce@...
Subject: ANNOUNCE: Apache SpamAssassin 3.2.0 available

Apache SpamAssassin 3.2.0 is now available!  This is the 
official release, and contains a significant number of 
changes and major enhancements -- please use it!

Downloads are available from:
  http://spamassassin.apache.org/downloads.cgi?update=200705021400
    

Still get this on Freebsd, sa-compile SEEMS to run fine, but this
happens

[97520] dbg: rules: compiled one_line_body tests
[97520] dbg: zoom: run_body_fast_scan for body_0 start
/libexec/ld-elf.so.1:
/var/db/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledRe
gexps/body_0/body_0.so: Undefined symbol
"Mail_SpamAssassin_CompiledRegexps_body_0_scan1"

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm). 
For Information please see http://www.spammertrap.com
_________________________________________________________________________

  

[ccarriere.vcf]

---

begin:vcard
fn:Dr. Craig Carriere
n:Carriere;Craig
org:Cobatco Inc.
adr:;;1215 NE Adams Street;Peoria;IL;61550;USA
email;internet:ccarriere@...
tel;work:309.676.2663
tel;fax:[phone]
url:http://www.cobatco.com
version:2.1
end:vcard

---

[Michael Scheidell]

Craig Carriere wrote:

I receive the exact same error on SLES10 FWIW.

I am assuming it's something to do with loader paths', but I haven't figured it out yet.

as for the FREEBSD port (which I maintain) I think I am going to publish the package without sa-compile, so it gets out there

(any freebsd users want to try?  rm the current contents of p5-Mail-SpamAssassin dir and untar this there, run make config first:

http://www.secnap.com/downloads/sa320.tgs

Still get this on Freebsd, sa-compile SEEMS to run fine, but this
happens

[97520] dbg: rules: compiled one_line_body tests
[97520] dbg: zoom: run_body_fast_scan for body_0 start
/libexec/ld-elf.so.1:
/var/db/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledRe
gexps/body_0/body_0.so: Undefined symbol
"Mail_SpamAssassin_CompiledRegexps_body_0_scan1"

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm). 
For Information please see http://www.spammertrap.com
_________________________________________________________________________

  

---

This email has been scanned and certified safe by SpammerTrap™.
For Information please see www.spammertrap.com

---

[Anders Norrbring]

I just ran into a big problem......

[25735] warn: bayes: database version is different than we understand
(3), aborting! at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/BayesStore/SQL.pm
line 136


Any ideas please?

Anders



Craig Carriere skrev:

> I receive the exact same error on SLES10 FWIW.
>
> Michael Scheidell wrote:
>>  
>>
>>  
>>> -----Original Message-----
>>> From: Justin Mason [mailto:jm@...]
>>> Sent: Wednesday, May 02, 2007 8:43 AM
>>> To: users@...;
>>> dev@...; announce@...
>>> Subject: ANNOUNCE: Apache SpamAssassin 3.2.0 available
>>>
>>> Apache SpamAssassin 3.2.0 is now available!  This is the
>>> official release, and contains a significant number of
>>> changes and major enhancements -- please use it!
>>>
>>> Downloads are available from:
>>>   http://spamassassin.apache.org/downloads.cgi?update=200705021400
>>>    
>>
>>
>> Still get this on Freebsd, sa-compile SEEMS to run fine, but this
>> happens
>>
>> [97520] dbg: rules: compiled one_line_body tests
>> [97520] dbg: zoom: run_body_fast_scan for body_0 start
>> /libexec/ld-elf.so.1:
>> /var/db/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledRe
>> gexps/body_0/body_0.so: Undefined symbol
>> "Mail_SpamAssassin_CompiledRegexps_body_0_scan1"
>>
>> _________________________________________________________________________
>> This email has been scanned and certified safe by SpammerTrap(tm).
>> For Information please see http://www.spammertrap.com
>> _________________________________________________________________________
>>
>>  

[Jakob Hirsch]

Michael Scheidell wrote:

> Still get this on Freebsd, sa-compile SEEMS to run fine, but this
> happens
>
> [97520] dbg: rules: compiled one_line_body tests
> [97520] dbg: zoom: run_body_fast_scan for body_0 start
> /libexec/ld-elf.so.1:
> /var/db/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledRe
> gexps/body_0/body_0.so: Undefined symbol
> "Mail_SpamAssassin_CompiledRegexps_body_0_scan1"

Are you sure that re2c compiled your rules properly? I had the same
error, it turned out to be re2c was segfaulting, but unfortunately
sa-compile didn't show any errors (which is bad, I'd say).

see
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5435
and
http://sourceforge.net/tracker/index.php?func=detail&aid=1708378&group_id=96864&atid=616200

re2c 12.0 works for me.

[Michael Scheidell]

Jakob Hirsch wrote:
> Michael Scheidell wrote:
>  

> sa-compile didn't show any errors (which is bad, I'd say).
>
> see
> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5435
> and
> http://sourceforge.net/tracker/index.php?func=detail&aid=1708378&group_id=96864&atid=616200
>
> re2c 12.0 works for me.
>
>  

i'll try that, I guess I have to submit a port patch for re2c now:

we are using:

pkg_info -cQ 're2c>=0'
re2c-0.11.1:Compile regular express

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_________________________________________________________________________

[Justin Mason]

Michael Scheidell writes:

> Jakob Hirsch wrote:
> > Michael Scheidell wrote:
> >  
>
> > sa-compile didn't show any errors (which is bad, I'd say).
> >
> > see
> > http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5435
> > and
> > http://sourceforge.net/tracker/index.php?func=detail&aid=1708378&group_id=96864&atid=616200
> >
> > re2c 12.0 works for me.
> >
> >  
>
> i'll try that, I guess I have to submit a port patch for re2c now:
>
> we are using:
>
> pkg_info -cQ 're2c>=0'
> re2c-0.11.1:Compile regular express

yep, apparently 0.11.3 works -- see bug 5435.

[Jakob Hirsch]

Quoting Justin Mason:

>>> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5435
>>> http://sourceforge.net/tracker/index.php?func=detail&aid=1708378&group_id=96864&atid=616200
>>> re2c 12.0 works for me.
>> re2c-0.11.1:Compile regular express
> yep, apparently 0.11.3 works -- see bug 5435.

As I wrote, it didn't work for me, but (the now released) 12.0 did.
Probably depends on the rules (though I have nothing special) and the
compiler you use (gcc 4.1.1 here). But as the re2c-developer writes:

> Actually i highly suggest you use cvs version of either 0.12.0
> (unreleased) or even HEAD. It appears the generated code is wrong using the
> older re2c versions.

So I guess 12.0 should be used.

[Andrzej Migdalski]

I had a problem with re2c v0.11.3 segfaulting when bogus-virus-warnings.cf
was in use (?). 0.12.0 runs ok.
A.


Jakob Hirsch wrote:

> Quoting Justin Mason:
>
>>>> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5435
>>>> http://sourceforge.net/tracker/index.php?func=detail&aid=1708378&group_id=96864&atid=616200
>>>> re2c 12.0 works for me.
>>> re2c-0.11.1:Compile regular express
>> yep, apparently 0.11.3 works -- see bug 5435.
>
> As I wrote, it didn't work for me, but (the now released) 12.0 did.
> Probably depends on the rules (though I have nothing special) and the
> compiler you use (gcc 4.1.1 here). But as the re2c-developer writes:
>
>> Actually i highly suggest you use cvs version of either 0.12.0
>> (unreleased) or even HEAD. It appears the generated code is wrong using the
>> older re2c versions.
>
> So I guess 12.0 should be used.
>
>

[JamesDR-2]

Anders Norrbring wrote:

>
> I just ran into a big problem......
>
> [25735] warn: bayes: database version is different than we understand
> (3), aborting! at
> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/BayesStore/SQL.pm
> line 136
>
>
> Any ideas please?
>
> Anders

What version did you upgrade from?


--
Thanks,
James