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)
I have only checked one setting. Under what circumstances is an Amavis
restart needed?
Policyd: cluebringer-2.0.6 with patched amavisd-policyd.pm
Amavis: vinilla amavisd-new-2.6.1
Regards,
David Koski
[email protected]
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
