Perhaps I spoke too quickly when I suggested that the bayes
expiry code must be broken. I finally read David Lee's message
carefully and realized that the expiry code might be getting timed
out by mimedefang or sendmail and interrupted before it has time to
complete. I should have read it earlier but I've been fighting the
Novarg/Mydoom virus all day and haven't had time to get back to the
Bayes problem. My apologies for suggesting there must be a bug in
the code. I'll followup on the "getting timed out" possibility.
- rick
On Tue, 27 Jan 2004, Theo Van Dinter wrote:
> On Tue, Jan 27, 2004 at 03:57:56PM +0000, David Lee wrote:
> > The MailScanner maintainer, Julian Field, is very responsive, and he has
> > already coded up an alternative way of driving SA from MS, so that its use
> > of SA can avoid auto-expire (and thereby avoid the possible multiple
> > simultaneous expires) and instead do a more controlled, occasional and
> > explicit expire.
>
> Which is different from disabling auto_expire ("bayes_auto_expire 0")
> in the config and running "sa-learn --force-expire" when you want?
>
> The code already tries to avoid multiple parallel expire runs BTW.
> First, the DB is locked, second, the running expire updates a specific
> magic token in the DB which tells any other instance that an expire is
> occuring and they should abort.
>
> So what's the issue?
>
> --
> Randomly Generated Tagline:
> Who wants to remember that escape-x-alt-control-left shift-b puts you into
> super-edit-debug-compile mode?
> (Discussion in comp.os.linux.misc on the intuitiveness of commands, especially
> Emacs.)
>
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
