https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
Mark Martinec changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #14 from Mark Martinec 2011-09-21 16:03:34
UTC ---
> Mark: Now i can see problem isn't with bayes (btw, here is timing with
> bayes: timing:
>
> total 112630 ms - init: 12826 (11.4%), parse: 586 (0.5%),
> extract_message_met
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #13 from Marcin 2011-09-21 15:10:56 UTC ---
AXB: I think exim acl doesn't bring any new idea because i can reproduce this
problem using spamc. Imho problem is: why spamd idles and doesn't return any
response to client?
Mark:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #12 from John Hardin 2011-09-21 13:17:01 UTC
---
(In reply to comment #6)
> Please notice: spamd scans this email through ~2 minutes then idles but spamc
> doesn't return results of scan. Spamc timeouts after 10 minutes. Thi
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #11 from Mark Martinec 2011-09-21 10:36:38
UTC ---
We still do not have a confirmation that the culprit is Bayes.
Marcin, please re-read what John Hardin has asked:
> I find it really difficult to believe that Bayes would c
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #10 from AXB 2011-09-21 10:25:19 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > > spamc cannot timeout after ten minutes when the default is 5
> > > -t *timeout*, --timeout=*timeout*
> > > Set the tim
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #9 from AXB 2011-09-21 10:14:31 UTC ---
(In reply to comment #8)
> > spamc cannot timeout after ten minutes when the default is 5
> > -t *timeout*, --timeout=*timeout*
> > Set the timeout for spamc-to-spamd communicat
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #8 from Marcin 2011-09-21 10:10:20 UTC ---
> spamc cannot timeout after ten minutes when the default is 5
> -t *timeout*, --timeout=*timeout*
> Set the timeout for spamc-to-spamd communications (default: 600, 0
Are y
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #7 from AXB 2011-09-21 09:44:54 UTC ---
(In reply to comment #6)
> Yes, i know this messages is huge. I've to scan such big emails (second option
> is to use diffrent spamd for big emails but it's not always possible). I'm
>
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #6 from Marcin 2011-09-21 09:29:30 UTC ---
Yes, i know this messages is huge. I've to scan such big emails (second option
is to use diffrent spamd for big emails but it's not always possible). I'm
using postgresql-9.0 as back
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #5 from AXB 2011-09-21 09:03:39 UTC ---
(In reply to comment #4)
> Created attachment 4962 [details]
> sample email
>
> Please try to scan this mail using spamc client.
Either I've missed something in this bug or:
You mean
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
--- Comment #4 from Marcin 2011-09-21 08:03:55 UTC ---
Created attachment 4962
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=4962
sample email
Please try to scan this mail using spamc client.
--
Configure bugmail:
ht
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
Marcin changed:
What|Removed |Added
CC||b...@mejor.pl
--- Comment #3 from Marc
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
John Hardin changed:
What|Removed |Added
CC||jhar...@impsec.org
--- Comment #2
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
Darxus changed:
What|Removed |Added
CC||dar...@chaosreigns.com
--- Comment #1
15 matches
Mail list logo
