On Thu, 2007-11-01 at 16:28 -0400, Daryl C. W. O'Shea wrote:
> Robert Fitzpatrick wrote:
> > I have the following error message in the logs, didn't even notice until
> > tracking down an email for a user today, but been happening in all my
> > logs back the last week. All three servers running mail filtering to
> > pgsql db have this error including the server which hosts the db. I find
> > no problems with filtering and BAYES scoring seems to be working and is
> > tagging messages fine. So, I assume this means the learning part is not
> > working? However, looking at bayes_var in the db, I see token, spam and
> > ham counts all updating from AWL I assume. Can someone offer feedback to
> > help determine what exactly is the issue at hand? Thanks in advance.
> 
> I don't have the time to compare the backtrace to the actual code, so 
> I'll guess instead.  Disable bayes_auto_expire and see if the errors go 
> away.  It's probably bayes expiries taking longer than the amavis 
> timeout limit.

Thanks for the response. I did not have the setting defined in local.cf,
I added 'bayes_auto_expire 0' and it is still happening. I am using
Postfix + Maia mailguard, which is a amavisd-new 2.2 product. I made the
change and restarted amavisd.

-- 
Robert

Reply via email to