The Craving Mind

 Check whether antispam and antivirus service is enabled currently on server using the given command zmprov -l gs <mail.example.com> | egrep -i 'serviceen|servicein'  The above command will list all the services which are currently installed and enabled on the server. Disable the antivirus and antispam services using the given commands zmprov -l ms <mail.example.com> -zimbraServiceEnabled antispam  zmprov -l ms <mail.example.com> -zimbraServiceEnabled amavis zmprov -l ms <mail.example.com> -zimbraServiceEnabled antivirus  Comment the following line in the file /opt/zimbra/postfix/conf/main.cf content_filter = smtp-amavis:[127.0.0.1]:10024  Restart services on server zmcontrol restart  Confirm that the antispam and antivirus services are disabled with the given command zmprov -l gs <mail.example.com> | egrep -i 'serviceen|servicein'  zmcontrol status 

 L inux Booting procedure The stages involved in Linux Booting Process are: 1. BIOS 2. Boot Loader     - MBR     - GRUB 3. Kernel 4. Init 5. Runlevel scripts 6. User Interface     STEP 1. BIOS This is the first thing which loads once you power on your machine. When you press the power button of the machine, CPU looks out into ROM for further instruction. The ROM contains JUMP function in the form of instruction which tells the CPU to bring up the BIOS BIOS determine all the list of bootable devices available in the system. Prompts to select bootable device which can be Hard Disk, CD/DVD-ROM, Floppy Drive, USB Flash Memory Stick Etc.. Operating System tries to boot from Hard Disk where the MBR contains primary boot loader.     STEP 2. Boot Loader  To be very brief this phase includes loading of the boot loader (MBR and GRUB/LILO) into memory to bring up the kernel. MBR (Master Boot R...

Ref: https://www.youtube.com/watch?v=JxueKaNJ89s

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