Date: Thu, 31 May 2012 10:45:11 +0000
From: [email protected]
To: [email protected]
Subject: Re: [policyd-users] Policyd/amavisd stop processing messages after
policy update
On 05/31/12 10:41, Manel Gimeno Zaragozá wrote:
On 05/31/12 09:47, Manel Gimeno Zaragozá wrote:
I'm trying to solve this issue. I wrote a
post a week ago but I was getting problems uploading
the logs.
After some test I didn't found the reason why
policyd/amavis stop processing messages after a policy
update. I have to restart amavisd process to get a
SPAM/VIRUS scan again.
You can find all my logs in attached or you can
downloaded in the following url:
http://db.tt/MiF9iBJs
Its driving me crazy, because I can not found the
reason. If you need something else, do not hesitate to
come back to me
Thanks for your help!!!
For us to investigate this we need to reproduce it. With the
sheer number of posts in the past week, this is going to take
some time. We tend to prioritize issues which affect multiple
users higher than those that affect fewer users.
If you don't mind assisting us here, it would greatly speed
things up. I would suggest if you can prove with logs that
amavis is not getting an updated ruleset, is to maybe log all
the steps you use to reproduce this as a issue on the devlabs
site.
It makes it much easier and faster if we have a sql db dump of
the policyd db you're using to test with, a copy of your
Policyd config file, a copy of your Amavisd config file, a
copy of your Postfix config file (master & main). Details
like which OS you're using is also helpful, which version of
Amavisd, which version of Policyd. Then the logs showing the
incorrect behavior with full debugging everywhere turned on.
If you can provide the above, a fix should be pretty trivial
and fast to spin. I think Robert has spent most of the week
compiling the above details for each person that reported
issues and only yesterday actually got down to trying to
reproduce them.
Hello,
I've been testing my environment, waiting for you analisis about what happen
and I've notice that policyd is not able to process a bunch of mails (using
smtp-source). The problem is that some messages are processed, with amavis SPAM
headers (supplied by policyd) and other just go through and there is no sign of
policyd/amavis in the headers. The simpton are the same as before, it look like
policyd/amavisd get stuck or "dead" after a bunch of emails, even though any
process is really dead.
I've tried to increase the number of servers in cluebringer.conf:
min_servers=8
min_spare_servers=8
max_spare_servers=16
max_servers=64
max_requests=1000
but nothing change.
have you see problems lilke this in other instalations? could it be caused by
OS incompatibility? If I use amavis without policyd, it is able to process 1000
mails in 2 minutes and all marked as SPAM. But with policyd it looks like it
can not process a small bunch.
Could you please guide me to some solution?
As I have said before, I can not post all my logs due to I'm getting returned
the email from your server due to "size". Please, explain me the best way to
you to upload the log/conf files
Thanks & Regards.
Manel.
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
