The Craving Mind

Step: 1 To stop zimbra all services. #su zimbra #zmcontrol stop Step: 2 To execute the below commands with new hostname #/opt/zimbra/libexec/zmsetservername -n newhostname (mail.server.lan) Step: 3 Then start the zimbra service. #zmcontrol start Ref:  https://dilliganesh.wordpress.com/2018/11/14/how-to-change-hostname-on-zimbra/

We will start our DRBD installation from where the Heartbeat finished.  We can install it at individual level. For now, a quick review of what we have: Two (2) nodes of UBUNTU Both has different static IP address (192.168.1.151 192.168.1.152) Different Hostnames (node1.hatest.com, node2.hatest.com) Installed Heartbeat with alias IP (192.168.1.150) Both nodes have Secondary Hard Disks with space of 15 GB.  (Specially required for DRBD. We can also use single unused partition to install & configure DRBD) Let’s start. First install drbd package on both nodes. root@node1:/home/sharif # apt install drbd8-utils  After installation, we can check the DRBD status. We will notice as below: root@node1:/home/sharif# /etc/init.d/drbd status ● drbd.service - LSB: Control drbd resources.   Loaded: loaded (/etc/init.d/drbd; bad; vendor preset: enabled)     Active: inactive (dead)       Docs: man:systemd-sysv-generator(8) Restart the DRBD servi...

Setup Hosts & HOSTNAME file for both nodes as below: (Node1) root@node1:/home/sharif# cat /etc/hostname  node1.hatest.com root@node1:/home/sharif# cat /etc/hosts 192.168.1.151 node1.hatest.com node1 192.168.1.152 node2.hatest.com node2 (Node2) root@node2:/home/sharif# cat /etc/hostname  node1.hatest.com root@node2:/home/sharif# cat /etc/hosts 192.168.1.152 node2.hatest.com node2 192.168.1.151 node1.hatest.com node1 Install heartbeat on both nodes: root@node1:/home/sharif# apt install heartbeat Edit below mentioned files as below: root@node1:/etc/ha.d# vim ha.cf [Create and edit ha.cf ] keepalive 2 warntime 5 deadtime 15 initdead 90 udpport 694 auto_failback on ucast ens33 192.168.1.152 logfile /var/log/ha-log node node1.hatest.com node2.hatest.com root@node1:/etc/ha.d# vim authkeys auth 2 2 crc root@node1:/etc/ha.d# chmod 600 authkeys [Same for both nodes] root@node1:/etc/ha.d# vim haresources node1.hatest.com IPaddr::192.168.1.150/24/ens33:0 Now, we will...

su zimbra zmprov mcf +zimbraReverseProxySSLProtocols TLSv1 zmprov mcf +zimbraReverseProxySSLProtocols TLSv1.2 zmproxyctl restart

To do this, you can run the following: zmprov ms `zmhostname` zimbraReverseProxyMailMode redirect This will redirect your URLs to the zimbra hostname based HTTPs. Now, restart the proxy services: su - zimbra zmproxyctl restart Hope this helps. Ref: https://mellowhost.com/blog/how-to-redirect-http-to-https-zimbra-8-8.html

One of our client was facing problem that one of their internal user sends/forward mail to another internal user but receiver does not receive the mail. zimbra.log shows mail delivered to receivers mailbox. mailbox.log shows receiver's mailbox rejected the mail by detecting it as a duplicate email. We could do following things: check current cache size of zimbra: $ zmprov gcf zimbraMessageIdDedupeCacheSize zimbraMessageIdDedupeCacheSize: 3000  Option-1 Increase the cache size zmprov mcf zimbraMessageIdDedupeCacheSize 5000 zmmailboxdctl restart Option-2 disable the Deduplication cache size zmprov mcf zimbraMessageIdDedupeCacheSize 0 zmmailboxdctl restart Ref: https://wiki.zimbra.com/wiki/How_to_deliver_messages_with_duplicate_ids

Basic Connectivity:   Router (Broadband/mikrotik |dhcp enabled) >>> Unifi + LAPTOP Unifi (Powered ON) [POE port] >>>> LAPTOP [LAN port] Step1: Open Unifi controller in the browser. Step2: Open a site in the name of that client and keep the tab open. Step3: Open unifi discovery tool. Step4: Any newly connected (which is still unadopted) unifi device will appear in this tool. Note: In discovery tool,we will get three options to use. Primarily we will use manage and input url ( https://unifi.domain.com:8080/inform ) and apply. Step5: We will notice the communication between discovery tool and unifi controller in the controller.   . Step6: We will notice the communication between discovery tool and unifi controller in the controller.  Step7: We will notice that the unifi device is appreared in the controller (In our created site) and waiting for our adoption. Step8: We will adopt the device in the controller. Then the device will disappear fro...