yeah, I saw that too -- think it's fixed now.
--j.
Theo Van Dinter writes:
> fyi.
>
> - Forwarded message -
>
> [Using '-90 days' for --after setting]
> status: starting scan stage now: 2007-08-03
> 05:12:28
> print() on closed filehandle CACHE at
> /home
fyi.
- Forwarded message -
[Using '-90 days' for --after setting]
status: starting scan stage now: 2007-08-03
05:12:28
print() on closed filehandle CACHE at
/home/corpus/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/AICache.pm
line 162.
Can't writ
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 10:13 ---
Bingo... I am. Good catch!
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 10:07 ---
you could be using dccifd, which doesn't require forking a helper process; that
wouldn't display this bug, then.
--- You are receiving this mail becaus
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
---
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 09:46 ---
(In reply to comment #52)
> Weird, DCC worked fine for me after upgrading from 3.2.1 to 3.2.3
um, 3.2.3 hasn't been released yet ;)
--- You are receiv
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 09:38 ---
Weird, DCC worked fine for me after upgrading from 3.2.1 to 3.2.3 (CPAN/root
installation test failure prevented 3.2.2) and all tests passed (Perl 5.8.5)...
P
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 09:38 ---
Created an attachment (id=4079)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4079&action=view)
quick-and-dirty for installed system
-
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 08:36 ---
committers: more votes are needed. this is a critical bug, rendering spamd
unusable for lots of sites. we need to fix it in SVN and release a 3.2.3 ASAP...
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3852
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 08:34 ---
ok, I should add some comments based on how far I got.
There's a branch in SVN now at
https://svn.apache.org/repos/asf/spamassassin/branches/jm_bug_3852_two_
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5511
--- Additional Comments From [EMAIL PROTECTED] 2007-08-03 08:30 ---
This change of network lookups timeouts dramatically increases the time of
scan.
Sequential scanning of 1494 messages on the same machine (FreeBSD 6.2, Perl
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5584
Summary: tcp timeout
Product: Spamassassin
Version: 3.1.8
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: sp
Justin Mason wrote:
ok, let's vote to change the procedure: that changes in the "rules" tree
be considered Commit-Then-Review, even when changes in the code (such as
"lib") are considered Review-Then-Commit.
My vote: +1
+1
13 matches
Mail list logo
