RE: [SA] ANNOUNCE: Apache SpamAssassin 3.2.0 available

2007-05-02 Thread Eric Goforth
Will this upgrade be available via Yum repositories? 

Eric


-Original Message-
From: Justin Mason [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 02, 2007 5:43 AM
To: users@SpamAssassin.apache.org; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: [SA] 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

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
[EMAIL PROTECTED]
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 

RE: [SA] ANNOUNCE: Apache SpamAssassin 3.2.0 available

2007-05-02 Thread Eric Goforth
Roger that.. Thanks.

 


 
Eric J. Goforth | President  Sr. Engineer
Goforth Technology Management, Inc. dba Goforth Technologies
82850 Miles Ave.| Indio | CA | 92201
Ph. (760) 775-7004 ext. 109 | Fax. (760) 495-5574
24Hour Support: (760) 775-7004 Option 5

-Original Message-
From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 02, 2007 11:56 AM
To: Eric Goforth
Cc: users@spamassassin.apache.org
Subject: Re: [SA] ANNOUNCE: Apache SpamAssassin 3.2.0 available

Eric Goforth wrote:
 Will this upgrade be available via Yum repositories? 

I don't see why not; at least eventually.  Like most software, though,
you'll have to wait for the package maintainer to package and publish
the new version.  The SA project does not release packages.

Daryl


Fowarding spams to the list.... Not good???

2007-04-30 Thread Eric Goforth
Hey all,

I have a quick thought about something we may want to all consider.  For
those of us that use SA (all of us right?) and we use Bayes (most of us
I assume) and that have whitelisted this list (a few anyhow) that get
people forwarding their spam messages to the list (only a couple I
think...)  

I think your throwing our Bayes out of whack...  We are trying to train
our systems to drop the stuff your forwarding the list...

I may be off since I am still a newbie to SA and in particular how Bayes
does its job... But... Food for thought.  Can we avoid forwarding spam
messages to the list?  

Eric J. Goforth
[EMAIL PROTECTED]


Error restoring Bayes Database (MySQL)

2007-04-30 Thread Eric Goforth
Having a crazy thing happen when trying to restore my Bayes database to a new 
MySql Server.  
 
During the restore process, it stops with the following error message.  
However, it is clearly only partial informaiton as some of the characters must 
be goofy ascii codes.  The screen jumps around during the restore and dumps 
this error message:
 
 e 262: Duplicate entry '496-þÌ

I'm hosed if I can't restore my database (for whatever reason and heaven forbid 
a system failure...)..
 
Anyone have any insight?  Thanks!
 
Eric J. Goforth
[EMAIL PROTECTED]
 
 


RE: [SA] Re: Fowarding spams to the list.... Not good???

2007-04-30 Thread Eric Goforth
I guess that makes much better sense...  Point well taken and thanks. 

Eric


-Original Message-
From: Theo Van Dinter [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 30, 2007 4:28 PM
To: users@spamassassin.apache.org
Subject: [SA] Re: Fowarding spams to the list Not good???

On Mon, Apr 30, 2007 at 04:03:13PM -0700, Eric Goforth wrote:
 I may be off since I am still a newbie to SA and in particular how 
 Bayes does its job... But... Food for thought.  Can we avoid 
 forwarding spam messages to the list?

The more appropriate, and previously stated, way to deal with this is to
not filter or learn from spam-related lists.  There will always be
spammy snippets or whole messages sent to the list, that's part of
normal discussion here.

--
Randomly Selected Tagline:
It is my persistent belief (and fond hope) that theory and practice
don't always have to pull in opposite directions.
 -- Larry Wall in [EMAIL PROTECTED]


Mysql with Trusted IP's..

2007-04-29 Thread Eric Goforth
I have been google -ing for days to try to find out how/if Spamassassin
can poll a Mysql database for trusted IP's.  I have it working well with
userprefs (tons of documentation there!), but using mysql for trusted
IP's there isn't any...

 

Anyone know of a source for information on this?

 

Thanks!

Eric