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.
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
OK, I've added an sqldump to the zip, where you can find all the config files
and logs with debug enabled. You can downloaded it from:
http://db.tt/MiF9iBJs
I'm ussing URL method to pass the logs because It is always rejecting the email
with file attached due to "mail size restriction".
More Info:
#cat /etc/centos-release
CentOS release 6.2 (Final)
#rpm -qa | grep -iE "amavis|policyd|postfix|mysql|sasl|dspam"
amavisd-new-2.6.4-2.el5.x86_64
postfix-2.6.6-2.2.el6_1.x86_64
mysql-5.1.61-1.el6_2.1.x86_64
dspam-3.10.2-1.el6.x86_64
dspam-devel-3.10.2-1.el6.x86_64
cyrus-sasl-plain-2.1.23-13.el6.x86_64
cyrus-sasl-ldap-2.1.23-13.el6.x86_64
cyrus-sasl-devel-2.1.23-13.el6.x86_64
cyrus-sasl-2.1.23-13.el6.x86_64
cyrus-sasl-lib-2.1.23-13.el6.x86_64
mysql-libs-5.1.61-1.el6_2.1.x86_64
mysql-server-5.1.61-1.el6_2.1.x86_64
dspam-libs-3.10.2-1.el6.x86_64
dspam-client-3.10.2-1.el6.x86_64
dspam-mysql-3.10.2-1.el6.x86_64
dspam-web-3.10.2-1.el6.x86_64
mod_auth_mysql-3.0.0-11.el6_0.1.x86_64
php-mysql-5.3.3-3.el6_2.8.x86_64
perl-DBD-MySQL-4.013-3.el6.x86_64
# Policyd version: cluebringer-snapshot-2.1.x-201205100639.tar.gz
On the other hand, I do not understand what exactly you are asking for in the
second paragraph: "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."
Thanks! i really apreciate your help!
Manel.
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
