> I am currently using the latest stable of policyd2 (2.0.7) and > amavisd-new-2.6.3 (20090422) > everything is setup to sql ( bayes filters + quarantine also ) > policyd rules are working just fine, inheritance of rules like > greylisting are applied but the amavis implementation is causing me a > headeche. > > if the default policy ( any, any ) has a amavis-rule attached to just > inherite everything, things are working good. Rules of the config are > read and doing what they are supposed to do. If I add a @testdomain.com > to another policy and make a new amavis rule set, things going way wrong. > The overwrite of the tag levels do not work and the bypass sets are a > bit strange, if it is set to YES, hits will be - if it set to no or > inherit amavis will scan but say: Passed SPAM instead of Blocked > SPAM ... so the mail is quarantined in the database but still delivered > and this is not what I want :) and I guess it is not the intention of > the maker either. > If I change settings on the default rule similar things are happening, > so spam wil not quarantined into the sql database and also the > spamtaglevels are not is no working if you overwrite them. still > configfile values are taken > since the behaviour is changing when changing settings in the database > it must be a problem with the amavis itself or the plugin that should > give amavis the right values :S > > suggestions where I could look also are welcome and a solution even more :) > Policyd's amavis module totally replaces the policy bank. The overwrite, inherit ... etc is all in the context of the Policyd configuration.
The rules can either be configured in amavisd or in Policyd. -N _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
