Bug 4002 - Do Bayes expiry after message has been returned to client.
Summary: Do Bayes expiry after message has been returned to client.
Status: RESOLVED DUPLICATE of bug 3466
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 enhancement
Target Milestone: 3.3.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on: 3983 3986
Blocks:
  Show dependency tree
 
Reported: 2004-11-26 16:16 UTC by Theo Van Dinter
Modified: 2008-01-02 14:44 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Theo Van Dinter 2004-11-26 16:16:39 UTC 
In spamd currently, a message is received, it is checked, during the Bayes check the code 
opportunistically tries a journal sync and db expiry, then the processing completes and the message is 
passed back to the client.  This means that the client has to sit and wait during a db expiry, which is 
potentially going to take several minutes.

Instead, we should fully process the message, return it, then worry about doing bayes expiry.  This 
should now be possible via bug 3983 and bug 3986.
Comment 1 Theo Van Dinter 2004-11-26 16:17:25 UTC 
setting milestone, etc.
Comment 2 Daniel Quinlan 2005-01-19 16:39:31 UTC 
++1 to this idea
Comment 3 Daniel Quinlan 2005-03-29 15:11:52 UTC 
moving to 3.2.0
Comment 4 Justin Mason 2006-12-12 12:40:21 UTC 
moving RFEs and low-priority stuff to 3.3.0 target
Comment 5 Justin Mason 2008-01-02 14:44:01 UTC 
This appears to have been implemented already:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3466

*** This bug has been marked as a duplicate of 3466 ***