You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by mm...@apache.org on 2015/04/15 03:03:04 UTC
svn commit: r1673598 - /spamassassin/trunk/build/announcements/3.4.1-rc2.txt
Author: mmartinec
Date: Wed Apr 15 01:03:04 2015
New Revision: 1673598
URL: http://svn.apache.org/r1673598
Log:
more 3.4.1-rc2.txt editing
Modified:
spamassassin/trunk/build/announcements/3.4.1-rc2.txt
Modified: spamassassin/trunk/build/announcements/3.4.1-rc2.txt
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/announcements/3.4.1-rc2.txt?rev=1673598&r1=1673597&r2=1673598&view=diff
==============================================================================
--- spamassassin/trunk/build/announcements/3.4.1-rc2.txt (original)
+++ spamassassin/trunk/build/announcements/3.4.1-rc2.txt Wed Apr 15 01:03:04 2015
@@ -21,18 +21,40 @@ Notable features:
New plugins
-----------
-Mail::SpamAssassin::Plugin::TxRep
-Mail::SpamAssassin::Plugin::PDFInfo
-Mail::SpamAssassin::Plugin::URILocalBL.pm
+There are three new plugins added with this release:
+
+ Mail::SpamAssassin::Plugin::TxRep
+ Mail::SpamAssassin::Plugin::PDFInfo
+ Mail::SpamAssassin::Plugin::URILocalBL
+
+The TxRep (Reputation) plugin is designed as a substantially improved
+replacement of the AWL plugin. It adjusts the final message spam score
+by looking up and taking in consideration the reputation of the sender.
+It cannot coexist with the old AWL plugin, which must be disabled when
+the TxRep is loaded.
+
+The PDFInfo plugin helps detected spam using attached PDF files.
+
+The URILocalBL plugin creates some new rule test types, such as
+"uri_block_cc", "uri_block_cidr", and "uri_block_isp". These rules
+apply to the URIs found in the HTML portion of a message, i.e.
+<a href=...> markup.
+
+All these three plugins are disabled by default. To enable, uncomment
+the loadplugin configuration options in file v341.pre or add them to
+some local .pre file such as local.pre .
+
+Plugins are documented in their respective man pages.
Notable changes
---------------
Adding SHA digests of MIME parts as Bayes tokens allows bayes
-to see non-textual content. The set of sources of bayes tokens
-is configurable with a new configuration option 'bayes_token_sources'
-as documented in the Mail::SpamAssassin::Conf man page. (Bug 7115)
+to see non-textual content. The set of sources of bayes tokens is
+configurable with a new configuration option 'bayes_token_sources'
+as documented in the Mail::SpamAssassin::Conf man page, disabled
+by default for backward compatibility. (Bug 7115)
Subroutine Node::_normalize has been rewritten. The new behavior
is documented with the 'normalize_charset' option in the
@@ -45,114 +67,53 @@ in the Bayes plugin. (Bug 7130, Bug 7135
New configuration options
-------------------------
-perl_version
- (Introduced in 3.4.2) This will be replaced with the version
--->> THIS NEEDS TO BE FIXED in Conf.pm, WE ARE AT 3.4.1
-
-
-changed implementation, may produce different result in some cases:
-
-normalize_charset ( 0 | 1) (default: 0)
- Whether to decode non- UTF-8 and non-ASCII textual parts and recode
- them to UTF-8 before the text is given over to rules processing.
- The character set used for attempted decoding is primarily based on
- a declared character set in a Content-Type header, but if the
- decoding attempt fails a module Encode::Detect::Detector is
- consulted (if available) to provide a guess based on the actual
- text, and decoding is re-attempted. Even if the option is enabled
- no unnecessary decoding and re-encoding work is done when possible
- (like with an all-ASCII text with a US-ASCII or extended ASCII
- character set declaration, e.g. UTF-8 or ISO-8859-nn or Windows-nnnn).
-
- Unicode support in old versions of perl or in a core module Encode
- is likely to be buggy in places, so if the normalize_charset
- function is enabled it is advised to stick to more recent versions
- of perl (preferably 5.12 or later). The module
- Encode::Detect::Detector is optional, when necessary it will be
- used if it is available.
-
-
-option dns_server can now specify a scoped link-local IPv6 address, e.g.:
- dns_server [fe80::1%lo0]:53
-
-
-new option:
-
-bayes_token_sources (default: header visible invisible uri)
- Controls which sources in a mail message can contribute tokens
- (e.g. words, phrases, etc.) to a Bayes classifier. The argument is
- a space-separated list of keywords: header, visible, invisible,
- uri, mimepart), each of which may be prefixed by a no to indicate
- its exclusion. Additionally two reserved keywords are allowed: all
- and none (or: noall). The list of keywords is processed
- sequentially: a keyword all adds all available keywords to a set
- being built, a none or noall clears the set, other non-negated
- keywords are added to the set, and negated keywords are removed
- from the set. Keywords are case-insensitive.
-
- The default set is: header visible invisible uri, which is
- equivalent for example to: All NoMIMEpart. The reason why mimepart
- is not currently in a default set is that it is a newer source
- (introduced with SpamAssassin version 3.4.1) and not much
- experience has yet been gathered regarding its usefulness.
-
- See also option "bayes_ignore_header" for a fine-grained control on
- individual header fields under the umbrella of a more general
- keyword header here.
-
- Keywords imply the following data sources:
- header - tokens collected from a message header section
- visible - words from visible text (plain or HTML) in a message body
- invisible - hidden/invisible text in HTML parts of a message body
- uri - URIs collected from a message body
- mimepart - digests (hashes) of all MIME parts (textual or non-
- textual) of a message, computed after Base64 and quoted-printable
- decoding, suffixed by their Content-Type
- all - adds all the above keywords to the set being assembled
- none or noall - removes all keywords from the set
-
- The "bayes_token_sources" directive may appear multiple times, its
- keywords are interpreted sequentially, adding or removing items
- from the final set as they appear in their order in
- "bayes_token_sources" directive(s).
-
-
-new option:
-
-dkim_minimum_key_bits n (default: 1024)
- The smallest size of a signing key (in bits) for a valid signature
- to be considered for whitelisting. Additionally, the eval function
- check_dkim_valid() will return false on short keys when called with
- explicitly listed domains, and the eval function
- check_dkim_valid_author_sig() will return false on short keys
- (regardless of its arguments). Setting the option to 0 disables a
- key size check.
-
- Note that the option has no effect when the eval function
- check_dkim_valid() is called with no arguments (like in a rule
- DKIM_VALID). A mere presence of some valid signature on a message
- has no reputational value (without being associated with a
- particular domain), regardless of its key size - anyone can prepend
- its own signature on a copy of some third party mail and re-send
- it, which makes it no more trustworthy than without such signature.
- This is also a reason for a rule DKIM_VALID to have a near-zero score.
-
-
-change:
-
-check_rbl_from_domain
- This checks all the from addrs domain names as an alternate to
- check_rbl_from_host. As of v3.4.1, it has been improved to include
- a subtest for a specific octet.
-
-
-
-parse_dkim_uris ( 0 | 1 ) (default: 0)
-
- If this option is set to 1 and the message contains DKIM headers,
- the headers will be parsed for URIs to process alongside URIs found
- in the body with some rules and modules (ex. URIDNSBL)
+The 'normalize_charset' configuration option already existed in previous
+versions, but its functionality has been re-implemented to put more
+emphasis on the declared character set of a MIME part instead of relying
+on guesswork by Encode::Detect::Detector. When enabled, it converts
+non- UTF-8 textual parts of a mail message into UTF-8 encoding, before
+passing them to HTML decoding and to rules processing. This makes it
+possible to write regular expressions and strings in rules in UTF-8
+encoding, and allows plugins (such as tokenization in a Bayes plugin)
+to recognize multibyte characters and words in non-English languages
+as such, instead of 'randomly' considering some non-ASCII octets in
+multibyte characters as delimiters. Please see documentation for this
+configuration option in the Mail::SpamAssassin::Conf man page.
+
+The configuration option 'dns_server' can now specify a scoped
+link-local IPv6 address, e.g.: dns_server [fe80::1%lo0]:53
+
+A new configuration option 'bayes_token_sources' allows more control
+on the sources of tokens for the Bayes plugin. For compatibility
+the default set of sources is unchanged, but consider:
+ bayes_token_sources all
+or: bayes_token_sources mimepart
+to include SHA1 digests of all MIME parts of a message as Bayes tokens.
+Please see documentation for this option in the Mail::SpamAssassin::Conf
+man page.
+
+A new configuration option 'dkim_minimum_key_bits' with a default value
+of 1024 bits now controls the smallest size of a signing key (in bits)
+for a valid signature to be considered for whitelisting. Please see
+documentation for this option in the Mail::SpamAssassin::Plugin::DKIM
+man page.
+
+A new configuration option 'parse_dkim_uris' allows DKIM header fields
+to be parsed for URIs to process alongside URIs found in the body with
+some rules and modules (e.g. URIDNSBL).
+
+The configuration option 'check_rbl_from_domain' checks all the domain
+names in a From mail address as an alternate to check_rbl_from_host.
+As of v3.4.1, it has been improved to include a subtest for a specific
+octet.
+
+
+
+
+??? perl_version
+??? (Introduced in 3.4.2) This will be replaced with the version
+???-->> THIS NEEDS TO BE FIXED in Conf.pm, WE ARE AT 3.4.1
Added flag 'noawl' to the 'tflags' configuration option.