http://bugzilla.spamassassin.org/show_bug.cgi?id=3483
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #2126 is|0 |1
obsolete| |
------- Additional Comments From [EMAIL PROTECTED] 2004-07-14 23:35 -------
Created an attachment (id=2129)
--> (http://bugzilla.spamassassin.org/attachment.cgi?id=2129&action=view)
patch to move opportunistic calls
ok...
this patch has all the same stuff as 2126, plus:
- fixed the comment about cleanup()
- added journal sync only option to opportunistic_calls function
- added opportunistic_calls() call to is_sync_available, only for journal sync.
needs caller_will_untie magic around the call so that a sync won't untie and
leave the nham/nspam check with a 0 count.
- fixes small sync_due issue -- the check that says we should sync if the
journal exists and we haven't synced in the past day needed to be updated to
ignore this if a sync hasn't occurred before. this fixes the issue where the
first message creates the journal, then the second message forces a sync no
matter if the filesize is > max size or not. once the sync occurs for size
reasons, the 1 day rule will take effect again.
I have now verified that this fixes the issue in my test sandbox. I learned a
message to the journal, which also creates empty database files. I then
lowered the max journal size to 1 byte, and scanned another random message.
is_scan_available() properly saw that a sync was due, the sync occured, left
the db in r/w state, then is_scan_available() saw only 1 message was in the DB,
and untied/return false.
I think this is all set now. :)
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
