You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Duncan Findlay <du...@debian.org> on 2005/08/30 05:41:39 UTC
ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
*** THIS IS A RELEASE CANDIDATE ONLY, NOT THE FINAL 3.1.0 RELEASE ***
SpamAssassin 3.1.0-rc2 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).
This is a release candidate, and NOT the general availability release
(yet.) We think it's pretty rock solid, however. ;) Please test it
out, and report any bugs to:
http://bugzilla.spamassassin.org
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/released/Mail-SpamAssassin-3.1.0-rc2.tar.bz2
http://spamassassin.apache.org/released/Mail-SpamAssassin-3.1.0-rc2.tar.gz
http://spamassassin.apache.org/released/Mail-SpamAssassin-3.1.0-rc2.zip
md5sum:
1e2ecf555d62deae136b08fb482e8f68 Mail-SpamAssassin-3.1.0-rc2.tar.bz2
41fe5c0c5ab226e0d33de20c10f69240 Mail-SpamAssassin-3.1.0-rc2.tar.gz
91bc48f87eb520040ece42dced886243 Mail-SpamAssassin-3.1.0-rc2.zip
sha1sum:
a68a040c2b2c51d7284fbd15336e639a32a0d45d Mail-SpamAssassin-3.1.0-rc2.tar.bz2
a20f3d82743186af085fac1deb540c22ebdc8ce1 Mail-SpamAssassin-3.1.0-rc2.tar.gz
f76cc96981c6766d48edd6ed60c621036a9dfcf5 Mail-SpamAssassin-3.1.0-rc2.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 changes from 3.1.0-rc1
---------------------------------
- (Many) Documentation Fixes.
- Fixed problem in the PostgreSQL Bayes storage engine (bug 4531).
- Syslog entries now properly identified as 'spamd' instead of
'spamassassin' (bug 4533).
- Fixed situation where pyzor and dcc could be left running after a
timeout (bug 4518).
- Better handling of warnings while loading (bug 4536).
- Spamc learning/reporting is disabled by default in spamd, can be
enabled with the "--allow-tell" or "-l" option to spamd (bug 4546).
- Better support IPv6 resolvers (bug 4412).
- Better handle peculiarities with certain MIME boundaries (bug 4535).
- Fix unitialized value warnings in spamd with TELL commands (bug 4552).
- Fix sa-learn's --local option, which previously was always enabled
(bug 4494).
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.
--
Duncan Findlay
Re: Debian Packages for 3.1.0-rc2
Posted by Duncan Findlay <du...@debian.org>.
On Wed, Aug 31, 2005 at 02:23:14PM -0500, Chris Thielen wrote:
> Installed cleanly for me on my Sarge box. I merged my local.cf into the
> updated package one.
>
> Aug 31 14:04:27 ns1 spamd[4269]: Can't locate Sys/Hostname/Long.pm in @INC
> (@INC contains: ../lib /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.4
> /usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/lib/perl/5.8
> /usr/share/perl/5.8 /usr/local/lib/site_perl) at
> /usr/share/perl5/Mail/SPF/Query.pm line 328, <GEN12> line 64.
> I'm getting these in mail.log, but that's because libmail-spf-query-perl
> only suggests libsys-hostname-long-perl (which I don't have installed).
> I believe this is a warning at worst since the package is only
> suggested, and I assume it is out of your control.
That should be reported to the BTS as a libmail-spf-query-perl bug, I
believe.
> I am seeing some other anomalous messages in the log, but I believe they
> are not packaging related.
Hmm... feel free to report those to SA Bugzilla. :-)
--
Duncan Findlay
Re: SA 3.03, Fedora3 - missing sock
Posted by jdow <jd...@earthlink.net>.
No place sendmail would look for it, I believe.
{o.o}
----- Original Message -----
From: ".rp" <pr...@moveupdate.com>
> and no, it is not in the dryer :-)
>
> I have spamd running, but there is no sock file being created for sendmail
> to "hook" into to. and i do mean no sock file anywhere on the system that
> belongs to spamd. Where is the sock?
>
Re: SA 3.03, Fedora3 - missing sock
Posted by jdow <jd...@earthlink.net>.
From: ".rp" <pr...@moveupdate.com>
To: <us...@spamassassin.apache.org>
Sent: 2005 September, 04, Sunday 15:04
Subject: Re: SA 3.03, Fedora3 - missing sock
>> >
>> > I have spamd running, but there is no sock file being created for
>> > sendmail to "hook" into to. and i do mean no sock file anywhere on
>> > the system that belongs to spamd. Where is the sock?
>>
>> spamd isn't a milter, thus it doesn't create a socket for sendmail to
>> hook to. Spamd creates a IP socket for spamc to connect to.
>>
>> Look at milter-spamc to create a socket for sendmail to hook to. This
>> will "bridge the gap" between sendmail and spamd.
>>
>
> Hmm, this is the setup of my sendmail, which worked just fine with SA2.6x
>
> MAIL_FILTER(`spamassassin',`S=local:/var/run/spamass.sock,F=,T=C:15
> m;S:4m;R:4m;E:10m')dnl
/var/run/spamass.sock, as described above, is not a part of spamassassin.
So you have to deal with why that failed. SpamAssassin does not create
a socket. Spamd does. I don't know if the "/var/run/spamass.sock" knows
what socket spamd creates. For that matter, I do not see anything telling
the /var/run/spamass.sock program what socket to use. How does it decide
who and how to talk to? If it looks at port XXXX only then has clamav
already claimed that socket? Address the problem in your mail filter
not in spamassassin.
> define(`confMILTER_MACROS_CONNECT',`b, j, _, {daemon_name},
> {if_name}, {if_addr}')dnl
> dnl now the antivirus
> MAIL_FILTER(`clamav-milter',`S=local:/var/run/clamav/clamav-
> milter.sock,F=,T=S:4m;R:4m;E:10m')dnl
> define(`confINPUT_MAIL_FILTERS',`spamassassin, clamav-milter')
>
>
> just to make sure, I also tried
> MAIL_FILTER(`spamassassin',`S=local:/var/run/clamav/spamass.sock,F=,
> T=C:15m;S:4m;R:4m;E:10m')dnl
>
> since I knew there was no permissions problem with the clamav directory,
> but that did not help.
{^_^}
Re: SA 3.03, Fedora3 - missing sock
Posted by ".rp" <pr...@moveupdate.com>.
> >
> > I have spamd running, but there is no sock file being created for
> > sendmail to "hook" into to. and i do mean no sock file anywhere on
> > the system that belongs to spamd. Where is the sock?
>
> spamd isn't a milter, thus it doesn't create a socket for sendmail to
> hook to. Spamd creates a IP socket for spamc to connect to.
>
> Look at milter-spamc to create a socket for sendmail to hook to. This
> will "bridge the gap" between sendmail and spamd.
>
Hmm, this is the setup of my sendmail, which worked just fine with SA2.6x
MAIL_FILTER(`spamassassin',`S=local:/var/run/spamass.sock,F=,T=C:15
m;S:4m;R:4m;E:10m')dnl
define(`confMILTER_MACROS_CONNECT',`b, j, _, {daemon_name},
{if_name}, {if_addr}')dnl
dnl now the antivirus
MAIL_FILTER(`clamav-milter',`S=local:/var/run/clamav/clamav-
milter.sock,F=,T=S:4m;R:4m;E:10m')dnl
define(`confINPUT_MAIL_FILTERS',`spamassassin, clamav-milter')
just to make sure, I also tried
MAIL_FILTER(`spamassassin',`S=local:/var/run/clamav/spamass.sock,F=,
T=C:15m;S:4m;R:4m;E:10m')dnl
since I knew there was no permissions problem with the clamav directory,
but that did not help.
Re: SA 3.03, Fedora3 - missing sock
Posted by Matt Kettler <mk...@evi-inc.com>.
.rp wrote:
> and no, it is not in the dryer :-)
>
> I have spamd running, but there is no sock file being created for sendmail
> to "hook" into to. and i do mean no sock file anywhere on the system that
> belongs to spamd. Where is the sock?
spamd isn't a milter, thus it doesn't create a socket for sendmail to hook to.
Spamd creates a IP socket for spamc to connect to.
Look at milter-spamc to create a socket for sendmail to hook to. This will
"bridge the gap" between sendmail and spamd.
SA 3.03, Fedora3 - missing sock
Posted by ".rp" <pr...@moveupdate.com>.
and no, it is not in the dryer :-)
I have spamd running, but there is no sock file being created for sendmail
to "hook" into to. and i do mean no sock file anywhere on the system that
belongs to spamd. Where is the sock?
Re: Debian Packages for 3.1.0-rc2
Posted by Chris Thielen <cm...@someone.dhs.org>.
Duncan Findlay wrote:
>On Mon, Aug 29, 2005 at 11:41:39PM -0400, Duncan Findlay wrote:
>
>
>Debian packages or 3.1.0-rc2 are available from the experimental
>distibution (version 3.0.99pre3.1.0+rc2-1). I'd appreciate help
>testing them, so that all the bugs in the packaging can be worked out
>by the time 3.1.0 is uploaded to unstable.
>
Hi Duncan,
Installed cleanly for me on my Sarge box. I merged my local.cf into the
updated package one.
Aug 31 14:04:27 ns1 spamd[4269]: Can't locate Sys/Hostname/Long.pm in @INC (@INC contains: ../lib /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl) at /usr/share/perl5/Mail/SPF/Query.pm line 328, <GEN12> line 64.
I'm getting these in mail.log, but that's because libmail-spf-query-perl
only suggests libsys-hostname-long-perl (which I don't have installed).
I believe this is a warning at worst since the package is only
suggested, and I assume it is out of your control.
I am seeing some other anomalous messages in the log, but I believe they
are not packaging related.
Chris
Re: Debian Packages for 3.1.0-rc2
Posted by Stuart Johnston <st...@ebby.com>.
Bob Proulx wrote:
> jdow wrote:
>
>>Is it found in a handy place in CPAN?
>>{^_^}
>
>
> Because CPAN is for released modules (I am talking designed process
> and not observed quality here) I don't see how it could get there
> until it is actually released.
CPAN does have a way for tagging a "Developer Release" that will not be
installed by default. See for example:
http://search.cpan.org/dist/Compress-Zlib/
`install Compress::Zlib` will install 1.37 - not 2.000_01. To install
the dev. release you would probably have to do something like:
`install P/PM/PMQS/Compress-Zlib-2.000_01.tar.gz`
Not sure why SA doesn't use this functionality though.
Re: Debian Packages for 3.1.0-rc2
Posted by Bob Proulx <bo...@proulx.com>.
jdow wrote:
> Is it found in a handy place in CPAN?
> {^_^}
Because CPAN is for released modules (I am talking designed process
and not observed quality here) I don't see how it could get there
until it is actually released.
If you are installing by CPAN and not using a package manager then
using the built packages won't work for you. And using CPAN won't
work for you. You would need to pull the SA packages directly and do
your own build.
Or find a CPAN configuration that pulls from someone who has already
done this that is not from CPAN. :-)
Bob
Re: Debian Packages for 3.1.0-rc2
Posted by jdow <jd...@earthlink.net>.
Is it found in a handy place in CPAN?
{^_^}
----- Original Message -----
From: "Duncan Findlay" <du...@debian.org>
Re: Debian Packages for 3.1.0-rc2
Posted by Chris Thielen <cm...@someone.dhs.org>.
Duncan Findlay wrote:
>On Mon, Aug 29, 2005 at 11:41:39PM -0400, Duncan Findlay wrote:
>
>
>Debian packages or 3.1.0-rc2 are available from the experimental
>distibution (version 3.0.99pre3.1.0+rc2-1). I'd appreciate help
>testing them, so that all the bugs in the packaging can be worked out
>by the time 3.1.0 is uploaded to unstable.
>
Hi Duncan,
Installed cleanly for me on my Sarge box. I merged my local.cf into the
updated package one.
Aug 31 14:04:27 ns1 spamd[4269]: Can't locate Sys/Hostname/Long.pm in @INC (@INC contains: ../lib /usr/share/perl5 /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl) at /usr/share/perl5/Mail/SPF/Query.pm line 328, <GEN12> line 64.
I'm getting these in mail.log, but that's because libmail-spf-query-perl
only suggests libsys-hostname-long-perl (which I don't have installed).
I believe this is a warning at worst since the package is only
suggested, and I assume it is out of your control.
I am seeing some other anomalous messages in the log, but I believe they
are not packaging related.
Chris
Debian Packages for 3.1.0-rc2
Posted by Duncan Findlay <du...@debian.org>.
On Mon, Aug 29, 2005 at 11:41:39PM -0400, Duncan Findlay wrote:
> *** THIS IS A RELEASE CANDIDATE ONLY, NOT THE FINAL 3.1.0 RELEASE ***
>
> SpamAssassin 3.1.0-rc2 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).
Debian packages or 3.1.0-rc2 are available from the experimental
distibution (version 3.0.99pre3.1.0+rc2-1). I'd appreciate help
testing them, so that all the bugs in the packaging can be worked out
by the time 3.1.0 is uploaded to unstable.
Packages.debian.org hasn't been updated yet, but if you have the
appropriate line for experimental in your /apt/sources.list, you can
try:
# apt-get install spamassassin/experimental spamc/experimental
Or you can download the files from your favourite (up-to-date) mirror:
ftp://ftp.us.debian.org/debian/pool/main/s/spamassassin/spamassassin_3.0.99pre3.1.0+rc2-1_all.deb
ftp://ftp.us.debian.org/debian/pool/main/s/spamassassin/spamc_3.0.99pre3.1.0+rc2-1_i386.deb
All bugs in the Debian packaging should be reported to the Debian BTS,
not the SpamAssassin bugzilla.
Thanks,
--
Duncan Findlay
Fedora Packages for 3.1.0-rc2
Posted by Warren Togami <wt...@redhat.com>.
Duncan Findlay wrote:
> *** THIS IS A RELEASE CANDIDATE ONLY, NOT THE FINAL 3.1.0 RELEASE ***
>
> SpamAssassin 3.1.0-rc2 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).
>
spamassassin-3.1.0-rc2 is now available in Fedora Development "rawhide",
which will eventually become our FC5 release scheduled for February, 2006.
http://cvs.fedora.redhat.com/viewcvs/rpms/spamassassin/
You may checkout spamassassin/devel and "make srpm" in order to obtain
the latest version of our SRPM. Rebuild of this source RPM should work
fine on any version of Fedora Core.
http://cvs.fedora.redhat.com/core.shtml
Anonymous CVS Checkout instructions
Warren Togami
wtogami@redhat.com
Debian Packages for 3.1.0-rc2
Posted by Duncan Findlay <du...@debian.org>.
On Mon, Aug 29, 2005 at 11:41:39PM -0400, Duncan Findlay wrote:
> *** THIS IS A RELEASE CANDIDATE ONLY, NOT THE FINAL 3.1.0 RELEASE ***
>
> SpamAssassin 3.1.0-rc2 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).
Debian packages or 3.1.0-rc2 are available from the experimental
distibution (version 3.0.99pre3.1.0+rc2-1). I'd appreciate help
testing them, so that all the bugs in the packaging can be worked out
by the time 3.1.0 is uploaded to unstable.
Packages.debian.org hasn't been updated yet, but if you have the
appropriate line for experimental in your /apt/sources.list, you can
try:
# apt-get install spamassassin/experimental spamc/experimental
Or you can download the files from your favourite (up-to-date) mirror:
ftp://ftp.us.debian.org/debian/pool/main/s/spamassassin/spamassassin_3.0.99pre3.1.0+rc2-1_all.deb
ftp://ftp.us.debian.org/debian/pool/main/s/spamassassin/spamc_3.0.99pre3.1.0+rc2-1_i386.deb
All bugs in the Debian packaging should be reported to the Debian BTS,
not the SpamAssassin bugzilla.
Thanks,
--
Duncan Findlay
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Thomas Hochstein <ml...@ancalagon.inka.de>.
Duncan Findlay schrieb:
>> Does this fix the problem with SIGCHLD?
>
> Do you have a bug number? What problem with SIGCHLD are you talking
> about?
The one reported by him in
<ea...@ucsc.edu>, I think.
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Duncan Findlay <du...@debian.org>.
On Mon, Aug 29, 2005 at 11:21:20PM -0700, John Rudd wrote:
>
> On Aug 29, 2005, at 9:29 PM, Duncan Findlay wrote:
>
> >On Mon, Aug 29, 2005 at 08:57:31PM -0700, John Rudd wrote:
> >>Does this fix the problem with SIGCHLD?
> >
> >Do you have a bug number? What problem with SIGCHLD are you talking
> >about?
> >
>
> I do not have a bug number. It's a problem I mentioned on the list
> just two days ago:
Issues mentioned on the users list won't get fixed unless, a) it's a
bug in SpamAssassin and b) it's filed in bugzilla. Most of the
developers don't read the users list very thoroughly, and we rely on
bugs being reported to bugzilla.
So, I think the answer is probably no.
Furthermore, it's way too late in the release cycle to be messing with
SIGCHLD. This area is full of perl bugs and what we've got seems to
work in all (most?) situations? Feel free to file a bug, and maybe
it'll be targeted for 3.1.1, but someone has already suggested that
it's not a problem in SpamAssassin.
--
Duncan Findlay
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Loren Wilton <lw...@earthlink.net>.
It isn't fixed in rc2.
You only posted that analysis 2 days before the rc2 release, and the tarball
had already been cut at the time you posted the message. (It takes a day or
two between release cutoff and the release showing up, since it needs to be
tested before the announcement.)
Furthermore, you only posted the notice here in the users group where it
could easily be missed by the SA devs. The proper thing to do is open a bug
in Bugzilla on this subject, and include the info that you posted here.
FWIW, the change that is causing the problems was a deliberate change to
work around another problem in another tool. So the fix isn't likely to be
as simple as backing out that change, since that would just bring the
previous bug back.
Loren
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by John Rudd <jr...@ucsc.edu>.
I don't remember seeing any subsequent messages on the subject. And,
over on the mimedefang list the developer worked out a work-around in
mimedefang, but it still sounded like it was an SA problem.
On Aug 30, 2005, at 1:13 AM, jdow wrote:
> As I remember subsequent messages on this topic a debug run showed the
> problem was in MimeDefang. So of course it is not fixed.
> {^_^}
> ----- Original Message ----- From: "John Rudd" <jr...@ucsc.edu>
>
>> On Aug 29, 2005, at 9:29 PM, Duncan Findlay wrote:
>>> On Mon, Aug 29, 2005 at 08:57:31PM -0700, John Rudd wrote:
>>>> Does this fix the problem with SIGCHLD?
>>>
>>> Do you have a bug number? What problem with SIGCHLD are you talking
>>> about?
>>>
>> I do not have a bug number. It's a problem I mentioned on the list
>> just two days ago:
>>> From: John Rudd <jr...@ucsc.edu>
>>>
>>> This is a problem that some mimedefang people are experiencing with
>>> SA 3.1 rc1.
>>>
>>> (mimedefang slave processes are becoming un-killable due to a
>>> mis-feature in SA 3.1 which messes with SIGCHLD)
>
>
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by jdow <jd...@earthlink.net>.
From: "Kelson" <ke...@speed.net>
> jdow wrote:
>> As I remember subsequent messages on this topic a debug run showed the
>> problem was in MimeDefang. So of course it is not fixed.
>
> There was no subsequent discussion. I'm not sure there was even a
> single reply.
>
> The problem came up in another thread, and the submitter was advised to
> take it to the MIMEDefang list. The lead MD developer looked at it,
> found that SA was messing around with SIGCHLD, and came up with a
> workaround (which will be included in the next version of MD), but seems
> to consider it a bug (or at least a misfeature) in SA. At that point
> John posted David Skoll's analysis of the problem over here.
OK. I'd only followed it peripherally because I do not use such things
as amavis and mimedefang. They seem to have their dark side as well as
their light side. It's like messing with the Force. You hicough and
you're sliced beef.
{^_^}
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Loren Wilton <lw...@earthlink.net>.
> The problem came up in another thread, and the submitter was advised to
> take it to the MIMEDefang list. The lead MD developer looked at it,
> found that SA was messing around with SIGCHLD, and came up with a
> workaround (which will be included in the next version of MD), but seems
> to consider it a bug (or at least a misfeature) in SA. At that point
> John posted David Skoll's analysis of the problem over here.
FWIW, any routine at any level of a program is free to mess with any of the
signals, just so long as they restore them. SA does it all over the place
in many situations, not just the one that annoyed the MD developer. Since
SA is the one starting the timer that is going to bean the child in X
seconds, it has a perfectly valid right to fiddle with the signals that will
announce when the child gets boinked.
Loren
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Kelson <ke...@speed.net>.
jdow wrote:
> As I remember subsequent messages on this topic a debug run showed the
> problem was in MimeDefang. So of course it is not fixed.
There was no subsequent discussion. I'm not sure there was even a
single reply.
The problem came up in another thread, and the submitter was advised to
take it to the MIMEDefang list. The lead MD developer looked at it,
found that SA was messing around with SIGCHLD, and came up with a
workaround (which will be included in the next version of MD), but seems
to consider it a bug (or at least a misfeature) in SA. At that point
John posted David Skoll's analysis of the problem over here.
--
Kelson Vibber
SpeedGate Communications <www.speed.net>
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by jdow <jd...@earthlink.net>.
As I remember subsequent messages on this topic a debug run showed the
problem was in MimeDefang. So of course it is not fixed.
{^_^}
----- Original Message -----
From: "John Rudd" <jr...@ucsc.edu>
>
> On Aug 29, 2005, at 9:29 PM, Duncan Findlay wrote:
>
>> On Mon, Aug 29, 2005 at 08:57:31PM -0700, John Rudd wrote:
>>> Does this fix the problem with SIGCHLD?
>>
>> Do you have a bug number? What problem with SIGCHLD are you talking
>> about?
>>
>
> I do not have a bug number. It's a problem I mentioned on the list
> just two days ago:
>
>
>
>
>> From: John Rudd <jr...@ucsc.edu>
>>
>> This is a problem that some mimedefang people are experiencing with SA
>> 3.1 rc1.
>>
>> (mimedefang slave processes are becoming un-killable due to a
>> mis-feature in SA 3.1 which messes with SIGCHLD)
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by John Rudd <jr...@ucsc.edu>.
On Aug 29, 2005, at 9:29 PM, Duncan Findlay wrote:
> On Mon, Aug 29, 2005 at 08:57:31PM -0700, John Rudd wrote:
>> Does this fix the problem with SIGCHLD?
>
> Do you have a bug number? What problem with SIGCHLD are you talking
> about?
>
I do not have a bug number. It's a problem I mentioned on the list
just two days ago:
> From: John Rudd <jr...@ucsc.edu>
> Date: August 27, 2005 7:32:24 PM PDT
> To: Spamassassin <us...@spamassassin.apache.org>
> Subject: Problems with SpamAssassin 3.1 RC1and MIMEDefang
> Return-Path:
> <us...@spamassassin.apache.org>
> X-Ucsc-Cats-Mailscanner-Spamcheck:
> X-Ucsc-Cats-Mailscanner-Spamcheck: not spam, SpamAssassin (score=0,
> required 8)
>
>
> This is a problem that some mimedefang people are experiencing with SA
> 3.1 rc1.
>
> (mimedefang slave processes are becoming un-killable due to a
> mis-feature in SA 3.1 which messes with SIGCHLD)
>
>
> Begin forwarded message:
>
>> From: "David F. Skoll" <df...@roaringpenguin.com>
>> Date: August 27, 2005 6:01:28 PM PDT
>> To: mimedefang@lists.roaringpenguin.com
>> Subject: Re: [Mimedefang] Problems with SpamAssassin 3.1 RC1and
>> MIMEDefang
>>
>> Martin Blapp wrote:
>>
>>
>>> Please download SA3.1 Pre 1 and try yourself.
>>
>> I downloaded it, and didn't have to try anything; the problem was
>> obvious
>> after I read the SA 3.1 code.
>>
>> It's a bug in SA 3.1.
>>
>> Look at the file "Dns.pm", in the routine enter_helper_run_mode.
>> We see this code:
>>
>> # enforce SIGCHLD as DEFAULT; IGNORE causes spurious kernel warnings
>> # on Red Hat NPTL kernels (bug 1536), and some users of the
>> # Mail::SpamAssassin modules set SIGCHLD to be a fatal signal
>> # for some reason! (bug 3507)
>> $self->{old_sigchld_handler} = $SIG{CHLD};
>> $SIG{CHLD} = 'DEFAULT';
>>
>> There's a leave_helper_run_mode that resets the SIGCHLD handler to its
>> old value.
>>
>> HOWEVER: If the slave dies sometime between enter_helper_run_mode and
>> leave_helper_run_mode, the multiplexor never gets a SIGCHLD signal.
>>
>> I don't know why the SA developers are even monkeying with the
>> SIGCHLD handler
>> in the Perl module; you'd have to ask them. It seems like a bad idea
>> to me.
>>
>> I think I have a workaround; I'll release a beta soon.
>> In the meantime, I believe that turning off the embedded interpreter
>> will
>> make it work properly.
>>
>> Regards,
>>
>> David.
>
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Duncan Findlay <du...@debian.org>.
On Mon, Aug 29, 2005 at 08:57:31PM -0700, John Rudd wrote:
> Does this fix the problem with SIGCHLD?
Do you have a bug number? What problem with SIGCHLD are you talking
about?
--
Duncan Findlay
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by Phil Barnett <ph...@philb.us>.
On Monday 29 August 2005 11:57 pm, John Rudd wrote:
> Does this fix the problem with SIGCHLD?
Do you really need to quote the entire message?
--
Don't think that a small group of dedicated individuals can't change the
world. it's the only thing that ever has.
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
Posted by John Rudd <jr...@ucsc.edu>.
Does this fix the problem with SIGCHLD?
On Aug 29, 2005, at 8:41 PM, Duncan Findlay wrote:
> *** THIS IS A RELEASE CANDIDATE ONLY, NOT THE FINAL 3.1.0 RELEASE ***
>
> SpamAssassin 3.1.0-rc2 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).
>
> This is a release candidate, and NOT the general availability release
> (yet.) We think it's pretty rock solid, however. ;) Please test it
> out, and report any bugs to:
> http://bugzilla.spamassassin.org
>
>
> 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/released/Mail-SpamAssassin-3.1.0-
> rc2.tar.bz2
>
> http://spamassassin.apache.org/released/Mail-SpamAssassin-3.1.0-
> rc2.tar.gz
>
> http://spamassassin.apache.org/released/Mail-SpamAssassin-3.1.0-
> rc2.zip
>
> md5sum:
>
> 1e2ecf555d62deae136b08fb482e8f68 Mail-SpamAssassin-3.1.0-rc2.tar.bz2
> 41fe5c0c5ab226e0d33de20c10f69240 Mail-SpamAssassin-3.1.0-rc2.tar.gz
> 91bc48f87eb520040ece42dced886243 Mail-SpamAssassin-3.1.0-rc2.zip
>
> sha1sum:
>
> a68a040c2b2c51d7284fbd15336e639a32a0d45d
> Mail-SpamAssassin-3.1.0-rc2.tar.bz2
> a20f3d82743186af085fac1deb540c22ebdc8ce1
> Mail-SpamAssassin-3.1.0-rc2.tar.gz
> f76cc96981c6766d48edd6ed60c621036a9dfcf5
> Mail-SpamAssassin-3.1.0-rc2.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 changes from 3.1.0-rc1
> ---------------------------------
>
> - (Many) Documentation Fixes.
>
> - Fixed problem in the PostgreSQL Bayes storage engine (bug 4531).
>
> - Syslog entries now properly identified as 'spamd' instead of
> 'spamassassin' (bug 4533).
>
> - Fixed situation where pyzor and dcc could be left running after a
> timeout (bug 4518).
>
> - Better handling of warnings while loading (bug 4536).
>
> - Spamc learning/reporting is disabled by default in spamd, can be
> enabled with the "--allow-tell" or "-l" option to spamd (bug 4546).
>
> - Better support IPv6 resolvers (bug 4412).
>
> - Better handle peculiarities with certain MIME boundaries (bug 4535).
>
> - Fix unitialized value warnings in spamd with TELL commands (bug
> 4552).
>
> - Fix sa-learn's --local option, which previously was always enabled
> (bug 4494).
>
>
> 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.
>
>
> --
> Duncan Findlay