https://wiki.zimbra.com/api.php?action=feedcontributions&user=Ssatam&feedformat=atomZimbra :: Tech Center - User contributions [en]2024-03-28T17:07:29ZUser contributionsMediaWiki 1.39.0https://wiki.zimbra.com/index.php?title=Failed_to_start_slapd&diff=70223Failed to start slapd2023-12-20T11:59:57Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to fix the error "Failed to start slapd. Attempting debug start to determine error"=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}} <br />
<hr><br />
<br />
====Problem====<br />
Zimbra could not load anymore and slapd refuse to start.<br />
<br />
zmcontrol start<br />
Host ########.###<br />
Starting ldap...Done.<br />
Failed.<br />
Failed to start slapd. Attempting debug start to determine error.<br />
TLS: error:02001002:system library:fopen:No such file or directory bss_file.c:175<br />
TLS: error:2006D080:BIO routines:BIO_new_file:no such file bss_file.c:178<br />
main: TLS init def ctx failed: -1 <br />
<br />
Proxy service will also fail with the error below.<br />
zmproxyctl restart<br />
Stopping proxy...proxy is not running.<br />
Starting proxy...nginx: [emerg] BIO_new_file("/opt/zimbra/conf/dhparam.pem") failed (SSL: error:02001002:system library:fopen:<br />
No such file or directory:fopen('/opt/zimbra/conf/dhparam.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)failed. <br />
<br />
====Solution====<br />
Verify dhparam.pem file exist into /opt/zimbra/conf directory or not.<br />
<br />
Run following command to check:<br />
$ ls -lrth /opt/zimbra/conf/dhparam*<br />
<br />
Run the following command to create file if this file doesn't exist:<br />
$ openssl dhparam -out /opt/zimbra/conf/dhparam.pem 2048<br />
$ zmcontrol restart <br />
<br />
If the file exist,move this file and create new one:<br />
# su - zimbra<br />
$ cd /opt/zimbra/conf/<br />
$ mv dhparam.pem dhparam.pem.old<br />
$ openssl dhparam -out /opt/zimbra/conf/dhparam.pem 2048<br />
$ zmcontrol restart <br />
<br />
<br />
{{SubmittedBy|Gopal Singh Bhandari}}<br />
<br />
{{Article Footer|ZCS 8.8.15, ZCS 9.0|2020-07-28}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Failed_to_start_slapd&diff=70222Failed to start slapd2023-12-20T11:59:17Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to fix the error "Failed to start slapd. Attempting debug start to determine error"=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}} <br />
<hr><br />
<br />
====Problem====<br />
Zimbra could not load anymore and slapd refuse to start.<br />
<br />
zmcontrol start<br />
Host ########.###<br />
Starting ldap...Done.<br />
Failed.<br />
Failed to start slapd. Attempting debug start to determine error.<br />
TLS: error:02001002:system library:fopen:No such file or directory bss_file.c:175<br />
TLS: error:2006D080:BIO routines:BIO_new_file:no such file bss_file.c:178<br />
main: TLS init def ctx failed: -1 <br />
<br />
Proxy service will also fail with the error below.<br />
zmproxyctl restart<br />
Stopping proxy...proxy is not running.<br />
Starting proxy...nginx: [emerg] BIO_new_file("/opt/zimbra/conf/dhparam.pem") failed (SSL: error:02001002:system library:fopen:<br />
No such file or directory:fopen('/opt/zimbra/conf/dhparam.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)failed. <br />
<br />
====Solution====<br />
Verify dhparam.pem file exist into /opt/zimbra/conf directory or not.<br />
<br />
Run following command to check:<br />
$ ls -lrth /opt/zimbra/conf/dhparam*<br />
<br />
Run the following command to create file if this file doesn't exist:<br />
$ openssl dhparam -out /opt/zimbra/conf/dhparam.pem 2048<br />
$ zmcontrol restart <br />
<br />
If the file exist,move this file and create new one:<br />
# su - zimbra<br />
$ cd /opt/zimbra/conf/<br />
$ mv dhparam.pem dhparam.pem.old<br />
$ openssl dhparam -out /opt/zimbra/conf/dhparam.pem 2048<br />
$ zmcontrol restart <br />
<br />
<br />
{{SubmittedBy|Gopal Singh Bhandari}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_to_rewrite_email_addresses_before_sending_outbound_messages&diff=70221How to rewrite email addresses before sending outbound messages2023-12-20T11:55:59Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to rewrite email addresses before sending outbound messages= <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 9.0}}|}} <br />
<br />
<br />
====Requirement====<br />
How to mask the actual email address or domain of the sender or replace them with another address or domain?<br />
<br />
====Solution====<br />
`canonical_maps` is a configuration parameter used by the Postfix mail server to specify the location of the canonical mapping table. In Zimbra, zimbraMtaSenderCanonicalMaps is a configuration parameter that specifies the location of the sender canonical mapping table used by the Zimbra MTA. This table is used to rewrite or transform the sender email addresses according to the specified rules before sending outbound messages. The canonical mapping can be used to enforce a consistent email address format across the organization or to change the domain name of outgoing emails.<br />
<br />
For example, if you have a domain name "example.com" and want to replace all instances of "user@example.com" in the outgoing email headers with "user@example.net"<br />
<br />
Follow below steps to configure this:<br />
<br />
1) Create file postfix_sender_canonical and add the rules:<br />
$ cd /opt/zimbra/conf<br />
$ vim postfix_sender_canonical<br />
<br />
user@example.com user@example.net<br />
@example.com user@example.net<br />
<br />
Save the file.<br />
<br />
Each rule in the canonical mapping table contains two columns: the first column contains the original email address or pattern, and the second column contains the transformed email address or pattern. <br />
<br />
2) Postmap the file:<br />
$ postmap postfix_sender_canonical<br />
<br />
3) Run following command to configure this attribute:<br />
$ zmprov mcf zimbraMtaSenderCanonicalMaps 'lmdb:/opt/zimbra/conf/postfix_sender_canonical'<br />
$ zmmtactl restart<br />
<br />
Note: Before applying these steps to the production environment, it is recommended to first test them in a test environment to ensure that it works as expected.</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_to_check_accounts_in_a_specific_Mboxgroup_database&diff=70220How to check accounts in a specific Mboxgroup database2023-12-20T11:44:04Z<p>Ssatam: </p>
<hr />
<div>= How to check accounts in a specific mboxgroup database? = <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 9.0}}|{{ZCS 10.0}}|}} <br />
<hr> <br />
__FORCETOC__<br />
<br />
<br />
====Problem====<br />
<br />
How to check the accounts in a mboxgroup database?<br />
<br />
=====Solution=====<br />
<br />
Knowing how to identify the affected users when corruption occurs in a Mboxgroup database file can be incredibly helpful. It's important to understand that the identifiers used are unique to the mailstore, with "<code>group_id</code>" representing the Mboxgroup and id representing the "<code>userid</code>". However, "<code>account_id</code>" is a global variable, and its email address can be found in the "<code>comment</code>" field. Efficient troubleshooting and resolution of any issues with a Mboxgroup database can be achieved by comprehending these key identifiers.<br />
<br />
''Note: It's important to note that the number of displayed accounts may differ depending on the server size. This is because the round-robin method used to assign users to Mboxgroups is determined by zimbra_mailbox_groups, which is set to 100 by default.''<br />
<br />
*The following command checks the number of users present in the mboxgroup5 database (here mboxgroup5 is an exmaple).<br />
<pre><br />
$ mysql -e 'select id, comment, account_id, group_id from zimbra.mailbox where group_id=5'<br />
+----+-------------------------------------------+--------------------------------------+----------+<br />
| id | comment | account_id | group_id |<br />
+----+-------------------------------------------+--------------------------------------+----------+<br />
| 5 | account1@domain.com | 9ded4fa5-62fe-4ae4-ac14-7a8928386ea8 | 5 | <br />
+----+-------------------------------------------+--------------------------------------+----------+<br />
</pre><br />
<br />
*The account_id and comment information can also be double-checked using zmprov command:<br />
<br />
<pre><br />
$ zmprov gmi 9ded4fa5-62fe-4ae4-ac14-7a8928386ea8<br />
mailboxId: 5<br />
quotaUsed: 0<br />
<br />
$ zmprov gmi account1@domain.com<br />
mailboxId: 5<br />
quotaUsed: 0<br />
</pre><br />
<br />
{{SubmittedBy|Aman Shukla}}<br />
<br />
{{Article Footer|ZCS 8.8, ZCS 9.0, ZCS 10.0|2023-04-15}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Inaccessible_a_link_of_shared_documents_in_drive&diff=70219Inaccessible a link of shared documents in drive2023-12-20T11:21:50Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Document shared from zimbra drive via url is not accessible=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|||}} <br />
<br />
<br />
====Problem====<br />
When sharing documents as a link from Zimbra drive, generated URL become inaccessible, it's just hang or keep loading.<br />
<br />
====Solution====<br />
This problem occurs when <code>(zimbraPublicServiceHostname,zimbraPublicServiceProtocol,zimbraPublicServicePort)</code> attribute values are not configured. <br />
<br />
To fix this problem need to set parameters as shown below, these parameters can be set either on Domain or Global level.<br />
<br />
=====Global Level Changes=====<br />
<pre><br />
su - zimbra <br />
zmprov mcf zimbraPublicServiceHostname mail.example.com<br />
zmprov mcf zimbraPublicServiceProtocol https<br />
zmprov mcf zimbraPublicServicePort 443<br />
zmproxyctl restart<br />
</pre><br />
<br />
=====Domain Level Changes=====<br />
<pre><br />
su - zimbra <br />
zmprov md example.com zimbraPublicServiceHostname mail.example.com<br />
zmprov md example.com zimbraPublicServiceProtocol https<br />
zmprov md example.com zimbraPublicServicePort 443<br />
zmproxyctl restart<br />
</pre><br />
<br />
*Note:- Replace <code>example.com</code> and <code>mail.example.com</code> with the actual value according to the environment.<br />
<br />
<br />
<br />
{{SubmittedBy|Aditya Patidar}}<br />
<br />
{{Article Footer|ZCS 8.8,ZCS 9.0|2023-05-09}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Migrate_filter_rules_from_one_user_to_another_user&diff=70218Migrate filter rules from one user to another user2023-12-20T11:19:37Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to migrate filter rules from one user to another user?=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<hr><br />
<br />
====Problem====<br />
How to migrate filter rules from one user to another user? <br />
<br />
<br />
====Solution====<br />
<br />
These are the steps to export and import filter rules. <br />
<br />
'''1)''' Export exiting filter rules of a user and save into a file. <br />
zmprov -l ga UserA@DOMAIN.COM zimbraMailSieveScript > /tmp/filter_rules.txt <br />
<br />
<br />
'''2)''' Prepare the output file '''"/tmp/filter_rules.txt"'''. <br />
sed -i -e "1d" /tmp/filter_rules.txt <br />
sed -i -e 's/zimbraMailSieveScript: //g' /tmp/filter_rules.txt<br />
<br />
<br />
'''3)''' Check required folders' path for the filter rules. <br />
<br />
cat /tmp/filter_rules.txt | grep 'fileinto ' <br />
<br />
Example: <br />
<br />
zimbra@mail:~$ cat /tmp/filter_rules.txt | grep 'fileinto '<br />
fileinto "TestEmail/TEST2";<br />
fileinto "User5";<br />
fileinto "Admin";<br />
zimbra@mail:~$<br />
<br />
<br />
'''4)''' Import prepared filter rules on another user. <br />
zmprov ma UserB@DOMAIN.COM zimbraMailSieveScript "`cat /tmp/filter_rules.txt`" <br />
<br />
<br />
'''5)''' Create all required folders for the imported filter rules from the step 3. <br />
zmmailbox -z -m UserB@DOMAIN.COM cf -V message /<span style="color:lime">"FolderName"</span><br />
<br />
Example: <br />
<br />
zmmailbox -z -m UserB@DOMAIN.COM cf -V message /"User5" <br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer||}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_to_create_a_dynamic_distribution_list_that_contains_all_the_active_accounts_of_a_specific_domain&diff=70217How to create a dynamic distribution list that contains all the active accounts of a specific domain2023-12-20T11:16:44Z<p>Ssatam: </p>
<hr />
<div>= How to create a dynamic distribution list that contains all the active accounts of a specific domain? =<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 9.0}}|{{ZCS 10.0}}|}} <br />
<hr> <br />
__FORCETOC__<br />
<br />
==Purpose==<br />
Create a dynamic distribution list that contains all the active email addresses in a domain.<br />
<br />
==Resolution==<br />
Run the following command from the CLI:<br />
zmprov cddl all@example.com memberURL 'ldap:///??sub?(&(&(objectClass=zimbraAccount)(mail=*@example.com)(ZimbraAccountStatus=active))(!(objectClass=zimbraCalendarResource)))' zimbraIsACLGroup FALSE<br />
<br />
The ''''ZimbraAccountStatus=active'''' specifies that only active accounts are added. Similarly, more filters can be added as well.<br />
<br />
This can also be done from the admin console:<br />
* Go to '''Manage > Distribution Lists'''.<br />
* Click ''''New'''' from the gear icon<br />
* Add a dynamic distribution list name. Don't add members to the list.<br />
* Click "'''Next'''" to configure the dynamic DL<br />
* For the ''''Member URL'''' field, select ''''ldap:///??sub?(&(&(objectClass=zimbraAccount)(mail=*@example.com)(ZimbraAccountStatus=active))(!(objectClass=zimbraCalendarResource)))'''' to create a DL for all active accounts.<br />
<br />
{{SubmittedBy|Aman Shukla}}<br />
<br />
{{Article Footer|ZCS 8.8, ZCS 9.0, ZCS 10.0|2023-04-28}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Negative_greeting_error_while_sending_email&diff=70216Negative greeting error while sending email2023-12-20T11:15:44Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=MTA is not able to send emails when "localhost[127.0.0.1]" is missing from zimbraMtaMyNetworks=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}} <br />
<hr><br />
<br />
====Problem====<br />
Negative greeting 554 5.7.1 <localhost[127.0.0.1] error in zimbra.log while sending email.<br />
<br />
<pre><br />
May 31 03:28:16 mta2 postfix/smtp[2326054]: 02DEC202BDF0: to=<bob@example.com>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.18, delays=0.1/0.01/0/0.06, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=2321174-01 - Temporary MTA failure on relaying, From MTA() during fwd-connect (Negative greeting: 554 5.7.1 <localhost[127.0.0.1]>: Client host rejected: Access denied): id=2321174-01 (in reply to end of DATA command))<br />
</pre><br />
<br />
====Solution====<br />
Check the zimbraMtaMyNetworks output in all MTA servers:<br />
zmprov -l gs zimbra.example.com zimbraMtaMyNetworks <br />
<br />
Confirm localhost (127.0.0.0/8 [::1]/128) network added or not.<br />
Add localhost network into zimbraMtaMyNetworks.<br />
<br />
Example:<br />
zmprov ms `zmhostname` zimbraMtaMyNetworks '127.0.0.0/8 [::1]/128 10.0.1.34/32 10.0.2.35/32'<br />
zmcontrol restart<br />
<br />
{{SubmittedBy|Gopal Bhandari}}<br />
<br />
{{Article Footer|ZCS 8.8.15, ZCS 9.0|2023-12-20}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Negative_greeting_error_while_sending_email&diff=70215Negative greeting error while sending email2023-12-20T11:13:36Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=MTA is not able to send emails when "localhost[127.0.0.1]" is missing from zimbraMtaMyNetworks=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}} <br />
<hr><br />
<br />
====Problem====<br />
Negative greeting 554 5.7.1 <localhost[127.0.0.1] error in zimbra.log while sending email.<br />
<br />
<pre><br />
May 31 03:28:16 mta2 postfix/smtp[2326054]: 02DEC202BDF0: to=<bob@example.com>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.18, delays=0.1/0.01/0/0.06, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=2321174-01 - Temporary MTA failure on relaying, From MTA() during fwd-connect (Negative greeting: 554 5.7.1 <localhost[127.0.0.1]>: Client host rejected: Access denied): id=2321174-01 (in reply to end of DATA command))<br />
</pre><br />
<br />
====Solution====<br />
Check the zimbraMtaMyNetworks output in all MTA servers:<br />
zmprov -l gs zimbra.example.com zimbraMtaMyNetworks <br />
<br />
Confirm localhost (127.0.0.0/8 [::1]/128) network added or not.<br />
Add localhost network into zimbraMtaMyNetworks.<br />
<br />
Example:<br />
zmprov ms `zmhostname` zimbraMtaMyNetworks '127.0.0.0/8 [::1]/128 10.0.1.34/32 10.0.2.35/32'<br />
zmcontrol restart</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Installing_a_LetsEncrypt_SSL_Certificate&diff=70214Installing a LetsEncrypt SSL Certificate2023-12-20T11:11:26Z<p>Ssatam: </p>
<hr />
<div>{{BC|Community Sandbox}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Installing a Let's Encrypt SSL Certificate=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 10.0}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}}<br />
<hr><br />
<br />
= How to use Zimbra with Let's Encrypt certificates =<br />
<br />
This article is a step-by-step instruction on setting up a Zimbra with Let’s Encrypt certificates.<br />
<br />
If you are running a multi server installation of Zimbra it is recommended you set-up a dedicated VM for obtaining the Let’s Encrypt certificate and follow the steps under <code>Manual installation of Let’s Encrypt on Zimbra</code>.<br />
<br />
= Prerequisites =<br />
<br />
This guide assumes you are using Ubuntu 20 and you have set up a correct hostname and DNS, to check run the following as user <code>zimbra</code> and verify <code>zmhostname</code> is the same as <code>hostname --fqdn</code>:<br />
<br />
<pre>zimbra@le-test:~$ source ~/bin/zmshutil; zmsetvars<br />
zimbra@le-test:~$ zmhostname<br />
le-test.zimbra.tech<br />
zimbra@le-test:~$ hostname --fqdn<br />
le-test.zimbra.tech</pre><br />
Next you should have set up a CAA DNS record so that Let’s Encrypt can issue certificates for your domain, to check run the following and make sure <code>0 issue &quot;letsencrypt.org&quot;</code> is in the output of the command:<br />
<br />
<pre>zimbra@le-test:~$ sudo apt install -y net-tools dnsutils<br />
zimbra@le-test:~$ dig +short type257 $(hostname --d)<br />
0 issuewild &quot;letsencrypt.org&quot;<br />
0 issue &quot;letsencrypt.org&quot;</pre><br />
Next check if Zimbra listens on port 80, Let’s Encrypt needs to be able to run a temporary webserver on port 80, so it can not be used by Zimbra. This is not an issue as most browsers now try https first. The following command should not have any output:<br />
<br />
<pre>netstat -tulpn | grep &quot;:80 &quot;</pre><br />
In case your Zimbra is listening on port 80, you have to switch the proxy mode like this:<br />
<br />
<pre>sudo su zimbra -<br />
zmprov ms `zmhostname` zimbraReverseProxyMailMode https<br />
zmprov ms `zmhostname` zimbraMailMode https<br />
/opt/zimbra/bin/zmtlsctl https<br />
/opt/zimbra/libexec/zmproxyconfig -e -w -o -a 8080:80:8443:443 -x https -H `zmhostname`</pre><br />
If you are having trouble setting up Zimbra you can use our automated installer that will take care of Let’s Encrypt also: https://github.com/Zimbra/zinstaller<br />
<br />
Further reading:<br />
<br />
* https://wiki.zimbra.com/wiki/CLI_zmtlsctl_to_set_Web_Server_Mode<br />
* https://wiki.zimbra.com/wiki/Enabling_Zimbra_Proxy_and_memcached<br />
<br />
= Installing Certbot =<br />
<br />
Certbot in the Ubuntu repositories is too old and cannot be used for Zimbra. The newer version can be installed via snap or pip. Run below commands to install Cerbot and obtain a certificate:<br />
<br />
<pre>apt install -y python3 python3-venv libaugeas0<br />
python3 -m venv /opt/certbot/<br />
/opt/certbot/bin/pip install --upgrade pip<br />
/opt/certbot/bin/pip install certbot<br />
ln -s /opt/certbot/bin/certbot /usr/local/sbin/certbot<br />
/usr/local/sbin/certbot certonly -d $(hostname --fqdn) --standalone --preferred-chain &quot;ISRG Root X1&quot; --agree-tos --register-unsafely-without-email</pre><br />
Support for ECDSA TLS (elliptic curve cryptography ECC) certificates has been added to Zimbra <code>zmcertmgr</code> from Zimbra versions 10.0.6, Joule-8.8.15-Patch-45, Kepler-9.0.0-Patch-38. Let’s Encrypt Certbot defaults to ECDSA secp256r1 (P-256) since version 2.0.0. If you are running out-of-date versions of the software or have another reason why you are required to use RSA certificates append to to cerbot command the <code>--key-type rsa</code> switch after <code>--register-unsafely-without-email</code>.<br />
<br />
= Zimbra deployment =<br />
<br />
Create the following script that deploys the Let’s Encrypt certificate on Zimbra:<br />
<br />
<pre>cat &gt;&gt; /usr/local/sbin/letsencrypt-zimbra &lt;&lt; EOF<br />
#!/bin/bash<br />
/usr/local/sbin/certbot certonly -d $(hostname --fqdn) --standalone -n --preferred-chain &quot;ISRG Root X1&quot; --agree-tos --register-unsafely-without-email<br />
cp &quot;/etc/letsencrypt/live/$(hostname --fqdn)/privkey.pem&quot; /opt/zimbra/ssl/zimbra/commercial/commercial.key<br />
chown zimbra:zimbra /opt/zimbra/ssl/zimbra/commercial/commercial.key<br />
wget -O /tmp/ISRG-X1.pem https://letsencrypt.org/certs/isrgrootx1.pem.txt<br />
rm -f &quot;/etc/letsencrypt/live/$(hostname --fqdn)/chainZimbra.pem&quot;<br />
cp &quot;/etc/letsencrypt/live/$(hostname --fqdn)/chain.pem&quot; &quot;/etc/letsencrypt/live/$(hostname --fqdn)/chainZimbra.pem&quot;<br />
cat /tmp/ISRG-X1.pem &gt;&gt; &quot;/etc/letsencrypt/live/$(hostname --fqdn)/chainZimbra.pem&quot;<br />
chown zimbra:zimbra /etc/letsencrypt -R<br />
cd /tmp<br />
su zimbra -c '/opt/zimbra/bin/zmcertmgr deploycrt comm &quot;/etc/letsencrypt/live/$(hostname --fqdn)/cert.pem&quot; &quot;/etc/letsencrypt/live/$(hostname --fqdn)/chainZimbra.pem&quot;'<br />
rm -f &quot;/etc/letsencrypt/live/$(hostname --fqdn)/chainZimbra.pem&quot;<br />
EOF</pre><br />
Set the correct permission, set up a cron job and run the deployment:<br />
<br />
<pre>chmod +rx /usr/local/sbin/letsencrypt-zimbra<br />
ln -s /usr/local/sbin/letsencrypt-zimbra /etc/cron.daily/letsencrypt-zimbra<br />
/etc/cron.daily/letsencrypt-zimbra</pre><br />
Finally restart Zimbra to load the new certificate:<br />
<br />
<pre>sudo su zimbra -c '/opt/zimbra/bin/zmcontrol restart'</pre><br />
'''''The cron job will renew your certificate about 1 month prior to the expiration date, you need to manually restart Zimbra before the renewal date to load the new certificate.'''''<br />
<br />
= Manual installation of Let’s Encrypt on Zimbra =<br />
<br />
Make sure to request a certificate with the <code>--preferred-chain &quot;ISRG Root X1&quot;</code> option. In case you already have a certificate but you have not used the option, you have to do a force renewal with the <code>--force-renewal --preferred-chain &quot;ISRG Root X1&quot;</code> options.<br />
<br />
After you have received the certificate from Let’s Encrypt you can deploy it on Zimbra like this:<br />
<br />
As user root or sudo:<br />
<br />
<pre>cp /etc/letsencrypt/live/barrydegraaff.nl/privkey.pem /opt/zimbra/ssl/zimbra/commercial/commercial.key<br />
chown zimbra:zimbra /opt/zimbra/ssl/zimbra/commercial/commercial.key<br />
wget -O /tmp/ISRG-X1.pem https://letsencrypt.org/certs/isrgrootx1.pem.txt<br />
cat /tmp/ISRG-X1.pem &gt;&gt; /etc/letsencrypt/live/barrydegraaff.nl/chain.pem</pre><br />
As user zimbra or <code>sudo su zimbra -</code>:<br />
<br />
<pre>cd ~<br />
/opt/zimbra/bin/zmcertmgr verifycrt comm /opt/zimbra/ssl/zimbra/commercial/commercial.key /etc/letsencrypt/live/barrydegraaff.nl/cert.pem /etc/letsencrypt/live/barrydegraaff.nl/chain.pem<br />
/opt/zimbra/bin/zmcertmgr deploycrt comm /etc/letsencrypt/live/barrydegraaff.nl/cert.pem /etc/letsencrypt/live/barrydegraaff.nl/chain.pem</pre><br />
The output should be similar to:<br />
<br />
<pre>root@zimbra9:~# su zimbra -<br />
zimbra@zimbra9:/root$ /opt/zimbra/bin/zmcertmgr verifycrt comm /opt/zimbra/ssl/zimbra/commercial/commercial.key /etc/letsencrypt/live/barrydegraaff.nl/cert.pem /etc/letsencrypt/live/barrydegraaff.nl/chain.pem<br />
** Verifying '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' against '/opt/zimbra/ssl/zimbra/commercial/commercial.key'<br />
Certificate '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' and private key '/opt/zimbra/ssl/zimbra/commercial/commercial.key' match.<br />
** Verifying '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' against '/etc/letsencrypt/live/barrydegraaff.nl/chain.pem'<br />
Valid certificate chain: /etc/letsencrypt/live/barrydegraaff.nl/cert.pem: OK<br />
zimbra@zimbra9:/root$ cd ~<br />
zimbra@zimbra9:~$ /opt/zimbra/bin/zmcertmgr deploycrt comm /etc/letsencrypt/live/barrydegraaff.nl/cert.pem /etc/letsencrypt/live/barrydegraaff.nl/chain.pem<br />
** Verifying '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' against '/opt/zimbra/ssl/zimbra/commercial/commercial.key'<br />
Certificate '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' and private key '/opt/zimbra/ssl/zimbra/commercial/commercial.key' match.<br />
** Verifying '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' against '/etc/letsencrypt/live/barrydegraaff.nl/chain.pem'<br />
Valid certificate chain: /etc/letsencrypt/live/barrydegraaff.nl/cert.pem: OK<br />
** Copying '/etc/letsencrypt/live/barrydegraaff.nl/cert.pem' to '/opt/zimbra/ssl/zimbra/commercial/commercial.crt'<br />
** Copying '/etc/letsencrypt/live/barrydegraaff.nl/chain.pem' to '/opt/zimbra/ssl/zimbra/commercial/commercial_ca.crt'<br />
** Appending ca chain '/etc/letsencrypt/live/barrydegraaff.nl/chain.pem' to '/opt/zimbra/ssl/zimbra/commercial/commercial.crt'<br />
** Importing cert '/opt/zimbra/ssl/zimbra/commercial/commercial_ca.crt' as 'zcs-user-commercial_ca' into cacerts '/opt/zimbra/common/lib/jvm/java/lib/security/cacerts'<br />
** NOTE: restart mailboxd to use the imported certificate.<br />
** Saving config key 'zimbraSSLCertificate' via zmprov modifyServer zimbra9.barrydegraaff.nl...ok<br />
** Saving config key 'zimbraSSLPrivateKey' via zmprov modifyServer zimbra9.barrydegraaff.nl...ok<br />
** Installing imapd certificate '/opt/zimbra/conf/imapd.crt' and key '/opt/zimbra/conf/imapd.key'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.crt' to '/opt/zimbra/conf/imapd.crt'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.key' to '/opt/zimbra/conf/imapd.key'<br />
** Creating file '/opt/zimbra/ssl/zimbra/jetty.pkcs12'<br />
** Creating keystore '/opt/zimbra/conf/imapd.keystore'<br />
** Installing ldap certificate '/opt/zimbra/conf/slapd.crt' and key '/opt/zimbra/conf/slapd.key'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.crt' to '/opt/zimbra/conf/slapd.crt'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.key' to '/opt/zimbra/conf/slapd.key'<br />
** Creating file '/opt/zimbra/ssl/zimbra/jetty.pkcs12'<br />
** Creating keystore '/opt/zimbra/mailboxd/etc/keystore'<br />
** Installing mta certificate '/opt/zimbra/conf/smtpd.crt' and key '/opt/zimbra/conf/smtpd.key'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.crt' to '/opt/zimbra/conf/smtpd.crt'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.key' to '/opt/zimbra/conf/smtpd.key'<br />
** Installing proxy certificate '/opt/zimbra/conf/nginx.crt' and key '/opt/zimbra/conf/nginx.key'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.crt' to '/opt/zimbra/conf/nginx.crt'<br />
** Copying '/opt/zimbra/ssl/zimbra/commercial/commercial.key' to '/opt/zimbra/conf/nginx.key'<br />
** NOTE: restart services to use the new certificates.<br />
** Cleaning up 3 files from '/opt/zimbra/conf/ca'<br />
** Removing /opt/zimbra/conf/ca/ca.key<br />
** Removing /opt/zimbra/conf/ca/e50a23da.0<br />
** Removing /opt/zimbra/conf/ca/ca.pem<br />
** Copying CA to /opt/zimbra/conf/ca<br />
** Copying '/opt/zimbra/ssl/zimbra/ca/ca.key' to '/opt/zimbra/conf/ca/ca.key'<br />
** Copying '/opt/zimbra/ssl/zimbra/ca/ca.pem' to '/opt/zimbra/conf/ca/ca.pem'<br />
** Creating CA hash symlink 'e50a23da.0' -&gt; 'ca.pem'<br />
** Creating /opt/zimbra/conf/ca/commercial_ca_1.crt<br />
** Creating CA hash symlink '8d33f237.0' -&gt; 'commercial_ca_1.crt'<br />
** Creating /opt/zimbra/conf/ca/commercial_ca_2.crt<br />
** Creating CA hash symlink '4042bcee.0' -&gt; 'commercial_ca_2.crt'</pre><br />
Finally restart Zimbra as user zimbra or <code>sudo su zimbra -</code>:<br />
<br />
<pre>zmcontrol restart</pre><br />
= Using DANE =<br />
<br />
You have to use Certbot with the <code>--reuse-key</code> option, see https://blog.zimbra.com/2022/04/zimbra-skillz-enable-dane-verification-for-incoming-email-in-zimbra/<br />
<br />
= Using multiple https domains with SNI =<br />
<br />
Refer to: https://blog.zimbra.com/2022/06/zimbra-skillz-how-to-use-zimbra-with-multiple-https-domains-server-name-indication-sni/<br />
<br />
= Further reading =<br />
<br />
* https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry<br />
<br />
<br />
<br />
{{Article Footer|Zimbra Collaboration 10.0, 9.0, 8.8|22/09/2022}}<br />
<br />
[[Category:Certificates]]</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Disable_alias_login&diff=70213Disable alias login2023-12-20T11:06:17Z<p>Ssatam: </p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
<br />
=How to enable or disable login using alias account? = <br />
{{KB|{{ZC}}|{{ZCS 8.7}}|{{ZCS 8.8}}|{{ZCS 9.0}}||||}} <br />
<br />
====Problem====<br />
How to allow or disallow alias account to login to the webmail?<br />
====Solution====<br />
* Execute the below command on the respective mailbox server to check the current status first. It will show TRUE or FALSE.<br />
<pre> zmlocalconfig alias_login_enabled<br />
</pre><br />
<br />
* Execute the below command to disallow login to alias account. <br />
<pre> zmlocalconfig -e alias_login_enabled=false </pre><br />
<br />
* Execute the below command to allow login to alias account <br />
<pre> zmlocalconfig -e alias_login_enabled=true </pre><br />
<br />
* Once done with the above changes make sure to restart the mailbox services.<br />
<pre> zmmailboxdctl restart</pre><br />
* If alias login is disabled and still somebody tries to login using alias account the log entry will show like follows in /opt/zimbra/log/audit.log <br />
<pre> 2021-06-28 23:14:25,104 WARN [qtp1225197672-333://localhost:8080/service/soap/BatchRequest] [name=alias-user@example.com;oip=xx.xx.xx.xx;ua=zclient/8.8.15_GA_3991;soapId=c2df7e2;] <br />
security - cmd=Auth account=original-user@example.com; protocol=soap; error=authentication failed for [alias-user@example.com], alias login not enabled.;</pre><br />
<br />
<br />
{{SubmittedBy|Amol Mistry}}<br />
<br />
{{Article Footer|ZCS 8.8|2021-06-24}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_to_view_complete_message_body_parts_in_large_emails&diff=70212How to view complete message body parts in large emails2023-12-20T11:03:10Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to view complete message body parts in large emails?= <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 9.0}}||||}} <br />
<br />
<br />
<br />
====Problem====<br />
For large emails, some body part in the email is not displayed on screen.<br />
<br />
<br />
<br />
====Solution====<br />
In webmail, for large message(i.e. message size greater than 250k bytes) will only return the part that is displayed on the screen, one must click 'view entire message' to display the whole message. This 'view entire message' link will be displayed at the top of the email, like mentioned in the below example screenshot.<br />
<br />
<br />
[[File:Body.png]]<br />
<br />
<br />
{{SubmittedBy|Vivek Dhande}}<br />
<br />
{{Article Footer|ZCS 8.8|ZCS 9.0|2021-10-16}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_To_Check_Owner_Of_DL_Through_CLI&diff=70211How To Check Owner Of DL Through CLI2023-12-20T11:00:46Z<p>Ssatam: </p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Error: postscreen_cache: MDB_CURSOR_FULL: Internal error=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 9.0}}}}<br />
<hr><br />
<br />
<br />
<br />
====Overview====<br />
This article will show the method to find the owner of different DL through CLI commands<br />
====Solution====<br />
To find the owner of a DL below steps are needed to follow:<br />
=====Step 1=====<br />
* First step will give the zimbra id of the DL owner user<br />
$ zmprov gdl dl@domain.com |grep -w "zimbraACE:" |grep "ownDistList" |awk '{print $2}'<br />
f74f6b75-6c31-49e8-8aa1-08a391eb58b1<br />
<br />
=====Step 2===== <br />
* Now run below command to find the actual name of the owner from id<br />
$ zmprov -l ga f74f6b75-6c31-49e8-8aa1-08a391eb58b1 |grep -w name |awk '{print $3}'<br />
dlowner@domain.com<br />
<br />
{{SubmittedBy|Aman Shukla}}<br />
<br />
{{Article Footer|ZCS 8.8, ZCS 9.0|2020-09-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Purge_old_zmstats_data&diff=70210Purge old zmstats data2023-12-20T10:58:15Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to purge old zmstats data? =<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<hr><br />
<br />
====Problem====<br />
Stats data under '''"/opt/zimbra/zmstat"''' is taking large disk space. <br />
<br />
ZCS server does not purge the stats data automatically, and retention for zmstats is controlled by the localconfig key ''"zmstat_max_retention"'''. <br />
<br />
By default '''zmstat_max_retention''' is set to 0 (zero), and because of that '''"zmstat-cleanup"''' command is giving following warning. <br />
<br />
zimbra@mail:~$ /opt/zimbra/libexec/zmstat-cleanup<br />
WARNING: zmstat_max_retention is set to 0 or is undefined. No zmstat data has been pruned.<br />
zimbra@mail:~$ <br />
<br />
<br />
====Solution====<br />
<br />
These are the available options with the zmstat-cleanup. <br />
zimbra@mail:~$ /opt/zimbra/libexec/zmstat-cleanup -h<br />
Usage: /opt/zimbra/libexec/zmstat-cleanup [-k <keep count>] [-h] [-l] [-p]<br />
<br />
-h|--help Help/usage information<br />
-k|--keep Number of archived copies of zmstat data to retain.<br />
-l|--list Generate a listing of log dates archived.<br />
-p|--purge Purge ALL archived zmstats data.<br />
<br />
<br />
To keep zmstats data of a time period without changing the localconfig key, run:<br />
<br />
'''Syntax:'''<br />
/opt/zimbra/libexec/zmstat-cleanup --keep <span style="color:lime">"<number of days>"</span> <br />
<br />
<br />
'''Example:'''<br />
<br />
Keep zmstats data of 300 days. <br />
/opt/zimbra/libexec/zmstat-cleanup --keep 300 <br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer||}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_to_Disable_DNSSEC_functionality_from_DNSCACHE_service&diff=70176How to Disable DNSSEC functionality from DNSCACHE service2023-10-28T07:19:08Z<p>Ssatam: </p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to Disable DNSSEC functionality from DNSCACHE service=<br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 8.8}}|{{ZCS 9.0}}|{{ZCS 10.0}}}}<br />
<hr><br />
<br />
====Problem====<br />
<br />
Instances of name resolution failure may arise when the master DNS service lacks support for DNSSEC functionality.<br />
<br />
====Solution====<br />
<br />
To address this concern, the DNSSEC functionality within the MTA (Message Transfer Agent) server should be disabled, as it is enabled by default.<br />
<br />
Check the current status of the DNSSEC functionality by running the command:<br />
<br />
zmlocalconfig zimbra_enable_dnssec<br />
<br />
If the output shows that zimbra_enable_dnssec is set to "true", then DNSSEC is currently enabled.<br />
<br />
'''Disable DNSSEC:'''<br />
<br />
Change the value of zimbra_enable_dnssec to false using the following command:<br />
<br />
zmlocalconfig -e zimbra_enable_dnssec=false<br />
<br />
Restart Services:<br />
<br />
Restart both the zmconfigd and zmdnscache services to apply the changes:<br />
<br />
zmconfigdctl restart<br />
zmdnscachectl restart<br />
<br />
By following these steps, the DNSSEC functionality will be disabled on the MTA server, addressing the issue of name resolution failure linked to DNSSEC incompatibility with the master DNS service.<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8 ZCS 9.0 ZCS 10.0 |2023-08-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=***UNCHECKED***_gets_added_to_the_subject_of_encrypted_mail_using_PGP&diff=70175***UNCHECKED*** gets added to the subject of encrypted mail using PGP2023-10-28T07:09:26Z<p>Ssatam: </p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=***UNCHECKED*** gets added to the subject of encrypted mail using PGP=<br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 8.8}}|{{ZCS 9.0}}|{{ZCS 10.0}}}}<br />
<hr><br />
<br />
====Problem====<br />
<br />
Emails that utilize PGP encryption may encounter the insertion of the UNCHECKED keyword into the subject line due to Amavis behavior.<br />
<br />
====Solution====<br />
<br />
Recognizing this occurrence as a false positive, it is possible to prevent the inclusion of the UNCHECKED tag in the subject line for emails that are PGP-encrypted. <br />
<br />
This ensures accurate subject lines for encrypted communication.<br />
<br />
Here are the steps:<br />
<br />
Edit the following file,<br />
<br />
vi /opt/zimbra/common/lib/perl5/Amavis/Conf.pm<br />
<br />
Change the line:<br />
<br />
$undecipherable_subject_tag = '***UNCHECKED*** ';<br />
<br />
to:<br />
<br />
$undecipherable_subject_tag = '';<br />
<br />
Restart Amavis Service:<br />
<br />
As zimbra:<br />
<br />
zmamavisdctl restart<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8 ZCS 9.0 ZCS 10.0 |2023-08-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Zimbra_10_How_to_configure_Zimbra_legacy_Backup_for_domain_level&diff=70092Zimbra 10 How to configure Zimbra legacy Backup for domain level2023-09-13T08:45:39Z<p>Ssatam: /* Zimbra 10: How to configure Zimbra legacy Backup for domain level? */</p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to configure backup on domain level in zimbra-10 (Daffodil) onward=<br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 10.0}}}}<br />
<hr><br />
<br />
====Problem====<br />
Configuring Zimbra Legacy Backup for Domain-Level in Zimbra 10<br />
<br />
<br />
Zimbra 10 offers the capability to set up legacy backups at the domain level. This guide outlines the steps required to configure Zimbra legacy backups specifically for a domain, ensuring data security and recovery.<br />
<br />
====Solution====<br />
<br />
Note: This wiki is not supported for ZCS-8.8.15 and ZCS-9<br />
<br />
<br />
Access the Zimbra Admin Console: Begin by logging into the Zimbra Admin Console, which provides administrative access to various settings and configurations.<br />
<br />
<br />
Navigate to Global Backup Settings: Once logged in, proceed to the "Configure" section in the navigation menu, then select "Global Settings." <br />
<br />
Within this section, locate and click on the "Backup/Restore" option.<br />
<br />
<br />
[[File:Legacy_backup_3.jpg|1080px]]<br />
<br />
<br />
Select Users for Backup: In the Backup/Restore settings area, you will find an option labeled "Select users for backup." <br />
<br />
Click on this option to proceed to the backup user selection settings.<br />
<br />
<br />
[[File:Legacy_backup_4.png|1080px]]<br />
<br />
<br />
Enable Domain and COS Backup: To configure the backup settings for a specific domain, choose the "Enable backup for" option. <br />
<br />
From the available choices, select "Domain and COS" to ensure that the backup encompasses the domain and its Class of Service (COS).<br />
<br />
<br />
[[File:Legacy_backup_2.png|1080px]]<br />
<br />
<br />
Specify the Domain for Configuration: Specify the domain for which you intend to configure the backup. This ensures that the backup process is tailored to the selected domain. <br />
<br />
After entering the domain, remember to save the updated settings.<br />
<br />
<br />
[[File:Legacy_backup_5.png|1080px]]<br />
<br />
<br />
<br />
Verify the Zimbra Cronjob Entry: It is crucial to confirm the cronjob entry responsible for initiating the backup process. <br />
<br />
This entry triggers the backup action at specified intervals. Verify that the cronjob entry resembles the following pattern:<br />
<br />
<br />
# BACKUP BEGIN 0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a useBackupConfig -t /opt/zimbra/backup --zip --mail-report<br />
<br />
<br />
The above entry schedules the backup to occur at 1:00 AM every Saturday (6th day of the week) while utilizing the configured backup settings.<br />
<br />
<br />
By following these steps, Zimbra administrators can effectively configure legacy backups for a specific domain within the Zimbra 10 environment. <br />
<br />
This ensures the availability of comprehensive backup data, enabling efficient data recovery in case of any unforeseen data loss or system disruptions.<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 10.0 |2023-08-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=***UNCHECKED***_gets_added_to_the_subject_of_encrypted_mail_using_PGP&diff=70078***UNCHECKED*** gets added to the subject of encrypted mail using PGP2023-09-01T07:27:35Z<p>Ssatam: ***UNCHECKED*** gets added to the subject of encrypted mail using PGP</p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=***UNCHECKED*** gets added to the subject of encrypted mail using PGP=<br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 8.8}}|{{ZCS 9.0}}|{{ZCS 10.0}}}}<br />
<hr><br />
<br />
====Problem====<br />
<br />
Emails that utilize PGP encryption may encounter the insertion of the UNCHECKED keyword into the subject line due to Amavis behavior.<br />
<br />
<br />
====Solution====<br />
<br />
Recognizing this occurrence as a false positive, it is possible to prevent the inclusion of the UNCHECKED tag in the subject line for emails that are PGP-encrypted. <br />
<br />
<br />
This ensures accurate subject lines for encrypted communication.<br />
<br />
<br />
Here are the steps:<br />
<br />
<br />
Edit the following file,<br />
<br />
<br />
vi /opt/zimbra/common/lib/perl5/Amavis/Conf.pm<br />
<br />
<br />
change the line:<br />
<br />
<br />
$undecipherable_subject_tag = '***UNCHECKED*** ';<br />
<br />
to:<br />
<br />
$undecipherable_subject_tag = '';<br />
<br />
<br />
As zimbra:<br />
<br />
zmamavisdctl restart<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8 ZCS 9.0 ZCS 10.0 |2023-08-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How_to_Disable_DNSSEC_functionality_from_DNSCACHE_service&diff=70077How to Disable DNSSEC functionality from DNSCACHE service2023-09-01T07:22:08Z<p>Ssatam: How to Disable DNSSEC functionality from DNSCACHE service</p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to Disable DNSSEC functionality from DNSCACHE service=<br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 8.8}}|{{ZCS 9.0}}|{{ZCS 10.0}}}}<br />
<hr><br />
<br />
====Problem====<br />
<br />
Instances of name resolution failure may arise when the master DNS service lacks support for DNSSEC functionality.<br />
<br />
<br />
====Solution====<br />
<br />
To address this concern, the DNSSEC functionality within the MTA (Message Transfer Agent) server should be disabled, as it is enabled by default. <br />
<br />
<br />
Access the Command Line:<br />
<br />
<br />
Start by logging into the system's command line interface.<br />
<br />
<br />
Switch to the Zimbra User:<br />
<br />
<br />
Execute the command su - zimbra to switch to the Zimbra user account, which is necessary for Zimbra-related configurations.<br />
<br />
<br />
Verify Current DNSSEC Setting:<br />
<br />
<br />
Check the current status of the DNSSEC functionality by running the command:<br />
<br />
<br />
zmlocalconfig zimbra_enable_dnssec<br />
<br />
<br />
If the output shows that zimbra_enable_dnssec is set to "true", then DNSSEC is currently enabled.<br />
<br />
<br />
Disable DNSSEC:<br />
<br />
<br />
Change the value of zimbra_enable_dnssec to false using the following command:<br />
<br />
<br />
zmlocalconfig -e zimbra_enable_dnssec=false<br />
<br />
<br />
Restart Services:<br />
<br />
<br />
Restart both the zmconfigd and zmdnscache services to apply the changes:<br />
<br />
<br />
zmconfigdctl restart<br />
<br />
<br />
zmdnscachectl restart<br />
<br />
<br />
By following these steps, the DNSSEC functionality will be disabled on the MTA server, addressing the issue of name resolution failure linked to DNSSEC incompatibility with the master DNS service.<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8 ZCS 9.0 ZCS 10.0 |2023-08-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Zimbra_10_How_to_configure_Zimbra_legacy_Backup_for_domain_level&diff=70073Zimbra 10 How to configure Zimbra legacy Backup for domain level2023-08-29T15:37:49Z<p>Ssatam: Zimbra 10: How to configure Zimbra legacy Backup for domain level</p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Zimbra 10: How to configure Zimbra legacy Backup for domain level?=<br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 10.0}}}}<br />
<hr><br />
<br />
====Problem====<br />
Configuring Zimbra Legacy Backup for Domain-Level in Zimbra 10<br />
<br />
<br />
Zimbra 10 offers the capability to set up legacy backups at the domain level. This guide outlines the steps required to configure Zimbra legacy backups specifically for a domain, ensuring data security and recovery.<br />
<br />
====Solution====<br />
<br />
Access the Zimbra Admin Console: Begin by logging into the Zimbra Admin Console, which provides administrative access to various settings and configurations.<br />
<br />
<br />
Navigate to Global Backup Settings: Once logged in, proceed to the "Configure" section in the navigation menu, then select "Global Settings." <br />
<br />
Within this section, locate and click on the "Backup/Restore" option.<br />
<br />
<br />
[[File:Legacy_backup_3.jpg|1080px]]<br />
<br />
<br />
Select Users for Backup: In the Backup/Restore settings area, you will find an option labeled "Select users for backup." <br />
<br />
Click on this option to proceed to the backup user selection settings.<br />
<br />
<br />
[[File:Legacy_backup_4.png|1080px]]<br />
<br />
<br />
Enable Domain and COS Backup: To configure the backup settings for a specific domain, choose the "Enable backup for" option. <br />
<br />
From the available choices, select "Domain and COS" to ensure that the backup encompasses the domain and its Class of Service (COS).<br />
<br />
<br />
[[File:Legacy_backup_2.png|1080px]]<br />
<br />
<br />
Specify the Domain for Configuration: Specify the domain for which you intend to configure the backup. This ensures that the backup process is tailored to the selected domain. <br />
<br />
After entering the domain, remember to save the updated settings.<br />
<br />
<br />
[[File:Legacy_backup_5.png|1080px]]<br />
<br />
<br />
<br />
Verify the Zimbra Cronjob Entry: It is crucial to confirm the cronjob entry responsible for initiating the backup process. <br />
<br />
This entry triggers the backup action at specified intervals. Verify that the cronjob entry resembles the following pattern:<br />
<br />
<br />
# BACKUP BEGIN 0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a useBackupConfig -t /opt/zimbra/backup --zip --mail-report<br />
<br />
<br />
The above entry schedules the backup to occur at 1:00 AM every Saturday (6th day of the week) while utilizing the configured backup settings.<br />
<br />
<br />
By following these steps, Zimbra administrators can effectively configure legacy backups for a specific domain within the Zimbra 10 environment. <br />
<br />
This ensures the availability of comprehensive backup data, enabling efficient data recovery in case of any unforeseen data loss or system disruptions.<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 10.0 |2023-08-29}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:Legacy_backup_5.png&diff=70072File:Legacy backup 5.png2023-08-29T15:32:50Z<p>Ssatam: </p>
<hr />
<div></div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:Legacy_backup_4.png&diff=70071File:Legacy backup 4.png2023-08-29T15:30:23Z<p>Ssatam: </p>
<hr />
<div></div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:Legacy_backup_3.jpg&diff=70070File:Legacy backup 3.jpg2023-08-29T15:26:44Z<p>Ssatam: </p>
<hr />
<div></div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:Legacy_backup_2.png&diff=70069File:Legacy backup 2.png2023-08-29T15:22:49Z<p>Ssatam: </p>
<hr />
<div></div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:Legacy_backup_1.png&diff=70068File:Legacy backup 1.png2023-08-29T15:21:35Z<p>Ssatam: </p>
<hr />
<div></div>Ssatamhttps://wiki.zimbra.com/index.php?title=Steps_to_create_a_delegated_admin_to_manage_resource_accounts_only&diff=69831Steps to create a delegated admin to manage resource accounts only2023-06-13T14:23:52Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Create a delegated admin to manage resource accounts only=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<hr><br />
<br />
====Problem====<br />
Steps to create a delegated admin to manage(create/delete) resource accounts.<br />
<br />
<br />
====Solution====<br />
=====Step 1=====<br />
Create delegated admin account with required AdminConsole UI components. <br />
zmprov ca Resource-ADMIN@DOMAIN.COM PASSWORD zimbraIsDelegatedAdminAccount TRUE zimbraAdminConsoleUIComponents resourceListView <br />
<br />
=====Step 2===== <br />
Now assign following grants. <br />
zmprov grr domain DOMAIN.COM usr RESOURCE-ADMIN@DOMAIN.COM adminConsoleResourceRights <br />
zmprov grr domain DOMAIN.COM usr RESOURCE-ADMIN@DOMAIN.COM countCalendarResource <br />
<br />
<br />
'''Note:'''<br />
Replace '''Resource-ADMIN''' and '''DOMAIN.COM''' with the actual Admin user and '''DOMAIN''' name. <br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer||}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=How-to-restrict-ssl-login&diff=69830How-to-restrict-ssl-login2023-06-13T14:11:13Z<p>Ssatam: </p>
<hr />
<div>{{BC|Community Sandbox}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to restrict SASL login for a user on postfix level?=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|{{ZCS 8.7}}|}}<br />
<hr><br />
<br />
<h2>Problem:</h2><br />
How to restrict SASL login for a user on postfix level in Zimbra? Sometime a system administrator needs to block SASL authentication of a user due to various reasons like company policy where web-client is allowed only for some users,<br />
account was compromised and spammer is sending spam emails using SASL authentication etc. <br />
<br />
<h2>Solution:</h2><br />
<br />
Here are the steps to do so.<br />
<br />
1. Switch to Zimbra user and open '''smtpd_sender_restrictions.cf''' using vim editor.<br />
<br />
su - zimbra<br />
vim /opt/zimbra/conf/zmconfigd/smtpd_sender_restrictions.cf<br />
<br />
2. Add this line '''check_sasl_access lmdb:/opt/zimbra/conf/sasl_access''' between '''"permit_mynetworks and permit_sasl_authenticated".<br />
<br />
permit_mynetworks, reject_sender_login_mismatch<br />
check_sasl_access lmdb:/opt/zimbra/conf/sasl_access_block<br />
permit_sasl_authenticated<br />
<br />
3. Create '''sasl_access_block''' file and add a user which has to be restricted using sasl authentication.<br />
<br />
vim /opt/zimbra/conf/sasl_access_block<br />
user1@example.com REJECT Sorry, you are not allowed to use SMTP SASL authentication.<br />
<br />
'''Note:''' Other conditions can be also used like HOLD or DISCARD etc.<br />
<br />
4. Save this file and run '''postmap''' command.<br />
<br />
postmap /opt/zimbra/conf/sasl_access_block<br />
<br />
5. Reload postfix service.<br />
<br />
postfix reload <br />
<br />
<br />
The following logs entries in the zimbra.log show up and a message should be appeared if a restricted user tries to send an email using SASL authentication. <br />
<br />
'''Log lines from zimbra.log'''<br />
<br />
Oct 5 14:00:33 proxy postfix/smtps/smtpd[32649]: NOQUEUE: reject: RCPT from unknown[172.16.7.222]: 554 5.7.1 <user1@example.com>: <br />
SASL login name rejected: Sorry, you are not allowed to use SMTP SASL authentication.; from=<user1@example.com> to=<user2@example.com> proto=ESMTP helo=<PNQWB7S2PRKUMA>Rejected <br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Prabhat Kumar<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0, 8.8, 8.7,|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Zimbra_Two_Factor_Authentication_code(TOTP)_does_not_appear_to_expire&diff=69828Zimbra Two Factor Authentication code(TOTP) does not appear to expire2023-06-13T13:11:03Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Zimbra Two Factor Authentication code (TOTP) does not appear to expire= <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 9.0}}|}} <br />
<hr><br />
<br />
<br />
<br />
====Problem====<br />
The Two Factor Authentication code can still be used even after its expiration.<br />
<br />
====Solution====<br />
Modify the "zimbraTwoFactorTimeWindowOffset" attribute at the global level in Zimbra. This attribute determines the number of windows to check when validating a TOTP code (NOW-n through NOW+n), and its default value is set to 1 minute. <br />
<br />
# $ zmprov desc -a zimbraTwoFactorTimeWindowOffset<br />
zimbraTwoFactorTimeWindowOffset<br />
Determines the number of windows to check when trying to validate a<br />
TOTP code (NOW-n through NOW+n). This number should typically be<br />
small, but a minimum value of 1 is usually necessary to account for<br />
network latency and clock drift. See also:<br />
zimbraTwoFactorTimeWindowLength and<br />
https://tools.ietf.org/html/rfc6238#section-5.2<br />
type : integer<br />
value :<br />
callback :<br />
immutable : false<br />
cardinality : single<br />
requiredIn :<br />
optionalIn : globalConfig<br />
flags :<br />
defaults : 1<br />
min : 1<br />
max :<br />
id : 1830<br />
requiresRestart :<br />
since : 8.7.0,9.0.0<br />
deprecatedSince : <br />
<br />
However, due to network latency and clock drift, need to adjust this value. <br />
<br />
To check the current value of this attribute run the following command:<br />
$ zmprov -l gacf zimbraTwoFactorTimeWindowOffset<br />
<br />
Change The value:<br />
$ zmprov mcf zimbraTwoFactorTimeWindowOffset 1<br />
<br />
Once this adjustment is made, the TOTP code will expire after one minute, providing better security by ensuring that expired codes cannot be used for authentication. It is worth noting that this attribute should typically have a small value, but a minimum of 1 is needed to account for network latency and clock drift. More information about this attribute can be found in https://tools.ietf.org/html/rfc6238#section-5.2.<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Gopal Bhandari<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0, 8.8, |2023-06-13}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Current_Known_Issues&diff=69089Current Known Issues2022-06-29T14:17:34Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Current Known Issues on 8.8.15= <br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 8.8}}|}} <br />
<br />
==Current known issues with ZCS 8.8.15 patch 32==<br />
<br />
----<br />
====Fixed in the latest packages for patch 32====<br />
<br />
The following bugs have been fixed in the latest packages, but are included here in case someone is still on the old package. <br />
<br />
'''Summary of the issue:''' zmconfigd is failing for ldap-only nodes. <br />
<br />
'''Bug number:''' <s>ZBUG-2837</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' zmconfigd is failing for ldap-only nodes.<br />
<br />
'''Workaround:''' Apply the given workaround<br />
<br />
1. On the ldap server wget these two files for the respective versions in /tmp/:<br />
<br />
wget https://raw.githubusercontent.com/Zimbra/zm-core-utils/8.8.15.p32/src/libexec/zmconfigd<br />
wget https://raw.githubusercontent.com/Zimbra/zm-jython/8.8.15.p32/jylibs/commands.py<br />
<br />
2. Take a backup and replace the files in this location:<br />
<br />
/opt/zimbra/common/lib/jylibs/commands.py /opt/zimbra/libexec/zmconfigd<br />
<br />
3. Restart zmconfigd<br />
<br />
----<br />
<br />
'''Summary of the issue:''' SMTP authentication failure with 2FA application passcode<br />
<br />
'''Bug number:''' <s>ZBUG-2831</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' SMTP authentication failure with 2FA application passcode is configured in client like outlook, thunderbird etc. <br />
<br />
'''Workaround:''' The following workaround can be applied on the affected server.<br />
<br />
1. Open /opt/zimbra/jetty_base/etc/jetty.xml.in and add below statement on line no 41.<br />
<Set name="forwardedPortAsAuthority">false</Set><br />
2. Restart mailbox after this<br />
<br />
----<br />
<br />
'''Summary of the issue:''' All Zimlets are disabled from custom COS after redeploying the Zimlets<br />
<br />
'''Bug number:''' <s>ZBUG-2833</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' When zimlets are redeployed on the server , then zimlets are disabled on the customer COS.<br />
<br />
'''Workaround:''' Those zimlets can be enabled on the custom COS manually.<br />
<br />
----<br />
<br />
'''Summary of the issue:''' No INFO logs while redeploying the Zimlets on the server.<br />
<br />
'''Bug number:''' <s>ZBUG-2834</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' When a zimlet is deployed on the server, it shows the output but it doesn't show anything on the screen and zimlet gets deployed silently in backend.<br />
<br />
'''Workaround:''' N/A<br />
<br />
----<br />
<br />
'''Summary of the issue:''' /var/log/syslog filling after applying the patch-32 on ZCS-8.8.15 and this leads to the disk space filling up.<br />
<br />
'''Bug number:''' <s>ZBUG-2835</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' /var/log/syslog filling after applying the patch-32 on ZCS-8.8.15. This leads to the disk space filling up.<br />
<br />
'''Workaround:''' The following workaround can be applied on the affected server.<br />
<br />
1. Open /opt/zimbra/conf/log4j.properties.in and update line no 195 and change value to info from debug.<br />
<br />
2. Update line no 210 and remove SLOGGER from statement.<br />
<br />
3. Restart mailbox after this<br />
<br />
<br />
* While deploying zimlets, if the following error is encountered, refer to the patch installation section to install the zimbra-common-core-jar, zimbra-common-core-libs, zimbra-mbox-store-libs packages in a particular order and re-deploy the zimlets <br />
<br />
<pre>/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory<br />
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target<br />
at com.zimbra.cs.localconfig.LocalConfigCLI.main(LocalConfigCLI.java:353)<br />
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target<br />
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)<br />
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)<br />
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)<br />
... 1 more</pre><br />
<br />
==Other issues with ZCS 8.8.15 patch 32==<br />
<br />
* From Kepler-Patch-25 onwards, customers using SSO will need to update zimbraVirtualHostName attribute for the domains. Please refer to the instructions to update the attribute.<br />
<br />
<br />
* With OpenJDK 17, weaker Kerberos encryption types like 3DES and RC4 have now been disabled by default. This can cause SPNEGO auth to fail if described encryption types are being used. We recommend using stronger encryption types like AES256.<br />
<br />
To get SPNEGO auth working with weak encryption types, weak encryption can be enabled by setting the allow_weak_crypto property to true in the krb5.conf configuration file. Please follow below instructions: <br />
<br />
1. In /opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults] section, set allow_weak_crypto = true<br />
<br />
2. Restart mailboxd service:<br />
<br />
<pre>su - zimbra<br />
zmmailboxdctl restart</pre></div>Ssatamhttps://wiki.zimbra.com/index.php?title=Current_Known_Issues_ZCS9&diff=69088Current Known Issues ZCS92022-06-29T14:12:56Z<p>Ssatam: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Current Known Issues on ZCS 9.0= <br />
<hr><br />
{{KB|{{WIP}}|{{ZCS 9.0}}|}} <br />
<br />
==Current known issues with ZCS 9.0 patch 25==<br />
<br />
<br />
'''Summary of the issue:''' Using the Org Chart in ZWC may cause the webclient to freeze<br />
<br />
'''Bug number:''' ZBUG-2853<br />
<br />
'''Description:''' Performing actions such a clicking on a checkbox or minimizing a branch may cause the client to freeze.<br />
<br />
'''Workaround:''' NA<br />
<br />
----<br />
<br />
====Fixed in the latest packages for patch 25====<br />
<br />
The following bugs have been fixed in the latest packages, but are included here in case someone is still on the old package. <br />
<br />
'''Summary of the issue:''' zmconfigd is failing for ldap-only nodes. <br />
<br />
'''Bug number:''' <s>ZBUG-2837</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' zmconfigd is failing for ldap-only nodes.<br />
<br />
'''Workaround:''' Apply the given workaround<br />
<br />
1. On the ldap server wget these two files for the respective versions in /tmp/:<br />
<br />
wget https://raw.githubusercontent.com/Zimbra/zm-core-utils/9.0.0.p25/src/libexec/zmconfigd<br />
wget https://raw.githubusercontent.com/Zimbra/zm-jython/9.0.0.p25/jylibs/commands.py<br />
<br />
2. Take a backup and replace the files in this location:<br />
<br />
/opt/zimbra/common/lib/jylibs/commands.py /opt/zimbra/libexec/zmconfigd<br />
<br />
3. Restart zmconfigd<br />
<br />
----<br />
<br />
'''Summary of the issue:''' SMTP authentication failure with 2FA application passcode<br />
<br />
'''Bug number:''' <s>ZBUG-2831</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' SMTP authentication failure with 2FA application passcode is configured in client like outlook, thunderbird etc. <br />
<br />
'''Workaround:''' The following workaround can be applied on the affected server.<br />
<br />
1. Open /opt/zimbra/jetty_base/etc/jetty.xml.in and add below statement on line no 41.<br />
<Set name="forwardedPortAsAuthority">false</Set><br />
2. Restart mailbox after this<br />
<br />
----<br />
<br />
'''Summary of the issue:''' All Zimlets are disabled from custom COS after redeploying the Zimlets<br />
<br />
'''Bug number:''' <s>ZZBUG-2833</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' When zimlets are redeployed on the server , then zimlets are disabled on the customer COS.<br />
<br />
'''Workaround:''' Those zimlets can be enabled on the custom COS manually.<br />
<br />
----<br />
<br />
'''Summary of the issue:''' No INFO logs while redeploying the Zimlets on the server.<br />
<br />
'''Bug number:''' <s>ZBUG-2834</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' When a zimlet is deployed on the server, it shows the output but it doesn't show anything on the screen and zimlet gets deployed silently in backend.<br />
<br />
'''Workaround:''' N/A<br />
<br />
<br />
'''Summary of the issue:''' /var/log/syslog filling after applying the patch-25 on ZCS-9 and this leads to the disk space filling up.<br />
<br />
'''Bug number:''' <s>ZBUG-2835</s> Fixed in the latest patch packages.<br />
<br />
'''Description:''' /var/log/syslog filling after applying the patch 8.8.15 patch 32. This leads to the disk space filling up.<br />
<br />
'''Workaround:''' The following workaround can be applied on the affected server.<br />
<br />
1. Open /opt/zimbra/conf/log4j.properties.in and update line no 195 and change value to info from debug.<br />
<br />
2. Update line no 210 and remove SLOGGER from statement.<br />
<br />
3. Restart mailbox after this<br />
<br />
<br />
==Other issues with ZCS 9.0 patch 25==<br />
<br />
* While deploying zimlets, if the following error is encountered, refer to the patch installation section to install the zimbra-common-core-jar, zimbra-common-core-libs, zimbra-mbox-store-libs packages in a particular order and re-deploy the zimlets <br />
<br />
<pre>/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory<br />
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target<br />
at com.zimbra.cs.localconfig.LocalConfigCLI.main(LocalConfigCLI.java:353)<br />
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target<br />
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)<br />
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)<br />
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)<br />
... 1 more</pre><br />
<br />
<br />
* From Kepler-Patch-25 onwards, customers using SSO will need to update zimbraVirtualHostName attribute for the domains. Please refer to the instructions to update the attribute.<br />
<br />
<br />
* With OpenJDK 17, weaker Kerberos encryption types like 3DES and RC4 have now been disabled by default. This can cause SPNEGO auth to fail if described encryption types are being used. We recommend using stronger encryption types like AES256.<br />
<br />
To get SPNEGO auth working with weak encryption types, weak encryption can be enabled by setting the allow_weak_crypto property to true in the krb5.conf configuration file. Please follow below instructions: <br />
<br />
1. In /opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults] section, set allow_weak_crypto = true<br />
<br />
2. Restart mailboxd service:<br />
<br />
<pre>su - zimbra<br />
zmmailboxdctl restart</pre></div>Ssatamhttps://wiki.zimbra.com/index.php?title=Zimbra_NG_Modules/First_Steps_with_the_Zimbra_NG_Modules&diff=67577Zimbra NG Modules/First Steps with the Zimbra NG Modules2020-09-01T17:18:58Z<p>Ssatam: </p>
<hr />
<div><div class="col-md-12"><br></div><br />
<div class="col-md-12"><br></div><br />
<ol class="breadcrumb"><br />
<li>[[Main Page|Zimbra Wiki]]</li><br />
<li>[[Zimbra_NG_Modules]]</li><br />
<li class="active">First Steps with the Zimbra NG Modules</li><br />
</ol><br />
__NOTOC__<br />
<div class="col-md-12"><br /></div><br />
<div class="col-md-9"><br />
<h2 class="title-header" style="padding-bottom: 9px; border-bottom: 4px solid #0087c3;">First Steps with the Zimbra NG Modules</h2><br />
<div class="col-md-12"><br />
<div class="ibox-content"><br />
<div class="post animated fadeInLeft animation-delay-8" style="padding-top:5px"><br />
<div class="panel panel-default"><br />
<div class="panel-body"><br />
<div class="row"><br />
This guides contains all information needed in order to switch to the new Zimbra Network NG modules from their legacy counterparts after upgrading to Zimbra 8.8.<br />
<br />
''It's strongly suggested to take a look at the specific introductory page of each module before switching, to learn and understand the differences between each NG module and its Legacy counterpart:''<br />
<br />
<ul><br />
<li>[[Zimbra_NG_Modules/Zimbra_NG_Backup|'''Zimbra NG Backup''']]: Features a cutting-edge, real-time engine that backs up every single item and event on your Zimbra server with split-second precision. Avoids data loss by using atomic and ever-consistent algorithms, while still saving disk space thanks to an intelligent de-duplication and compression system.</li><br />
<li>[[Zimbra_NG_Modules/Zimbra_NG_Admin|'''Zimbra NG Admin''']]: Global Admin can grant Delegated Admin rights to users on your server using a simplified administrator user interface. With minimal effort, you can grant user management tasks, such as setting quotas, user limits and modifying COS variables for your domain(s).</li><br />
<li>[[Zimbra_NG_Modules/Zimbra_NG_HSM|'''Zimbra NG HSM''']]: Manage multiple volumes and HSM policies through the Zimbra Collaboration NG HSM Module. With an integrated user interface into your Zimbra Administration Console, the HSM Module gives you the tools to organize and manage your storage effectively.</li><br />
<li>[[Zimbra_NG_Modules/Zimbra_NG_Mobile|'''Zimbra NG Mobile''']]: With the advance integration, now your users can sync their primary and shared folders to their mobile devices while administrators have an advanced interface to manage policies and devices.<br />
</li><br />
</ul><br />
<br />
<!-- * [[An_Introduction_to_Backup_NG | An introduction to Backup NG]] --><br />
<!-- * [[An_Introduction_to_Mobile_NG | An introduction to Mobile NG]] --><br />
<!-- * [[An_Introduction_to_HSM_NG | An introduction to HSM NG]] --><br />
<!-- * [[An_Introduction_to_Admin_NG | An introduction to Admin NG]] --><br />
-----<br />
<br />
=Switching to Backup NG=<br />
Switching to the new Backup NG is a simple process that will initialize the new backup system on a dedicated path. Until the initialization is completed, the old backup engine will be active. Old backup files will not be removed and the old backup and restore tools are still available via the usual CLI commands.<br />
<br />
==Backup Path Limitations==<br />
In order to hold Backup NG data, a storage must comply to the following:<br />
<br />
* The storage must have a mountpoint on the system.<br />
* The "zimbra" user must of course have r/w permission on the path.<br />
* The data must be stored on a case-sensitive filesystem.<br />
<br />
Other than this, there are no hard limitations.<br />
<br />
==Backup NG Initialization==<br />
Before initializing the Backup NG module, make sure you have enough space on the storage you wish to store the backup in. The average size of the backup is 50-70% of the nominal total quota of all mailboxes.<br />
<br />
To initialize the Backup NG module:<br />
<br />
*Access the Zimbra Administration Console.<br />
*Enter the "Network Modules NG" section on the left menu.<br />
*Enter the "Backup" section.<br />
*Set the "Backup Path" to whatever directory you wish to store your backup into.<br />
*Click on the "Initialize" button<br />
<br />
== Usage Guide ==<br />
A complete user guide for the Backup NG Module is available in the [https://zimbra.github.io/adminguide/latest/index.html#backup-ng-guide ''"Backup NG (NG)"'' section of the Administrator's Guide] for your Zimbra version.<br />
-----<br />
<br />
=Switching to Mobile NG=<br />
Switching to the new Mobile NG is a simple process that will activate the new mobile handlers, deactivate the old ones and switch the synchronization control over to Mobile NG from the legacy Zimbra Mobile. Until the initialization is completed, the old mobile engine will be active.<br />
<br />
'''NOTE: Mobile NG is not currently compatible with S/MIME. For those who need this feature, please use the legacy mobile sync service at this time. '''<br />
<br />
==What happens after the switch==<br />
After switching to Mobile NG, all existing syncstates will be invalidated, and all connected devices will automatically re-synchronize all of their data through the new engine.<br />
<br />
'''WARNING: Since the switch will force all connected devices to re-synchonise all of their data, make sure to alert your users beforehand to make sure that they have wifi coverage or enough traffic on their mobile data plans.'''<br />
<br />
'''Furthermore, the switch might lead to an abrupt increase in the number of connections to the server, and consequently its load, due to the resynchronisation of all devices.'''<br />
<br />
The switch is completely transparent to end users, and no user interaction should be prompted or required, but being the Exchange ActiveSync protocol mostly client-driven different behaviours might be experienced, such as:<br />
<br />
* Device not synchronising until user's action (e.g. opening the email client).<br />
* Device requiring a restart.<br />
* Device not synchronising until the user re-enter its username and password in the account's settings.<br />
<br />
''Albeit sporadic, such behaviours and the load impact on the system should be taken into account when planning to switch to Mobile NG.''<br />
<br />
==Mobile NG Initialization==<br />
To initialize the Mobile NG module:<br />
# Enter the "Network Modules NG" section on the left menu.<br />
# Enter the "General" section -> By default, “Mobile” module will be in Stopped state. <br />
# Click on "Start" button infront of Mobile module. <br />
# Error message will be shown and admin is asked to set zimbraNetworkMobileNGEnabled attribute to TRUE from CLI.<br />
# Set zimbraNetworkMobileNGEnabled attribute to TRUE on the server using below command:<pre>zmprov ms <server> zimbraNetworkMobileNGEnabled TRUE</pre><br />
# Then, start NG Mobile service using Admin Console UI by visiting "Network Modules NG" -> “General” -> click on Start button in front of Mobile module.<br />
<br />
<br />
== Usage Guide ==<br />
A complete user guide for the Mobile NG Module is available [https://zimbra.github.io/adminguide/latest/index.html#mobile-ng-guide in the ''"Mobile NG"'' section of the Zimbra Administrator's Guide] for your Zimbra version.<br />
-----<br />
<br />
=Switching to HSM NG=<br />
The HSM NG module will become active as soon as the upgrade to Zimbra 8.8 is completed, and does not require any interaction.<br />
<br />
Any old HSM policy, volume and volume configuration will be maintained.<br />
<br />
== Usage Guide ==<br />
A complete user guide for the HSM NG Module is available in the [https://zimbra.github.io/adminguide/latest/index.html#hsm-ng-guide ''"HSM NG"'' section of the Zimbra Administrator's Guide] for your Zimbra version.<br />
-----<br />
<br />
=Switching to Admin NG=<br />
Switching to the new Admin NG module is a simple process that will migrate any relevant ACL information to the module’s own configuration manager, clearing existing ACLs and ACEs from the system.<br />
<br />
'''Admin NG is significantly different than the old Delegated Administration engine. Please carefully read the product's documentation thoroughly and only migrate to Admin NG if its feature set meets your needs.'''<br />
<br />
==Admin Migration is a ONE WAY ONLY process==<br />
'''Switching to Admin NG will remove all existing ACLs and ACEs from the server. This new module is extremely different from its legacy counterpart, so after the migration will not be able to recreate the very same admin roles and settings'''<br />
<br />
'''''This is a one way only process.'''''<br />
<br />
'''Once Admin NG is initialized it's not possible to go back to the old engine, so if you have customized or complex ACLs/ACEs carefully consider whether or not to switch.'''<br />
<br />
==Admin NG Initialization==<br />
===Initialize Admin NG on Zimbra 8.7.6 to 8.8.4===<br />
* Access the Zimbra Administration Console.<br />
* Enter the "Network Modules NG" section on the left menu.<br />
* Enter the "Admin" section.<br />
* Click on the "Migrate" button.<br />
<br />
===Enable and initialize Admin NG on Zimbra 8.8.5+===<br />
Admin NG is disabled by default in Zimbra 8.8.5+ and its GUI is not available out-of-the-box, so it's necessary to enable the module beforehand running<br />
<br />
<pre>zmprov mcf zimbraNetworkAdminNGEnabled TRUE</pre><br />
<br />
as the "zimbra" user.<br />
<br />
After enabling the Admin NG module, it can be initialized following this steps:<br />
* Perform a mailbox restart, i.e <pre> zmmailboxdctl restart </pre><br />
* Access the Zimbra Administration Console.<br />
* Enter the "Network Modules NG" section on the left menu.<br />
* Enter the "Admin" section.<br />
* Click on the "Migrate" button.<br />
<br />
== Usage Guide ==<br />
A complete user guide for the Admin NG Module is available in the [https://zimbra.github.io/adminguide/latest/index.html#admin-ng-guide ''"Admin NG"'' section of the Zimbra Administrator's Guide] for your Zimbra version.<br />
<br />
</div><br />
</div><br />
<div class="col-md-9"><br />
<div class="panel-footer"><br />
<p><i class="fa fa-clock-o"></i> Aug 30, 2017 - [https://www.zimbra.com/email-server-software/ Know more »]</p><br />
</div><br />
</div><br />
</div><br />
</div><br />
</div><br />
</div><br />
</div><br />
<div class="col-md-3"><br /></div><br />
<div class="col-md-3"><br />
<div class="panel panel-zimbrared-light-border"> <br />
<div class="panel-heading"> <br />
<h3 class="panel-title"><i class="fa fa-gear pull-left"></i> Zimbra NG Modules</h3> <br />
</div><br />
<div class="panel-body"><br />
{{ZNG}}<br />
</div><br />
</div><br />
</div><br />
<div class="col-md-3"><br />
<div class="panel panel-primary-light-border"> <br />
<div class="panel-heading"> <br />
<h3 class="panel-title"><i class="fa fa-info-circle pull-left"></i> Zimbra NG Modules Resources</h3> <br />
</div><br />
<div class="panel-body"><br />
{{ZNGL}}<br />
</div><br />
</div><br />
</div><br />
<div class="clearfix"></div><br />
<div class="col-md-12"><br></div><br />
{{FH}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Block_user_to_send_email_locally_or_externally&diff=67250Block user to send email locally or externally2020-05-23T08:21:56Z<p>Ssatam: /* Block user to send email locally or externally */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Block user to send email locally or externally=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|||}} <br />
<br />
<br />
====Problem====<br />
How to block users to send email locally or externally.<br />
<br />
<br />
====Solution====<br />
<br />
=====ZCS 8.8.x and Later=====<br />
<br />
'''Step 1:'''<br />
<br />
Open file '''''/opt/zimbra/conf/zmconfigd/smtpd_sender_restrictions.cf''''' and add the below line at the top.<br />
<br />
%%contains VAR:zimbraMtaSmtpdSenderRestrictions check_sender_access lmdb:/opt/zimbra/common/conf/restricted_senders%%<br />
<br />
Then execute: <br />
<br />
zmprov ms `zmhostname` +zimbraMtaSmtpdSenderRestrictions "check_sender_access lmdb:/opt/zimbra/common/conf/restricted_senders"<br />
<br />
'''Step 2:'''<br />
<br />
Open file '''''/opt/zimbra/conf/zmconfigd.cf''''' and add below lines before "RESTART mta".<br />
<br />
POSTCONF smtpd_restriction_classes local_only<br />
POSTCONF local_only FILE postfix_check_recipient_access.cf<br />
<br />
'''Note:''' We can find like below<br />
<br />
<pre>SECTION mta DEPENDS amavis<br />
-----------<br />
-----------<br />
-----------<br />
RESTART mta</pre><br />
<br />
'''Step 3:'''<br />
<br />
Create a file '''''/opt/zimbra/conf/postfix_check_recipient_access.cf''''' and add the following line.<br />
<br />
check_recipient_access lmdb:/opt/zimbra/common/conf/local_domains, reject<br />
<br />
'''Step 4:'''<br />
<br />
Create a file '''''/opt/zimbra/common/conf/restricted_senders''''' and enter the list of users that you want to block. Follow this syntax:<br />
<br />
user@yourdomain.com local_only<br />
<br />
'''Step 5:'''<br />
<br />
Create an empty file '''''/opt/zimbra/common/conf/local_domains''''', here we list all the domains where restricted users allowed to send mails. But we will keep this blank file as we don't want to send emails inside or outside from this id. <br />Following is the command :<br />
<br />
touch /opt/zimbra/common/conf/local_domains<br />
<br />
'''Note:''' When we keep this file empty restricted sender can not send self email as well.<br />
<br />
'''i.e.:''' Allow User/Domain (user@domain.com OK/domain.com OK)<br />
<br />
'''Step 6:'''<br />
<br />
Set ownership permissions for created files<br />
<br />
chown zimbra:zimbra /opt/zimbra/conf/postfix_check_recipient_access.cf<br />
chmod 644 /opt/zimbra/conf/postfix_check_recipient_access.cf<br />
<br />
chown :zimbra /opt/zimbra/common/conf/restricted_senders<br />
chmod 775 /opt/zimbra/common/conf/restricted_senders<br />
<br />
chown :zimbra /opt/zimbra/postfix/conf/local_domains<br />
chmod 775 /opt/zimbra/postfix/conf/local_domains<br />
<br />
'''Step 7:'''<br />
<br />
Run the below commands as Zimbra user.<br />
<br />
postmap /opt/zimbra/common/conf/restricted_senders<br />
postmap /opt/zimbra/common/conf/local_domains<br />
zmmtactl stop<br />
zmmtactl start<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Navdeep Mathur<br />
|}<br />
<br />
{{Article Footer||}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Steps_to_update_LDAP_URL_and_Bind_Password_on_Domain_configuration_for_Autoprovisioning&diff=67249Steps to update LDAP URL and Bind Password on Domain configuration for Autoprovisioning2020-05-23T07:48:51Z<p>Ssatam: /* Update LDAP URL and Bind Password on Domain configuration for Auto-Provisioning */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Update LDAP URL and Bind Password on Domain configuration for Auto-Provisioning= <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<br />
<br />
<br />
====Problem====<br />
Auto-provisioning not working and mailbox.log shows following entries. <br />
<br />
2016-07-05 08:05:04,409 WARN [AutoProvision] [] autoprov - Unable to auto provision accounts for domain DOMAIN.COM <br />
com.zimbra.cs.ldap.LdapException: LDAP error: - unable to get connection: An error occurred while attempting to connect to server 192.168.0.134:3268: <br />
java.io.IOException: Unable to establish a connection to server 192.168.0.134:3268 within the configured timeout of 30000 milliseconds.<br />
ExceptionId:AutoProvision:1467723904380:2e38d9864676d9a6<br />
Code:ldap.LDAP_ERROR<br />
at com.zimbra.cs.ldap.LdapException.LDAP_ERROR(LdapException.java:88)<br />
at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToLdapException(UBIDLdapException.java:72)<br />
at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToExternalLdapException(UBIDLdapException.java:82) <br />
.......<br />
.......<br />
2016-07-05 17:22:11,582 WARN [AutoProvision] [] autoprov - Unable to auto provision accounts for domain DOMAIN.COM<br />
com.zimbra.cs.ldap.LdapException: LDAP error: - unable to get connection: 80090308: LdapErr: DSID-0C0903CF, comment: AcceptSecurityContext error, data 52e, v2580<br />
ExceptionId:AutoProvision:1467757331570:2e38d9864676d9a6<br />
Code:ldap.LDAP_ERROR<br />
at com.zimbra.cs.ldap.LdapException.LDAP_ERROR(LdapException.java:88)<br />
at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToLdapException(UBIDLdapException.java:72<br />
<br />
<br />
====Solution====<br />
With the help of following steps we can update auto-provision LDAP URL and Bind password. <br />
<br />
<br />
'''1).''' Command to check currently configured value:- <br />
zmprov gd DOMAIN.COM zimbraAutoProvLdapURL zimbraAutoProvLdapAdminBindPassword <br />
<br />
<br />
'''2).''' Commands to update attribute's value:- <br />
zmprov md DOMAIN.COM zimbraAutoProvLdapURL "ldap://AD-SERVER-IP:PORT" <br />
zmprov md DOMAIN.COM zimbraAutoProvLdapAdminBindPassword "ENTER-BIND-PASSWORD-HERE" <br />
zmprov fc -a all<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6, 8.5, 8.0.x, 7.x|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=ERROR:_service.AUTH_EXPIRED_error&diff=67248ERROR: service.AUTH EXPIRED error2020-05-23T07:47:34Z<p>Ssatam: /* ERROR: service.AUTH_EXPIRED error */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ERROR: service.AUTH_EXPIRED error=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<br />
<br />
====Problem====<br />
ERROR: service.AUTH_EXPIRED error when running the given command on server :<br />
zmprov ga user@domain zimbraMailHost<br />
ERROR: service.AUTH_EXPIRED (auth credentials have expired)<br />
<br />
<br />
====Solution====<br />
=====Step 1=====<br />
Check if the zimbraAuthTokenLifetime is not set too low value which might have caused the auth token to expire. Default is 2days :<br />
<br />
zmprov -l ga user@domain | grep -i zimbraAuthTokenLifetime<br />
<br />
=====Step 2=====<br />
It can also happen that the mailbox where the command is run from is not set to correct time in the server's timezone. If it's the case, set the correct time on server and rerun the command, as an example:<br />
<pre>[zimbra@zmstore ~]$ date<br />
Mon Jun 20 20:23:48 IST 2016<br />
[zimbra@zmstore ~]$ exit<br />
[root@zmstore ~]# date -s 'Tue Jun 21 08:25:30'<br />
Tue Jun 21 08:25:30 IST 2016<br />
[root@zmstore ~]# date<br />
[root@zmstore ~]# zmprov ga user@domain zimbraMailHost<br />
# name user@domain<br />
zimbraMailHost: mstore.domain</pre><br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Aarti Shah <br />
|}<br />
<br />
{{Article Footer||}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Steps_to_Increase_Maximum_Contact_Limit_for_a_User&diff=67247Steps to Increase Maximum Contact Limit for a User2020-05-23T07:45:01Z<p>Ssatam: /* Increase Maximum Contact Limit for a User */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Increase Maximum Contact Limit for a User= <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<br />
<br />
<br />
====Problem====<br />
Zimbra Desktop shows contact limit exceeded error. <br />
<br />
Following exception occurs while max contact limit exceeded. <br />
com.zimbra.cs.mailbox.MailServiceException: exceeded limit of 10000 contacts<br />
ExceptionId:sync-mbox-USERNAME@DOMAIN.COM:1467815759742:769v284f3dd4013e<br />
Code:mail.TOO_MANY_CONTACTS Arglimit, NUM, "10000")<br />
at com.zimbra.cs.mailbox.MailServiceException.TOO_MANY_CONTACTS(MailServiceException.java:303)<br />
at com.zimbra.cs.mailbox.Mailbox.updateContactCount(Mailbox.java:1083)<br />
at com.zimbra.cs.mailbox.Contact.create(Contact.java:620)<br />
at com.zimbra.cs.mailbox.Mailbox.createContact(Mailbox.java:6323)<br />
at com.zimbra.cs.mailbox.InitialSync.syncContact(InitialSync.java:973)<br />
at com.zimbra.cs.mailbox.InitialSync.syncContacts(InitialSync.java:999)<br />
at com.zimbra.cs.mailbox.DeltaSync.syncItems(DeltaSync.java:267)<br />
at com.zimbra.cs.mailbox.DeltaSync.deltaSync(DeltaSync.java:187)<br />
at com.zimbra.cs.mailbox.DeltaSync.sync(DeltaSync.java:124)<br />
at com.zimbra.cs.mailbox.DeltaSync.sync(DeltaSync.java:89)<br />
at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync.java:192)<br />
at com.zimbra.cs.mailbox.ZcsMailbox.sync(ZcsMailbox.java:124)<br />
at com.zimbra.cs.mailbox.ZcsMailbox.syncOnTimer(ZcsMailbox.java:105)<br />
at com.zimbra.cs.mailbox.SyncMailbox$1.run(SyncMailbox.java:279)<br />
at java.util.TimerThread.mainLoop(Unknown Source)<br />
at java.util.TimerThread.run(Unknown Source)<br />
<br />
<br />
====Solution====<br />
By default all user accounts allowed to store 10000 contacts. <br />
<br />
This setting controlled by the attribute ''''zimbraContactMaxNumEntries'''', and with the following steps we can check and update currently configured value.<br />
<br />
'''1).''' Command to check :- <br />
zmprov ga USERNAME@DOMAIN.COM zimbraContactMaxNumEntries <br />
<br />
'''2).''' Command to update:-<br />
zmprov ma USERNAME@DOMAIN.COM zimbraContactMaxNumEntries 20000 <br />
<br />
<br />
'''Note:''' Replace '''USERNAME@DOMAIN.COM''' with the actual user name according to your environment. <br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6, 8.5, 8.0.x, 7.x|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Step_to_rebuild_crontab_file_of_zimbra_user&diff=67246Step to rebuild crontab file of zimbra user2020-05-23T07:43:22Z<p>Ssatam: /* Step to rebuild crontab file of zimbra user */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
==Step to rebuild crontab file of zimbra user== <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}}<br />
<br />
==Problem==<br />
* Default crontab of zimbra user removed accidentally. <br />
* System admin removed some entries from the crontab file.<br />
<br />
<br />
==Solution==<br />
<br />
Steps to restore or rebuild crontab entries for the zimbra user on different ZCS environments.<br />
<br />
===(A) Steps for single-server setup: ===<br />
<br />
First we have to take backup of current crontab file, then we will use following commands to rebuild crontab for zimbra user.<br />
<br />
==== On ZCS v8.6: ==== <br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.ldap >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.store >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.logger >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
==== On ZCS v8.7.x and Above: ==== <br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.ldap >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.store >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.logger >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D"<br />
<br />
===(B) Steps for multi-server setup: ===<br />
<br />
Here we have mentioned the commands according to the role of ZCS server.<br />
<br />
==== On ZCS v8.6: ==== <br />
===== LDAP Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.ldap >> /tmp/cron.zimbra <br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== Mailbox Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.store >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
/etc/init.d/crond restart<br />
<br />
===== MTA+Proxy Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
<br />
<br />
==== On ZCS v8.7.x and Above: ==== <br />
===== LDAP Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.ldap >> /tmp/cron.zimbra <br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== Mailbox Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.store >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== MTA+Proxy Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
<br />
<br />
<br />
'''Note :''' We have to restart Cron service after installing new crontab file.<br />
<br />
'''Commands to restart Cron service on different OS versions.'''<br />
<br />
Ubuntu 12.04/14.04/16.04<br />
service cron restart<br />
<br />
RHEL/CentOS 7.x<br />
systemctl restart crond<br />
<br />
RHEL/CentOS 6.x<br />
service crond restart<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Step_to_rebuild_crontab_file_of_zimbra_user&diff=67245Step to rebuild crontab file of zimbra user2020-05-23T07:42:56Z<p>Ssatam: /* On ZCS v8.7.x: */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
==Step to rebuild crontab file of zimbra user== <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
{{WIP}}<br />
<br />
<br />
<br />
==Problem==<br />
* Default crontab of zimbra user removed accidentally. <br />
* System admin removed some entries from the crontab file.<br />
<br />
<br />
==Solution==<br />
<br />
Steps to restore or rebuild crontab entries for the zimbra user on different ZCS environments.<br />
<br />
===(A) Steps for single-server setup: ===<br />
<br />
First we have to take backup of current crontab file, then we will use following commands to rebuild crontab for zimbra user.<br />
<br />
==== On ZCS v8.6: ==== <br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.ldap >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.store >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.logger >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
==== On ZCS v8.7.x and Above: ==== <br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.ldap >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.store >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.logger >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D"<br />
<br />
===(B) Steps for multi-server setup: ===<br />
<br />
Here we have mentioned the commands according to the role of ZCS server.<br />
<br />
==== On ZCS v8.6: ==== <br />
===== LDAP Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.ldap >> /tmp/cron.zimbra <br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== Mailbox Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.store >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
/etc/init.d/crond restart<br />
<br />
===== MTA+Proxy Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
<br />
<br />
==== On ZCS v8.7.x and Above: ==== <br />
===== LDAP Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.ldap >> /tmp/cron.zimbra <br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== Mailbox Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.store >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== MTA+Proxy Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
<br />
<br />
<br />
'''Note :''' We have to restart Cron service after installing new crontab file.<br />
<br />
'''Commands to restart Cron service on different OS versions.'''<br />
<br />
Ubuntu 12.04/14.04/16.04<br />
service cron restart<br />
<br />
RHEL/CentOS 7.x<br />
systemctl restart crond<br />
<br />
RHEL/CentOS 6.x<br />
service crond restart<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Step_to_rebuild_crontab_file_of_zimbra_user&diff=67244Step to rebuild crontab file of zimbra user2020-05-23T07:42:32Z<p>Ssatam: /* (A) Steps for single-server setup: */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
==Step to rebuild crontab file of zimbra user== <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
{{WIP}}<br />
<br />
<br />
<br />
==Problem==<br />
* Default crontab of zimbra user removed accidentally. <br />
* System admin removed some entries from the crontab file.<br />
<br />
<br />
==Solution==<br />
<br />
Steps to restore or rebuild crontab entries for the zimbra user on different ZCS environments.<br />
<br />
===(A) Steps for single-server setup: ===<br />
<br />
First we have to take backup of current crontab file, then we will use following commands to rebuild crontab for zimbra user.<br />
<br />
==== On ZCS v8.6: ==== <br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.ldap >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.store >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.logger >> /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
==== On ZCS v8.7.x and Above: ==== <br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.ldap >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.store >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.logger >> /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D"<br />
<br />
===(B) Steps for multi-server setup: ===<br />
<br />
Here we have mentioned the commands according to the role of ZCS server.<br />
<br />
==== On ZCS v8.6: ==== <br />
===== LDAP Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.ldap >> /tmp/cron.zimbra <br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== Mailbox Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.store >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
/etc/init.d/crond restart<br />
<br />
===== MTA+Proxy Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/zimbramon/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/zimbramon/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
<br />
<br />
==== On ZCS v8.7.x: ==== <br />
===== LDAP Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.ldap >> /tmp/cron.zimbra <br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== Mailbox Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.store >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
su - zimbra -c "zmschedulebackup -D" <br />
<br />
===== MTA+Proxy Server: =====<br />
cp -pvr /var/spool/cron/zimbra /tmp/zimbra.cron.BAK <br />
cat /opt/zimbra/conf/crontabs/crontab > /tmp/cron.zimbra<br />
cat /opt/zimbra/conf/crontabs/crontab.mta >> /tmp/cron.zimbra<br />
echo "# ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART" >> /tmp/cron.zimbra <br />
crontab -u zimbra /tmp/cron.zimbra <br />
<br />
<br />
<br />
'''Note :''' We have to restart Cron service after installing new crontab file.<br />
<br />
'''Commands to restart Cron service on different OS versions.'''<br />
<br />
Ubuntu 12.04/14.04/16.04<br />
service cron restart<br />
<br />
RHEL/CentOS 7.x<br />
systemctl restart crond<br />
<br />
RHEL/CentOS 6.x<br />
service crond restart<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Steps_to_export_a_folder_from_command_line_where_folder_name_contains_white_spaces&diff=67243Steps to export a folder from command line where folder name contains white spaces2020-05-23T07:38:21Z<p>Ssatam: /* How to export a folder from command line when folder name contains white spaces */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=How to export a folder from command line when folder name contains white spaces= <br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0.x}}|{{ZCS 7.x}}|}}<br />
<br />
<br />
<br />
====Problem====<br />
Folder export fails when folder name has white spaces and generates "no such item" error as below - <br />
zmmailbox -z -m USERNAME@DOMAIN.COM gru '//Communications Officer Recruitment?fmt=zip' > /tmp/test.zip <br />
ERROR: service.FAILURE (system failure: GET from https://MAIL.DOMAIN.COM/home/USERNAME@DOMAIN.COM//Communications%20Officer%20Recruitment?fmt=zip failed, status=404. no such item) <br />
<br />
<br />
====Solution====<br />
Use the given commands to export a folder which has white spaces in it's name - <br />
<br />
zmmailbox -z -m USERNAME@DOMAIN.COM gru '//?fmt=tgz&query=in:"Communications Officer Recruitment"' > /tmp/test1.zip <br />
OR <br />
zmmailbox -z -m USERNAME@DOMAIN.COM gru '//?fmt=tgz&query=under:"Communications Officer Recruitment"' > /tmp/test2.zip <br />
<br />
'''Note:- ''' <br><br />
<br />
* If the query is [ in: ] , then only selected folder will export. <br><br />
<br />
* If the query is [ under: ] , then selected folder and sub-folders will export.<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6, 8.5, 8.0.x, 7.x|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Sender_address_triggers_FILTER_smtp-amavis&diff=67242Sender address triggers FILTER smtp-amavis2020-05-23T07:35:48Z<p>Ssatam: /* What does "Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026" mean? */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=What does "Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026" mean?=<br />
{{KB|{{ZC}}|{{ZCS 8.8}}||||}} <br />
<br />
<br />
====Problem====<br />
<br />
What does "Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026" mean? Is it harmless?<br />
<br />
<br />
====Solution====<br />
<br />
The message 'Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026' is completely harmless and expected.<br />
<br />
A typical log line containing this message looks like :<br />
<br />
NOQUEUE: filter: RCPT from external.domain.com[x.x.x.x]: <user@domain.com>: Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026; from=<user@domain.com> to=<user@example.com> proto=ESMTP helo=<[x.x.x.x]><br />
<br />
A breakdown of the log line :<br />
<br />
(Note that this line is logged even before the complete message has been transmitted.)<br />
<br />
NOQUEUE:</code> Postfix hasn't assigned a queue-id to this message as of yet. <br />
<br />
RCPT from external.domain.com:</code> The recipient domain's IP. Note the 'RCPT' -> This log line comes up immediately after RCPT, and before DATA.<br />
<br />
Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026:</code> This email will be filtered through amavis. By default all sender addresses will be triggered.<br />
<br />
proto=ESMTP:</code> ESMTP will be used<br />
<br />
helo=<[x.x.x.x]>:</code> The "helo" was sent from the specified IP.<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Shashank Shekhar Tewari<br />
|}<br />
<br />
{{Article Footer|ZCS 8.8, 8.7, 8.6|2017-08-23}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Errors_in_incremental_backups&diff=67241Errors in incremental backups2020-05-23T07:30:55Z<p>Ssatam: /* Errors in incremental backups */</p>
<hr />
<div>=Errors in incremental backups=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.7}}||||}} <br />
<br />
<br />
<br />
====Problem====<br />
<br />
When automatic incremental backup is executed on the server, following message is displayed in /opt/zimbra/log/mailbox.log file : <br />
<br />
<pre><br />
Found gap in redo log sequence; missing 1414 through 1446; To avoid future restore problems, discard all existing backups and take a full backup of all accounts; If this error occurred during restore, try the --ignoreRedoErrors option<br />
com.zimbra.cs.backup.BackupServiceException: Found gap in redo log sequence; missing 1414 through 1446; To avoid future restore problems, discard all existing backups and take a full backup of all accounts; If this error occurred during restore, try the --ignoreRedoErrors option <br />
ExceptionId:qtp662845511-542373:https://127.0.0.1:7071/service/admin/soap/BackupRequest:1463637618095:568e4f96fbb74864 <br />
Code:backup.REDOLOG_OUT_OF_SEQUENCE <br />
at com.zimbra.cs.backup.BackupServiceException.REDOLOG_OUT_OF_SEQUENCE(BackupServiceException.java:91) <br />
at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq(Utils.java:302)<br />
at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.backupRedoLogs(FileBackupTarget.java:1360)<br />
at com.zimbra.cs.backup.BackupSet.startIncrementalBackup(BackupSet.java:817)<br />
at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.startIncrementalBackup(FileBackupTarget.java:1067)<br />
at com.zimbra.cs.backup.BackupManager.backupIncremental(BackupManager.java:336)<br />
at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:153)<br />
at com.zimbra.cs.service.NetworkDocumentHandler.handle(NetworkDocumentHandler.java:23)<br />
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:569)<br />
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:432)<br />
</pre><br />
<br />
====Solution====<br />
<br />
* During a backup if the above error is seen, the recommendation is to move the old backups out - the directories in /opt/zimbra/backup/sessions/* .<br />
<br />
* It's advised to keep them somewhere at a different location to be on the safer side and then proceed to do a full backup.<br />
<br />
* Another possibe cause is the /tmp or /opt/zimbra/redolog/ filling up. Ensure that there is enough disk space available.<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Aarti Shah<br />
|}<br />
<br />
{{Article Footer|ZCS 8.7|2020-04-13}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Steps_to_create_a_delegated_admin_to_manage_only_Out_Of_Office_on_accounts&diff=67240Steps to create a delegated admin to manage only Out Of Office on accounts2020-05-23T07:27:55Z<p>Ssatam: /* Create a delegated admin to manage only OutOfOffice on accounts */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=Create a delegated admin to manage only OutOfOffice on accounts=<br />
<hr><br />
{{KB|{{ZC}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} <br />
<br />
<br />
====Problem====<br />
What are the steps to create a delegated admin to manage only Out-Of-Office on accounts? <br />
<br />
====Solution====<br />
<br />
=====Step 1=====<br />
Create delegated admin account with required AdminConsole UI component. <br />
zmprov ca Ooo-ADMIN@DOMAIN.COM <PASSWORD> zimbraIsDelegatedAdminAccount TRUE zimbraAdminConsoleUIComponents accountListView <br />
<br />
<br />
=====Step 2=====<br />
Now assign following grants. <br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM set.account.zimbraPrefOutOfOfficeReplyEnabled<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM set.account.zimbraPrefOutOfOfficeReply<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -adminConsoleAccountsAliasesTabRights<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -deleteAccount<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM set.account.zimbraPrefOutOfOfficeCacheDuration<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -changeAccountPassword<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM countAccount<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -setAccountPassword<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -setAdminConsoleAccountsInfoTab<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -renameAccount<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM adminConsoleSavedSearchRights<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -createAccount<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -adminConsoleAccountsForwardingTabRights<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -adminConsoleAccountsContactTabRights<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM adminConsoleAccountRights<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -set.account.zimbraMailCanonicalAddress<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -set.account.givenName<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -getAccountMembership<br />
zmprov grr domain DOMAIN.COM usr Ooo-ADMIN@DOMAIN.COM -adminConsoleAccountsThemesTabRights<br />
<br />
<br />
<br />
'''Note:''' <br />
Replace '''Ooo-ADMIN''' and '''DOMAIN.COM''' with the actual Admin user and '''DOMAIN''' name.<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Heera Singh Koranga<br />
|}<br />
<br />
{{Article Footer||}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=One_drive_integration_end_user_guide&diff=67211One drive integration end user guide2020-05-08T18:04:00Z<p>Ssatam: /* Re-enable the OpenDrive Zimlet (troubleshooting) */</p>
<hr />
<div>{{BC|Certified}}<br />
=OneDrive integration end user guide= <br />
<hr><br />
{{KB|{{ZC}}||{{ZCS 9.0}}|||}}<br />
__FORCETOC__<br />
<br />
This integration offers you the opportunity to connect your Microsoft OneDrive account to Zimbra so that you may save and share files from your OneDrive.<br />
<br />
Note: End user must login their respective Microsoft account to access their OneDrive space.<br />
<br />
<br />
====Activate the One Drive Zimlet====<br />
<br />
* Click on the "Settings" button.<br />
<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on the "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "OneDrive Integration".<br />
<br />
<br />
[[File:OneDrive_23.png|1080px]]<br />
<br />
<br />
* Click on the "Activate" button to activate OneDrive.<br />
<br />
<br />
[[File:OneDrive_24.png|1080px]]<br />
<br />
<br />
* Sign In to your "OneDrive" account.<br />
<br />
<br />
[[File:OneDrive_25.png|1080px]]<br />
<br />
<br />
* Click the "Allow" button to authorize access to your OneDrive account from Zimbra.<br />
<br />
<br />
[[File:OneDrive_26.png|800px]]<br />
<br />
<br />
* After a few seconds, the "Activate" button will be relabeled as "Deactivate", indicating you have activated the Zimlet. Click on the "Save" button.<br />
<br />
<br />
[[File:OneDrive_27.png|1080px]]<br />
<br />
<br />
====Save An Attachment to your OneDrive====<br />
<br />
* Hover over the attachment you would like to save and click the "download icon".<br />
<br />
<br />
[[File:OneDrive_22.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the list of download locations.<br />
<br />
<br />
[[File:OneDrive_21.png|1080px]]<br />
<br />
<br />
<br />
* Select a folder and click on the "Open" button to save the attachment to your OneDrive.<br />
<br />
<br />
[[File:OneDrive_20.png|1080px]]<br />
<br />
<br />
<br />
* A message will display indicating that you successfully saved your attachment to OneDrive.<br />
<br />
<br />
[[File:OneDrive_19.png|1080px]]<br />
<br />
<br />
====Attaching a file from OneDrive====<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_18.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to attach option to add the files as attachments in your email message.<br />
<br />
<br />
[[File:OneDrive_17.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to attach by selecting the checkbox in the upper right corner of each document; then click "Open".<br />
<br />
<br />
[[File:OneDrive_16.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_15.png|1080px]]<br />
<br />
<br />
====Link to a file on OneDrive====<br />
<br />
<br />
This option is recommended for larger files which could get rejected by email servers.<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_14.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to link option to add links of your OneDrive files into your email message.<br />
<br />
<br />
[[File:OneDrive_13.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to link by selecting the checkbox next to each document; then click "Choose".<br />
<br />
<br />
[[File:OneDrive_12.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_11.png|1080px]]<br />
<br />
====How to send large files via OneDrive====<br />
<br />
<br />
* Click the "Attachments" icon and select Attach from my Computer.<br />
<br />
<br />
[[File:OneDrive_10.png|1080px]]<br />
<br />
<br />
* Select the file you want to attach and click "Open".<br />
<br />
<br />
[[File:OneDrive_9.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the presented options.<br />
<br />
<br />
[[File:OneDrive_8.png|1080px]]<br />
<br />
<br />
* Click "Open" in the OneDrive window to save your file to be shared from OneDrive.<br />
<br />
<br />
[[File:OneDrive_7.png|1080px]]<br />
<br />
<br />
* The "Inserting Link" window will appear while the file is being saved to your OneDrive. Once completed, the link will appear in your email message<br />
<br />
<br />
[[File:OneDrive_6.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button as normal.<br />
<br />
<br />
[[File:OneDrive_5.png|1080px]]<br />
<br />
<br />
====Re-enable the OneDrive Zimlet (troubleshooting)====<br />
<br />
If you cannot see the OneDrive settings, you may need to re-enable your Zimlet.<br />
<br />
* Click on the "Settings" button.<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "Add-ons (Zimlets)" and ensure the checkbox for com_zimbra_x-onedrive is selected.<br />
<br />
<br />
[[File:OneDrive_2.png|1080px]]<br />
<br />
<br />
<br />
* Click on the "Save" button. A message will display asking you to reload. Click the "RELOAD NOW" link.<br />
<br />
<br />
[[File:OneDrive_1.png|1080px|]]<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0 |2020-04-26}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=Google_drive_integration_end_user_guide&diff=67205Google drive integration end user guide2020-05-08T16:15:30Z<p>Ssatam: /* Google Drive integration end user guide */</p>
<hr />
<div>=Google Drive integration end user guide= <br />
<hr><br />
{{KB|||{{ZCS 9.0}}|||}}<br />
{{WIP}}<br />
__FORCETOC__<br />
<br />
This integration offers you the opportunity to connect your Google account to Zimbra so that you may save and share files from your Google Drive.<br />
<br />
Note: End user must login their respective google account to access their Google Drive space.<br />
<br />
<br />
====Activate the Google Drive Zimlet====<br />
<br />
* Click on the "Settings" button.<br />
<br />
<br />
[[File:Google_Drive_1.png|1080px]]<br />
<br />
<br />
* Click on the "Settings".<br />
<br />
<br />
[[File:Google_drive_2.png|1080px]]<br />
<br />
<br />
* Click on "Google Drive Integration".<br />
<br />
<br />
[[File:Google_drive_3.png|1080px]]<br />
<br />
<br />
* Click on the "Activate" button to activate Google Drive.<br />
<br />
<br />
[[File:Google_drive_4.png|1080px]]<br />
<br />
<br />
* Sign In to your Google account. If you're signed into multiple accounts, you may be asked to choose one.<br />
<br />
<br />
[[File:Google_drive_5.png|1080px]]<br />
<br />
<br />
* Click the "Allow" button to authorize access to your Google Drive account from Zimbra.<br />
<br />
<br />
[[File:Google_drive_6.png|1080px]]<br />
<br />
<br />
* After a few seconds, the Activate button will be relabeled as Deactivate, indicating you have activated the Zimlet. Click on the "Save" button.<br />
<br />
<br />
[[File:Google_drive_7.png|1080px]]<br />
<br />
<br />
====Save An Attachment to your Google Drive====<br />
<br />
* Hover over the attachment you would like to save and click the download icon.<br />
<br />
<br />
[[File:Google_drive_8.png|1080px]]<br />
<br />
<br />
* Select "Google Drive" from the list of download locations.<br />
<br />
<br />
[[File:Google_drive_9.png|1080px]]<br />
<br />
<br />
<br />
* Select a folder and click on the "Select" button to save the attachment to your Google Drive.<br />
<br />
<br />
[[File:Google_drive_10.png|1080px]]<br />
<br />
<br />
<br />
* A message will display indicating that you successfully saved your attachment to Google Drive.<br />
<br />
<br />
[[File:Google_drive_11.png|1080px]]<br />
<br />
<br />
====Attaching a file from Google Drive====<br />
<br />
* Click the "Attachments" icon and select "Add files" from Google Drive.<br />
<br />
<br />
[[File:Google_drive_12.png|1080px]]<br />
<br />
<br />
* Choose the Select files to attach option to add the files as attachments in your email message.<br />
<br />
<br />
[[File:Google_drive_13.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to attach by clicking on them. Hold the Control key while clicking to select multiple items. When finished, click "Select". Do not attempt to select G Suite files (such as Google Docs, Sheets, etc.), as they cannot be opened directly from an email. Instead, link to them as shown in the next section.<br />
<br />
<br />
[[File:Google_drive_14.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:Google_drive_15.png|1080px]]<br />
<br />
<br />
====Link to a file on Google Drive====<br />
<br />
* This option is recommended for larger files which could get rejected by email servers.<br />
<br />
* Click the "Attachments" icon and select "Add files" from Google Drive.<br />
<br />
<br />
[[File:Google_drive_17.png|1080px]]<br />
<br />
<br />
* Choose the Select files to link option to add links of your Google Drive files into your email message.<br />
<br />
<br />
[[File:Google_drive_18.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to link by clicking on them. Hold the Control key while clicking to select multiple items. When finished, click "Select".<br />
<br />
<br />
[[File:Google_drive_19.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:Google_drive_20.png|1080px]]<br />
<br />
<br />
<br />
====How to send large files via Google Drive====<br />
<br />
<br />
* When trying to attach a file over a certain size, you'll be presented with the following dialog. Select "Drive" from the presented options.<br />
<br />
<br />
[[File:Google_drive_21.png|1080px]]<br />
<br />
<br />
* From the Google Drive picker, select a folder into which the large file should be uploaded and click "Select".<br />
<br />
<br />
[[File:Google_drive_22.png|1080px]]<br />
<br />
<br />
* The Inserting Link window will appear while the file is being saved to your Google Drive. Once completed, the link will appear in your email message<br />
<br />
<br />
[[File:Google_drive_23.png|1080px|middle]]<br />
<br />
<br />
<br />
* Compose your message and click the "Send" button as normal.<br />
<br />
====Re-enable the Google Drive Zimlet (troubleshooting)====<br />
<br />
* If you cannot see the Google Drive settings, you may need to re-enable your Zimlet.<br />
<br />
* Click on the "Settings" button.<br />
<br />
[[File:Google_Drive_1.png|1080px]]<br />
<br />
<br />
* Click on "Settings".<br />
<br />
<br />
[[File:Google_drive_2.png|1080px]]<br />
<br />
<br />
* Click on "Add-ons (Zimlets)" and ensure the checkbox for com_zimbra_x-google-drive is selected.<br />
<br />
<br />
[[File:Google_drive_24.png|1080px]]<br />
<br />
<br />
<br />
* Click on the "Save" button. A message will display asking you to reload. Click the "RELOAD NOW" link.<br />
<br />
<br />
[[File:Google_drive_25.png|1080px|]]<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0 |2020-04-25}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=One_drive_integration_end_user_guide&diff=67204One drive integration end user guide2020-05-08T16:14:36Z<p>Ssatam: /* OneDrive integration end user guide */</p>
<hr />
<div>=OneDrive integration end user guide= <br />
<hr><br />
{{KB|||{{ZCS 9.0}}|||}}<br />
{{WIP}}<br />
__FORCETOC__<br />
<br />
This integration offers you the opportunity to connect your Microsoft OneDrive account to Zimbra so that you may save and share files from your OneDrive.<br />
<br />
Note: End user must login their respective Microsoft account to access their OneDrive space.<br />
<br />
<br />
====Activate the One Drive Zimlet====<br />
<br />
* Click on the "Settings" button.<br />
<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on the "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "OneDrive Integration".<br />
<br />
<br />
[[File:OneDrive_23.png|1080px]]<br />
<br />
<br />
* Click on the "Activate" button to activate OneDrive.<br />
<br />
<br />
[[File:OneDrive_24.png|1080px]]<br />
<br />
<br />
* Sign In to your "OneDrive" account.<br />
<br />
<br />
[[File:OneDrive_25.png|1080px]]<br />
<br />
<br />
* Click the "Allow" button to authorize access to your OneDrive account from Zimbra.<br />
<br />
<br />
[[File:OneDrive_26.png|800px]]<br />
<br />
<br />
* After a few seconds, the "Activate" button will be relabeled as "Deactivate", indicating you have activated the Zimlet. Click on the "Save" button.<br />
<br />
<br />
[[File:OneDrive_27.png|1080px]]<br />
<br />
<br />
====Save An Attachment to your OneDrive====<br />
<br />
* Hover over the attachment you would like to save and click the "download icon".<br />
<br />
<br />
[[File:OneDrive_22.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the list of download locations.<br />
<br />
<br />
[[File:OneDrive_21.png|1080px]]<br />
<br />
<br />
<br />
* Select a folder and click on the "Open" button to save the attachment to your OneDrive.<br />
<br />
<br />
[[File:OneDrive_20.png|1080px]]<br />
<br />
<br />
<br />
* A message will display indicating that you successfully saved your attachment to OneDrive.<br />
<br />
<br />
[[File:OneDrive_19.png|1080px]]<br />
<br />
<br />
====Attaching a file from OneDrive====<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_18.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to attach option to add the files as attachments in your email message.<br />
<br />
<br />
[[File:OneDrive_17.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to attach by selecting the checkbox in the upper right corner of each document; then click "Open".<br />
<br />
<br />
[[File:OneDrive_16.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_15.png|1080px]]<br />
<br />
<br />
====Link to a file on OneDrive====<br />
<br />
<br />
This option is recommended for larger files which could get rejected by email servers.<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_14.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to link option to add links of your OneDrive files into your email message.<br />
<br />
<br />
[[File:OneDrive_13.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to link by selecting the checkbox next to each document; then click "Choose".<br />
<br />
<br />
[[File:OneDrive_12.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_11.png|1080px]]<br />
<br />
====How to send large files via OneDrive====<br />
<br />
<br />
* Click the "Attachments" icon and select Attach from my Computer.<br />
<br />
<br />
[[File:OneDrive_10.png|1080px]]<br />
<br />
<br />
* Select the file you want to attach and click "Open".<br />
<br />
<br />
[[File:OneDrive_9.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the presented options.<br />
<br />
<br />
[[File:OneDrive_8.png|1080px]]<br />
<br />
<br />
* Click "Open" in the OneDrive window to save your file to be shared from OneDrive.<br />
<br />
<br />
[[File:OneDrive_7.png|1080px]]<br />
<br />
<br />
* The "Inserting Link" window will appear while the file is being saved to your OneDrive. Once completed, the link will appear in your email message<br />
<br />
<br />
[[File:OneDrive_6.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button as normal.<br />
<br />
<br />
[[File:OneDrive_5.png|1080px]]<br />
<br />
<br />
====Re-enable the OpenDrive Zimlet (troubleshooting)====<br />
<br />
If you cannot see the OneDrive settings, you may need to re-enable your Zimlet.<br />
<br />
* Click on the "Settings" button.<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "Add-ons (Zimlets)" and ensure the checkbox for com_zimbra_x-onedrive is selected.<br />
<br />
<br />
[[File:OneDrive_2.png|1080px]]<br />
<br />
<br />
<br />
* Click on the "Save" button. A message will display asking you to reload. Click the "RELOAD NOW" link.<br />
<br />
<br />
[[File:OneDrive_1.png|1080px|]]<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0 |2020-04-26}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=One_drive_integration_end_user_guide&diff=67203One drive integration end user guide2020-05-08T16:09:58Z<p>Ssatam: /* OneDrive integration end user guide */</p>
<hr />
<div>=OneDrive integration end user guide= <br />
<hr><br />
{{KB|||{{ZCS 9.0}}|||}}<br />
{{WIP}}<br />
<br />
<br />
This integration offers you the opportunity to connect your Microsoft OneDrive account to Zimbra so that you may save and share files from your OneDrive.<br />
<br />
Note: End user must login their respective Microsoft account to access their OneDrive space.<br />
<br />
<br />
====Activate the One Drive Zimlet====<br />
<br />
* Click on the "Settings" button.<br />
<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on the "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "OneDrive Integration".<br />
<br />
<br />
[[File:OneDrive_23.png|1080px]]<br />
<br />
<br />
* Click on the "Activate" button to activate OneDrive.<br />
<br />
<br />
[[File:OneDrive_24.png|1080px]]<br />
<br />
<br />
* Sign In to your "OneDrive" account.<br />
<br />
<br />
[[File:OneDrive_25.png|1080px]]<br />
<br />
<br />
* Click the "Allow" button to authorize access to your OneDrive account from Zimbra.<br />
<br />
<br />
[[File:OneDrive_26.png|800px]]<br />
<br />
<br />
* After a few seconds, the "Activate" button will be relabeled as "Deactivate", indicating you have activated the Zimlet. Click on the "Save" button.<br />
<br />
<br />
[[File:OneDrive_27.png|1080px]]<br />
<br />
<br />
====Save An Attachment to your OneDrive====<br />
<br />
* Hover over the attachment you would like to save and click the "download icon".<br />
<br />
<br />
[[File:OneDrive_22.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the list of download locations.<br />
<br />
<br />
[[File:OneDrive_21.png|1080px]]<br />
<br />
<br />
<br />
* Select a folder and click on the "Open" button to save the attachment to your OneDrive.<br />
<br />
<br />
[[File:OneDrive_20.png|1080px]]<br />
<br />
<br />
<br />
* A message will display indicating that you successfully saved your attachment to OneDrive.<br />
<br />
<br />
[[File:OneDrive_19.png|1080px]]<br />
<br />
<br />
====Attaching a file from OneDrive====<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_18.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to attach option to add the files as attachments in your email message.<br />
<br />
<br />
[[File:OneDrive_17.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to attach by selecting the checkbox in the upper right corner of each document; then click "Open".<br />
<br />
<br />
[[File:OneDrive_16.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_15.png|1080px]]<br />
<br />
<br />
====Link to a file on OneDrive====<br />
<br />
<br />
This option is recommended for larger files which could get rejected by email servers.<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_14.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to link option to add links of your OneDrive files into your email message.<br />
<br />
<br />
[[File:OneDrive_13.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to link by selecting the checkbox next to each document; then click "Choose".<br />
<br />
<br />
[[File:OneDrive_12.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_11.png|1080px]]<br />
<br />
====How to send large files via OneDrive====<br />
<br />
<br />
* Click the "Attachments" icon and select Attach from my Computer.<br />
<br />
<br />
[[File:OneDrive_10.png|1080px]]<br />
<br />
<br />
* Select the file you want to attach and click "Open".<br />
<br />
<br />
[[File:OneDrive_9.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the presented options.<br />
<br />
<br />
[[File:OneDrive_8.png|1080px]]<br />
<br />
<br />
* Click "Open" in the OneDrive window to save your file to be shared from OneDrive.<br />
<br />
<br />
[[File:OneDrive_7.png|1080px]]<br />
<br />
<br />
* The "Inserting Link" window will appear while the file is being saved to your OneDrive. Once completed, the link will appear in your email message<br />
<br />
<br />
[[File:OneDrive_6.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button as normal.<br />
<br />
<br />
[[File:OneDrive_5.png|1080px]]<br />
<br />
<br />
====Re-enable the OpenDrive Zimlet (troubleshooting)====<br />
<br />
If you cannot see the OneDrive settings, you may need to re-enable your Zimlet.<br />
<br />
* Click on the "Settings" button.<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "Add-ons (Zimlets)" and ensure the checkbox for com_zimbra_x-onedrive is selected.<br />
<br />
<br />
[[File:OneDrive_2.png|1080px]]<br />
<br />
<br />
<br />
* Click on the "Save" button. A message will display asking you to reload. Click the "RELOAD NOW" link.<br />
<br />
<br />
[[File:OneDrive_1.png|1080px|]]<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0 |2020-04-26}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=One_drive_integration_end_user_guide&diff=67110One drive integration end user guide2020-04-26T11:23:30Z<p>Ssatam: /* OneDrive integration end user guide */</p>
<hr />
<div>=OneDrive integration end user guide= <br />
<hr><br />
{{KB|||{{ZCS 9.0}}|||}}<br />
{{WIP}}<br />
<br />
<br />
This integration offers you the opportunity to connect your Microsoft OneDrive account to Zimbra so that you may save and share files from your OneDrive.<br />
<br />
Note: End user must login their respective Microsoft account to access their OneDrive space.<br />
<br />
<br />
====Activate the One Drive Zimlet====<br />
<br />
* Click on the "Settings" button.<br />
<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on the "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "OneDrive Integration".<br />
<br />
<br />
[[File:OneDrive_23.png|1080px]]<br />
<br />
<br />
* Click on the "Activate" button to activate OneDrive.<br />
<br />
<br />
[[File:OneDrive_24.png|1080px]]<br />
<br />
<br />
* Sign In to your "OneDrive" account.<br />
<br />
<br />
[[File:OneDrive_25.png|1080px]]<br />
<br />
<br />
* Click the "Allow" button to authorize access to your OneDrive account from Zimbra.<br />
<br />
<br />
[[File:OneDrive_26.png|800px]]<br />
<br />
<br />
* After a few seconds, the "Activate" button will be relabeled as "Deactivate", indicating you have activated the Zimlet. Click on the "Save" button.<br />
<br />
<br />
[[File:OneDrive_27.png|1080px]]<br />
<br />
<br />
====Save An Attachment to your OneDrive====<br />
<br />
* Hover over the attachment you would like to save and click the "download icon".<br />
<br />
<br />
[[File:OneDrive_22.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the list of download locations.<br />
<br />
<br />
[[File:OneDrive_21.png|1080px]]<br />
<br />
<br />
<br />
* Select a folder and click on the "Select" button to save the attachment to your OneDrive.<br />
<br />
<br />
[[File:OneDrive_20.png|1080px]]<br />
<br />
<br />
<br />
* A message will display indicating that you successfully saved your attachment to OneDrive.<br />
<br />
<br />
[[File:OneDrive_19.png|1080px]]<br />
<br />
<br />
====Attaching a file from OneDrive====<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_18.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to attach option to add the files as attachments in your email message.<br />
<br />
<br />
[[File:OneDrive_17.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to attach by selecting the checkbox in the upper right corner of each document; then click "Open".<br />
<br />
<br />
[[File:OneDrive_16.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_15.png|1080px]]<br />
<br />
<br />
====Link to a file on OneDrive====<br />
<br />
<br />
* This option is recommended for larger files which could get rejected by email servers.<br />
<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_14.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to link option to add links of your OneDrive files into your email message.<br />
<br />
<br />
[[File:OneDrive_13.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to link by selecting the checkbox next to each document; then click "Choose".<br />
<br />
<br />
[[File:OneDrive_12.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_11.png|1080px]]<br />
<br />
<br />
<br />
====How to send large files via OneDrive====<br />
<br />
<br />
* Click the "Attachments" icon and select Attach from my Computer.<br />
<br />
<br />
[[File:OneDrive_10.png|1080px]]<br />
<br />
<br />
* Select the file you want to attach and click "Open".<br />
<br />
<br />
[[File:OneDrive_9.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the presented options.<br />
<br />
<br />
[[File:OneDrive_8.png|1080px]]<br />
<br />
<br />
* Click "Open" in the OneDrive window to save your file to be shared from OneDrive.<br />
<br />
<br />
[[File:OneDrive_7.png|1080px]]<br />
<br />
<br />
* The "Inserting Link" window will appear while the file is being saved to your OneDrive. Once completed, the link will appear in your email message<br />
<br />
<br />
[[File:OneDrive_6.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button as normal.<br />
<br />
<br />
[[File:OneDrive_5.png|1080px]]<br />
<br />
<br />
====Re-enable the OpenDrive Zimlet (troubleshooting)====<br />
<br />
* If you cannot see the OneDrive settings, you may need to re-enable your Zimlet.<br />
<br />
* Click on the "Settings" button.<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "Add-ons (Zimlets)" and ensure the checkbox for com_zimbra_x-onedrive is selected.<br />
<br />
<br />
[[File:OneDrive_2.png|1080px]]<br />
<br />
<br />
<br />
* Click on the "Save" button. A message will display asking you to reload. Click the "RELOAD NOW" link.<br />
<br />
<br />
[[File:OneDrive_1.png|1080px|]]<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0 |2020-04-26}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=One_drive_integration_end_user_guide&diff=67109One drive integration end user guide2020-04-26T11:22:44Z<p>Ssatam: Created page with "=One Drive integration end user guide= <hr> {{KB|||{{ZCS 9.0}}|||}} {{WIP}} This integration offers you the opportunity to connect your Microsoft OneDrive account to Zimbra..."</p>
<hr />
<div>=One Drive integration end user guide= <br />
<hr><br />
{{KB|||{{ZCS 9.0}}|||}}<br />
{{WIP}}<br />
<br />
<br />
This integration offers you the opportunity to connect your Microsoft OneDrive account to Zimbra so that you may save and share files from your OneDrive.<br />
<br />
Note: End user must login their respective Microsoft account to access their OneDrive space.<br />
<br />
<br />
====Activate the One Drive Zimlet====<br />
<br />
* Click on the "Settings" button.<br />
<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on the "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "OneDrive Integration".<br />
<br />
<br />
[[File:OneDrive_23.png|1080px]]<br />
<br />
<br />
* Click on the "Activate" button to activate OneDrive.<br />
<br />
<br />
[[File:OneDrive_24.png|1080px]]<br />
<br />
<br />
* Sign In to your "OneDrive" account.<br />
<br />
<br />
[[File:OneDrive_25.png|1080px]]<br />
<br />
<br />
* Click the "Allow" button to authorize access to your OneDrive account from Zimbra.<br />
<br />
<br />
[[File:OneDrive_26.png|800px]]<br />
<br />
<br />
* After a few seconds, the "Activate" button will be relabeled as "Deactivate", indicating you have activated the Zimlet. Click on the "Save" button.<br />
<br />
<br />
[[File:OneDrive_27.png|1080px]]<br />
<br />
<br />
====Save An Attachment to your OneDrive====<br />
<br />
* Hover over the attachment you would like to save and click the "download icon".<br />
<br />
<br />
[[File:OneDrive_22.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the list of download locations.<br />
<br />
<br />
[[File:OneDrive_21.png|1080px]]<br />
<br />
<br />
<br />
* Select a folder and click on the "Select" button to save the attachment to your OneDrive.<br />
<br />
<br />
[[File:OneDrive_20.png|1080px]]<br />
<br />
<br />
<br />
* A message will display indicating that you successfully saved your attachment to OneDrive.<br />
<br />
<br />
[[File:OneDrive_19.png|1080px]]<br />
<br />
<br />
====Attaching a file from OneDrive====<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_18.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to attach option to add the files as attachments in your email message.<br />
<br />
<br />
[[File:OneDrive_17.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to attach by selecting the checkbox in the upper right corner of each document; then click "Open".<br />
<br />
<br />
[[File:OneDrive_16.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_15.png|1080px]]<br />
<br />
<br />
====Link to a file on OneDrive====<br />
<br />
<br />
* This option is recommended for larger files which could get rejected by email servers.<br />
<br />
<br />
* Click the "Attachments" icon and select "Add files" from OneDrive.<br />
<br />
<br />
[[File:OneDrive_14.png|1080px]]<br />
<br />
<br />
* Choose the "Select files" to link option to add links of your OneDrive files into your email message.<br />
<br />
<br />
[[File:OneDrive_13.png|1080px]]<br />
<br />
<br />
* Choose the file or files you would like to link by selecting the checkbox next to each document; then click "Choose".<br />
<br />
<br />
[[File:OneDrive_12.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button.<br />
<br />
<br />
[[File:OneDrive_11.png|1080px]]<br />
<br />
<br />
<br />
====How to send large files via OneDrive====<br />
<br />
<br />
* Click the "Attachments" icon and select Attach from my Computer.<br />
<br />
<br />
[[File:OneDrive_10.png|1080px]]<br />
<br />
<br />
* Select the file you want to attach and click "Open".<br />
<br />
<br />
[[File:OneDrive_9.png|1080px]]<br />
<br />
<br />
* Select "OneDrive" from the presented options.<br />
<br />
<br />
[[File:OneDrive_8.png|1080px]]<br />
<br />
<br />
* Click "Open" in the OneDrive window to save your file to be shared from OneDrive.<br />
<br />
<br />
[[File:OneDrive_7.png|1080px]]<br />
<br />
<br />
* The "Inserting Link" window will appear while the file is being saved to your OneDrive. Once completed, the link will appear in your email message<br />
<br />
<br />
[[File:OneDrive_6.png|1080px]]<br />
<br />
<br />
* Compose your message and click the "Send" button as normal.<br />
<br />
<br />
[[File:OneDrive_5.png|1080px]]<br />
<br />
<br />
====Re-enable the OpenDrive Zimlet (troubleshooting)====<br />
<br />
* If you cannot see the OneDrive settings, you may need to re-enable your Zimlet.<br />
<br />
* Click on the "Settings" button.<br />
<br />
[[File:OneDrive_3.png|1080px]]<br />
<br />
<br />
* Click on "Settings".<br />
<br />
<br />
[[File:OneDrive_4.png|1080px]]<br />
<br />
<br />
* Click on "Add-ons (Zimlets)" and ensure the checkbox for com_zimbra_x-onedrive is selected.<br />
<br />
<br />
[[File:OneDrive_2.png|1080px]]<br />
<br />
<br />
<br />
* Click on the "Save" button. A message will display asking you to reload. Click the "RELOAD NOW" link.<br />
<br />
<br />
[[File:OneDrive_1.png|1080px|]]<br />
<br />
<br />
<br />
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"<br />
|'''Submitted by''': Sandesh Satam<br />
|}<br />
<br />
{{Article Footer|ZCS 9.0 |2020-04-26}}</div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:OneDrive_27.png&diff=67108File:OneDrive 27.png2020-04-26T11:02:35Z<p>Ssatam: </p>
<hr />
<div></div>Ssatamhttps://wiki.zimbra.com/index.php?title=File:OneDrive_26.png&diff=67107File:OneDrive 26.png2020-04-26T10:59:26Z<p>Ssatam: </p>
<hr />
<div></div>Ssatam