Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
On 9/7/05, Loren Wilton [EMAIL PROTECTED] wrote: has this been opened as a bug in BZ yet? I haven't seen a sign of it. I hope the OP does this, I'd hate to have to try to track back through 3 weeks of deleted mail to find the original posting. Especially since I don't remember who posted it! John Rudd, on August 27. Took me about 15 seconds to find it in gmail (well, really, to find the message John sent on August 29 in which he quoted the August 27 mail). The subject was Problems with SpamAssassin 3.1 RC1and MIMEDefang.
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
On Sep 8, 2005, at 10:34 AM, Bart Schaefer wrote: On 9/7/05, Loren Wilton [EMAIL PROTECTED] wrote: has this been opened as a bug in BZ yet? I haven't seen a sign of it. I hope the OP does this, I'd hate to have to try to track back through 3 weeks of deleted mail to find the original posting. Especially since I don't remember who posted it! John Rudd, on August 27. Took me about 15 seconds to find it in gmail (well, really, to find the message John sent on August 29 in which he quoted the August 27 mail). The subject was Problems with SpamAssassin 3.1 RC1and MIMEDefang. It looks like Loren did find it and enter it: http://bugzilla.spamassassin.org/show_bug.cgi?id=4573 (and, I'm sorry I'm not the one who entered it; I'm not the one who actually has been having the problem, I was just trying to get it on the SA developers radar after it popped up on the mimedefang mailing list ... so I was leery of starting the next step when I wouldn't be able to give actual technical details)
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
On 7 Sep 2005 at 18:46, Loren Wilton wrote: has this been opened as a bug in BZ yet? I can't find it. I'd like to get this worked out on the BZ so we can track it as an rc3 issue (or not). I haven't seen a sign of it. I hope the OP does this, I'd hate to have to try to track back through 3 weeks of deleted mail to find the original posting. Especially since I don't remember who posted it! My apologies. I believe I was the original poster; I opened Bugzilla ID #4556, posted an strace which Justin suggested a MIMEDefang problem and then left civilization for vacation. I see much has occurred in my absence! I'm going to close BZ 4556 and mark it as a duplicate of 4573. Nels Lindquist * Information Systems Manager Morningstar Air Express Inc.
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Rudd writes: On Sep 8, 2005, at 10:34 AM, Bart Schaefer wrote: On 9/7/05, Loren Wilton [EMAIL PROTECTED] wrote: has this been opened as a bug in BZ yet? I haven't seen a sign of it. I hope the OP does this, I'd hate to have to try to track back through 3 weeks of deleted mail to find the original posting. Especially since I don't remember who posted it! John Rudd, on August 27. Took me about 15 seconds to find it in gmail (well, really, to find the message John sent on August 29 in which he quoted the August 27 mail). The subject was Problems with SpamAssassin 3.1 RC1and MIMEDefang. It looks like Loren did find it and enter it: http://bugzilla.spamassassin.org/show_bug.cgi?id=4573 (and, I'm sorry I'm not the one who entered it; I'm not the one who actually has been having the problem, I was just trying to get it on the SA developers radar after it popped up on the mimedefang mailing list ... so I was leery of starting the next step when I wouldn't be able to give actual technical details) Fair enough. That indeed is why I was wary of opening it myself; without someone close to the original reporter, what often winds up happening is that we speculate uselessly, and occasionally receive forwarded comments that have been filtered via chinese whispers. it can be messy. (I think in this case we've gotten away with it safely, though, as I see David is now commenting on the bug.) - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFDIKEvMJF5cimLx9ARAqs2AJ4qxluWU6clarTvrPK57LWGG6YJqwCfa8ki 3zhLXgKnFHUjfn3Q0FfLP5A= =WpCf -END PGP SIGNATURE-
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Loren Wilton writes: 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. has this been opened as a bug in BZ yet? I can't find it. I'd like to get this worked out on the BZ so we can track it as an rc3 issue (or not). - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFDH5PlMJF5cimLx9ARApOqAKCEkWQTjIFqHo/36SWvLrs9agQNVACgqaMw RMWWraH/HuNwRSbQSltj81M= =h6p1 -END PGP SIGNATURE-
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
has this been opened as a bug in BZ yet? I can't find it. I'd like to get this worked out on the BZ so we can track it as an rc3 issue (or not). I haven't seen a sign of it. I hope the OP does this, I'd hate to have to try to track back through 3 weeks of deleted mail to find the original posting. Especially since I don't remember who posted it! Loren
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Loren Wilton writes: 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. Following up on this -- yes, Loren has nailed it here. It would be best to open this as a bug in bugzilla for further followup. - --j. (just back from a week's vacation) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFDHki0MJF5cimLx9ARAmrQAJsESlKBkU7bdWHCJMWGRMn+7kwfzACdH2eD QCjLAPOEV25EZKwZUJmG+ZQ= =Y2Xl -END PGP SIGNATURE-
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
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 [EMAIL PROTECTED]
Date: August 27, 2005 7:32:24 PM PDT
To: Spamassassin users@spamassassin.apache.org
Subject: Problems with SpamAssassin 3.1 RC1and MIMEDefang
Return-Path:
[EMAIL PROTECTED]
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 [EMAIL PROTECTED]
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!
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 [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
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!
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 [EMAIL PROTECTED], I think.
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
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 [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
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!
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 signature.asc Description: Digital signature
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
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!
From: Kelson [EMAIL PROTECTED]
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!
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!
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!
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!
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 [EMAIL PROTECTED] 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
