Bash Scripts for cbpolicyd: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{BC| | {{BC|Zeta Alliance}} <!-- Note, this will also add [[Category: Zeta Alliance]] to bottom of wiki page. --> | ||
__FORCETOC__ | __FORCETOC__ <!-- Will force a TOC regards of size of article. __NOTOC__ if no TOC is wanted. --> | ||
<div class="col-md-12 ibox-content"> | <div class="col-md-12 ibox-content"> | ||
=Bash Scripts for CBPolicyD= | =Bash Scripts for CBPolicyD= <!-- Normally will reflect page title. Is listed at very top of page. --> | ||
{{KB|{{ | {{KB|{{ZETA}}|{{ZCS 10.0}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}} <!-- Can only handle 3 ZCS versions. --> | ||
{{WIP}}==Introduction== | {{WIP}} <!-- For pages that are "work in progress". --> | ||
==Introduction== | |||
Automated cbpolicd installer for single-server. Tested on Zimbra 8.8.15 p7 CentOS7, Zimbra 9.0.0 p29 CentOS 7, Zimbra 9.0.0 patch 29 on Ubuntu 20, Zimbra 10 on Ubuntu 20. | Automated cbpolicd installer for single-server. Tested on Zimbra 8.8.15 p7 CentOS7, Zimbra 9.0.0 p29 CentOS 7, Zimbra 9.0.0 patch 29 on Ubuntu 20, Zimbra 10 on Ubuntu 20. | ||
| Line 24: | Line 26: | ||
[[Category:ZCS 9.0]] | [[Category:ZCS 9.0]] | ||
[[Category:ZCS 8.8]] | [[Category:ZCS 8.8]] | ||
[[Category: Zeta Alliance]] | |||
Latest revision as of 10:14, 18 January 2023
Bash Scripts for CBPolicyD
- This article is a Work in Progress, and may be unfinished or missing sections.
Introduction
Automated cbpolicd installer for single-server. Tested on Zimbra 8.8.15 p7 CentOS7, Zimbra 9.0.0 p29 CentOS 7, Zimbra 9.0.0 patch 29 on Ubuntu 20, Zimbra 10 on Ubuntu 20.
- Installs policyd on MariaDB or MySQL (shipped with Zimbra) and show commands on how to activate on Zimbra
- No webui is installed
You can download the script from here and run it as root:
https://raw.githubusercontent.com/Zimbra-Community/zimbra-tools/master/cbpolicyd.sh
You can use mysqldump to make backups of your policyd database. It is recommended you keep a copy of the cbpolicyd.sh up-to-date with your custom policies and rules so that you can easily re-install policyd on Zimbra upgrades or in disaster recovery situations. You can also install policyd on a separate MariaDB server that way you can have multiple Zimbra MTA nodes talk to the same policyd database.
