Difference between revisions of "Unable to configure domain disclaimer if ldap url has more than one ldap server entries in ZCS v8.5 and v8.6"
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
<div class="col-md-12 ibox-content"> | <div class="col-md-12 ibox-content"> | ||
=Unable to configure domain disclaimer if "ldap_url" has more than one ldap server entries in ZCS v8.5 and v8.6= | =Unable to configure domain disclaimer if "ldap_url" has more than one ldap server entries in ZCS v8.5 and v8.6= | ||
+ | {{KB|{{ZC}}||||}} | ||
{{WIP}} | {{WIP}} | ||
Line 43: | Line 44: | ||
− | + | {| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10" | |
+ | |'''Submitted by''': Heera Singh Koranga | ||
+ | |} | ||
− | + | {{Article Footer||}} |
Latest revision as of 23:53, 20 August 2018
Contents
Unable to configure domain disclaimer if "ldap_url" has more than one ldap server entries in ZCS v8.5 and v8.6
Problem
Unable to configure domain disclaimer if more than one ldap server entries exist in the ldap_url. Altermime throwing below error while generating disclaimer files :
./libexec/zmaltermimeconfig -e DOMAIN.COM
Error connecting to LDAP server: ldap://ldap1.DOMAIN.COM:389 ldap://ldap2.DOMAIN.COM:389 at ./libexec/zmaltermimeconfig line 63, line 751.
Solution
See the following steps to fix this problem, and using these steps there is no need to restart any service.
Step 1
Check LDAP server entries in localconfig:-
zmlocalconfig ldap_url
Output:-
ldap_url = ldap://ldap1.DOMAIN.COM:389 ldap://ldap2.DOMAIN.COM:389
Step 2
Remove second LDAP server entry from ldap_url. There is no need to restart any service for this change.
zmlocalconfig -e ldap_url="ldap://ldap1.DOMAIN.COM:389"
Step 3
Now generate domain disclaimer files for altermime:-
./libexec/zmaltermimeconfig -e DOMAIN.COM
Step 4
After generating domain disclaimer files revert ldap_url entries:-
zmlocalconfig -e ldap_url="ldap://ldap1.DOMAIN.COM:389 ldap://ldap2.DOMAIN.COM:389"
Note :
There is a bug for this issue, which affecting v8.0.x, v8.5.x and v8.6. https://bugzilla.zimbra.com/show_bug.cgi?id=84003
This bug fixed on v8.7.0.
Submitted by: Heera Singh Koranga |