>
> I actually have two different questions. I hope it is OK to have them
> in one mail.
>
> 1) I installed postfix-policyd package (on Debian with apt-get install
> postfix-policyd). Then I realised this is not the newest package.
> Version 2.0 is called cluebringer instead (is that package name for
> Debian also --> apt-get install cluebringer ?) so I tried apt-get
> remove postfix-policyd but get exit with error 1 on that one. It is
> never removed. Instead I actually have to stop the daemon AGAIN
> because it automatically restarts after trying to remove it! I know
> you would maybe like more error messages from me on this, but maybe
> it's not important? Maybe I could just:
>
> Would it be safe for me to just do:
> #apt-get install cluebringer
> even though v. 1.8 is still there, not working?

This is more a packaging issue or distro issue, you'll need to take it
up with the relevant distribution support channel.


>
> 2) How does it work with the relationship between postfix main.cf
> <http://main.cf> and cbpolicyd.conf? If I already have specified a
> parameter in main.cf <http://main.cf> that I would like to keep but
> I'm afraid it will get in conflict with cbpolicyd.conf, who is
> overruling who then? Can I just comment out in policyd configuration
> the stuff I don't wish to use? Or will there be defaults still
> implemented?
>
> I want to use policyd because of one single feature that has proven to
> be nearly impossible to do in main.cf <http://main.cf>. That is:
> Reject outbound mail from users trying to send more than x mail/time
> unit. In all other cases I would like my main.cf <http://main.cf> to
> be master config. 

The Postfix main.cf file has nothing to do with the cbpolicyd.conf file,
these are two different daemons. Maybe check out on the Postfix page how
the policy delegation protocol works :)

-N

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users

Reply via email to