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/MiF9iBJsIts driving me crazy, because I can not found the reason. If you need something else, do not hesitate to come back to meThanks 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.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
