Why run different instances of policyd-weight? Cause you may want use different scorings based on Access Policy Delegation.
At first you need make a copy of policyd-weight and modify it, since Robert didn’t implement a switch to specify a config file (yet):
# cp policyd-weight policyd-weight-instance2
# sed “s/\/policyd-weight.conf/\/policyd-weight-instance2.conf/” \
policyd-weight-instance2
Required changes to the config file:
# echo “$syslog_ident = \
“postfix/policyd-weight-INSTANCE2″;” >> \
/etc/policyd-weight-mx.conf
# echo “$SPATH = \
$LOCKPATH.’/polw-instance2.sock’;” >> \
/etc/policyd-weight-mx.conf
# echo “$PIDFILE = \
“/var/run/policyd-weight-instance2.pid”;” >> \
/etc/policyd-weight-mx.conf
# echo “$TCP_PORT = \
12526;” >> /etc/policyd-weight-mx.conf
The difference in my case is to not score “bogus_mx_score”, which may cause trouble when mails coming in from backup MX:
# echo “@bogus_mx_score = (0, 0 );” >> \
/etc/policyd-weight-mx.conf

The Running different policyd-weight instances by Cyconet Blog, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License. Terms and conditions beyond the scope of this license may be available at blog.waja.info.

0 Responses to “Running different policyd-weight instances”