>>> I thoutht I was chasing a strange bug until I found a pattern in the way >>> Amavis changes take effect. In my tests, most changes require a restart >>> of Amavis. This seems quite odd in that the change is in the policyd >>> database. The follwoing table illistrates this behaviour: >>> >>> Amavis bypass_ Virus is >>> Restarted virus_checks Checked >>> >>> Yes Inherit Yes (checks enabled by default) >>> Yes Yes (should not check for virus) >>> Yes No (restart fixed it) >>> Inherit Yes (no restart needed in this case) >>> Yes Yes (should not check for virus) >>> Yes No (restart fixed it) >>> Inherit Yes (no restart needed in this case) >>> Yes Yes (should not check for virus) >>> Yes No (restart fixed it) >>> No No (should have checked for virus) >>> Inherit No (should have checked for virus) >>> Yes Yes (restart fixed it) >>> >> This makes very little sense .... policyd overwrites the policy bank >> every time amavisd processes a message. >> >> I'll need to try reproduce this. >> >> >>> I have only checked one setting. Under what circumstances is an Amavis >>> restart needed? >>> >> It shouldn't be needed at all. >> > > What can I do to help whith this? > Well I am going to have to dig into the amavisd code and dump the policy bank before and after each check to see whats going on. This will take time.
I will try get to it ASAP as its holding back the next stable release aswell. -N
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
