You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by jm...@jmason.org on 2005/09/15 01:52:32 UTC
ANNOUNCE: SpamAssassin 3.1.0 available!
SpamAssassin 3.1.0 is released! SpamAssassin 3.1.0 is a major update.
SpamAssassin is a mail filter which uses advanced statistical and
heuristic tests to identify spam (also known as unsolicited bulk email).
Highlights of the release
-------------------------
- Apache preforking algorithm adopted; number of spamd child processes is now
scaled, according to demand. This provides better VM behaviour when not
under peak load.
- added PostgreSQL, MySQL 4.1+, and local SDBM file Bayes storage modules. SQL
storage is now recommended for Bayes, instead of DB_File. NDBM_File support
has been dropped due to a major bug in that module.
- detect legitimate SMTP AUTH submission, to avoid false positives on
Dynablock-style rules.
- new plugins: DomainKeys (off by default), MIMEHeader: a new plugin to perform
tests against header in internal MIME structure, ReplaceTags: plugin by Felix
Bauer to support fuzzy text matching, WhiteListSubject: plugin added to
support user whitelists by Subject header.
- Razor: disable Razor2 support by default per our policy, since the service is
not free for non-personal use. It's trivial to reenable (by editing
'/etc/mail/spamassassin/v310.pre').
- DCC: disable DCC for similar reasons, due to new license terms.
- Net::DNS bug: high load caused answer packets to be mixed up and delivered as
answers to the wrong request, causing false positives. worked around.
- DNSBL lookups and other DNS operations are now more efficient, by using a
custom single-socket event-based model instead of Net::DNS.
Downloading
-----------
Pick it up from:
http://SpamAssassin.apache.org/
Note, it may take up to two hours from now for that mirror to update.
md5sum:
d28bd7e83d01b234144e336bbfde0caa Mail-SpamAssassin-3.1.0.tar.bz2
f70c1fcab3d9563731bbc307eda7d69e Mail-SpamAssassin-3.1.0.tar.gz
65e9629ce255244fe3cb3d9772cdf239 Mail-SpamAssassin-3.1.0.zip
sha1sum:
0185f076f619dd9e64e94b453017f9b08d4b0f04 Mail-SpamAssassin-3.1.0.tar.bz2
d887cbae5962cb03e45aaf71cd93881a27cccc99 Mail-SpamAssassin-3.1.0.tar.gz
8b9494448782f910e573377bf226a8072f24bb3f Mail-SpamAssassin-3.1.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 <re...@spamassassin.org>
Key fingerprint =3D 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B
Important installation notes
----------------------------
- see the INSTALL and UPGRADE files in the distribution.
Summary of major changes since 3.0.x
------------------------------------
- Apache preforking algorithm adopted; number of spamd child processes is now
scaled, according to demand. This provides better VM behaviour when not
under peak load.
- Inclusion of sa-update script which will allow for updates of rules and
scores in between code releases.
- added PostgreSQL, MySQL 4.1+, and local SDBM file Bayes storage modules. SQL
storage is now recommended for Bayes, instead of DB_File. NDBM_File support
has been dropped due to a major bug in that module.
- detect legitimate SMTP AUTH submission, to avoid false positives on
Dynablock-style rules.
- new Advance Fee Fraud (419 scam) rules.
- removed use of the Storable module, due to several reported hangs on SMP
Linux machines.
- Converted several rule/engine components into Plugins such as:
AccessDB, AWL, Pyzor, Razor2, DCC, Bayes AutoLearn Determination, etc.
- new plugins: DomainKeys (off by default), MIMEHeader: a new plugin to perform
tests against header in internal MIME structure, ReplaceTags: plugin by Felix
Bauer to support fuzzy text matching, WhiteListSubject: plugin added to
support user whitelists by Subject header.
- TextCat language guesser moved to a plugin. (This means "ok_languages"
is no longer part of the core engine by default.)
- Razor: disable Razor2 support by default per our policy, since the
service is not free for non-personal use. It's trivial to reenable.
- DCC: disable DCC for similar reasons, due to new license terms.
- Net::DNS bug: high load caused answer packets to be mixed up and delivered as
answers to the wrong request, causing false positives. worked around.
- DNSBL lookups and other DNS operations are now more efficient, by using a
custom single-socket event-based model instead of Net::DNS.
- add support for accreditation services, including Habeas v2.
- better URI parsing -- many evasion tricks now caught.
- URIBL lookups are prioritized based on the location in the message
the URI was found.
- mass-check now supports reusing realtime DNSBL hit results, and sample-based
Bayes autolearning emulation, to reduce complexity.
- sa-learn, spamassassin and mass-check now have optional progress bars.
- modify header ordering for DomainKeys compatibility, by placing markup
headers at the top of the message instead at the bottom of the list.
- spamd/spamc now support remote Bayes training, and reporting spam.
- spamc now supports reading its flags from a configuration file using the -F
switch, contributed by John Madden.
- added SPF-based whitelisting.
- Polish rules contributed by Radoslaw Stachowiak.
- many rule changes and additions.
Re: ANNOUNCE: SpamAssassin 3.1.0 available!
Posted by Warren Togami <wt...@redhat.com>.
- What are the implications of the language models code new in 3.1.x? I
don't see any mention of it in the announcement.
- Is it safe to use 3.0.x and 3.1.x interchangably on the same bayes
database files? (I intend on testing both 3.0.x and 3.1.x going into
the future.)
Warren Togami
wtogami@redhat.com
Re: ReplaceTags questions
Posted by Fred <te...@i-is.com>.
I've been very active playing with ReplaceTags so I'll make an attempt to
answer what I can.
Darryl Bleau wrote:
>
> 1. According to http://wiki.apache.org/spamassassin/ReplaceTags, you
> need to specify a 'replace_start' and 'replace_end', but I don't grep
> either of those in the current 3.1.0 ruleset. Has that changed and now
> <> is the official wrapper?
<> is the official wrapper, the < & > are default delimiters. I don't find
them defined in the cf files but it is defined in the .pm file.
push(@cmds, {
setting => 'replace_start',
default => '<',
type => $Mail::SpamAssassin::Conf::CONF_TYPE_STRING,
});
push(@cmds, {
setting => 'replace_end',
default => '>',
type => $Mail::SpamAssassin::Conf::CONF_TYPE_STRING,
});
> 2. Are the ReplaceTags supposed to be cross-file or limited to
> replacing tags in the file they are delared in? If they are across
> files does that mean you have to be sure to have the "replace_" lines
> loaded prior to
> any replace rules? (ie, declared in 25_replace to replace in 30_extra
> but not in 10_noreplace).
Just guessing here but I assume they are cross-file. All config files are
loaded at run-time, since meta rules allow sub rules to be located in any
file, I would assume the same applies for ReplaceTags.
ReplaceTags questions
Posted by Darryl Bleau <da...@submersion.com>.
I think the plugin is a good idea but I was trying to wrap my head
around the ReplaceTags plugin and I have a few questions that I'm sure
others might have. I tried to search for answers but couldn't find anything.
1. According to http://wiki.apache.org/spamassassin/ReplaceTags, you
need to specify a 'replace_start' and 'replace_end', but I don't grep
either of those in the current 3.1.0 ruleset. Has that changed and now
<> is the official wrapper?
2. Are the ReplaceTags supposed to be cross-file or limited to replacing
tags in the file they are delared in? If they are across files does that
mean you have to be sure to have the "replace_" lines loaded prior to
any replace rules? (ie, declared in 25_replace to replace in 30_extra
but not in 10_noreplace).
3. What's the precendence for inter/pre/post rules? Is it iterative from
the beginning? To clarify, given:
replace_inter X [ecks]
replace_inter O [ooh]
replace_tag A [a]
replace_tag B [b]
body XOREPLACE /<inter X><inter O><A><B>/
Should one expect "/[a][ecks][b]/" or "/[a][ecks][ooh][b]/" or maybe
even "/[a][ooh][ecks][b]/" ?
4. On that same vein, if we add this to the above:
replace_post I [aye]
And have "/<inter X><post I><A><B>/"
Should we expect "/[a][ecks][aye][b][aye]/" or "/[a][aye][ecks][b][aye]/" ?
5. Next, if we add:
replace_tag C [<A>]
And have "/<A><B><C>/"
Should we expect "/[a][b][a]/" or "/[a][b]<A>/" ?
6. The last question is why do we have different ways to specify a
replacement? Ie, in the current 3.1.0 we have:
replace_tag SP [\s\d_*\$\%(),.:;?!}{\[\]|\/?^\#~\xa1`'+-]
replace_inter SP [\s\d_*\$\%(),.:;?!}{\[\]|\/?^\#~\xa1`'+-]
Why not just declare 'tags' in general and let the usage dictate how
they are evaluated? For example, if we had:
replace_tag X (?:[x\xd7]|><)
replace_tag Y [y\xff\xfd\xa5j]
replace_tag Z [zs]
Wouldn't it be easier to write rules like:
body MYRULE /<inter X><Y><Z>/
body MYRULE2 /<post Y><X><Z>/
body MYRULE3 /<inter Z><post X><Y>/
The 'replace_(tag|inter|post|pre)' syntax just seems redundant to me,
but it's just a suggestion.
Thanks!
Re: ANNOUNCE: SpamAssassin 3.1.0 available!
Posted by Kenneth Porter <sh...@sewingwitch.com>.
Wiki needs an update:
<http://wiki.apache.org/spamassassin/NextRelease>
(I just updated 3 servers and was looking for the "new features" list to
add to the report to my users. For now I'll grab the one from the
announcement email.)