TetraWiki - User contributions [en]

Technical Training Serssions 2021 Linux Team

2021-11-03T10:58:42Z

Chandrakant:

[[category:Training‏‎]]

==Session for Client Introduction with Technologies (Part1) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee==

<HTML5video type="youtube" width="640" height="480" autoplay="false">Okd_MQE2oqw</HTML5video>

==Session for Client Introduction with Technologies (Part2) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">7VX1kXFQWEs</HTML5video>

==Session for Client Introduction with Technologies - capital bank . Dated 18th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">9rHaInJVD84</HTML5video>

==Session for Client Introduction with Technologies - JBOSS/POSTGRESQL Brijraj/Beetel . Dated 19th Jan 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">MZZKR0Lt8FQ</HTML5video>

==Session for Client Introduction with Technologies - LAMP . Dated 20th Jan 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">Jw5dVkNqy5w</HTML5video>

==Session for Introduction with Technologies - Generic . Dated 24th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">PGeTUt9vj50</HTML5video>

==Session Harsh for Team about Infosys-ITD zimbra Deployment . Dated 25th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">ar1q3ufH2jk</HTML5video>

==Session for Introduction with Mail Concept . Dated 25th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">uN8iTDPr9bQ</HTML5video>

==Session Harsh for Team about Infosys-ITD ELK Deployment . Dated 26th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">e7AfaibdCVM</HTML5video>

==Session for Mail Concept (Contd). Dated 26th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">k4wIxQVnf7I</HTML5video>

==Session Harsh for Team about Samba and Desktop Central Deployment at Triburg. Dated 27th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">6CHqu7iuY68</HTML5video>

==Session Harsh for Team about NextCloud deployment at Triburg. Dated 1st April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">RFTOkS71vRM</HTML5video>

==Session Harsh for Team about Various Clients deployments. Dated 2nd April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">jdxJAKkfUTs</HTML5video>

==Session for Zimbra Mail Concept (Contd).Part2 Dated 2nd April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">QIvBgsFTEiA</HTML5video>

==Session for Zimbra Mail Log Analysis Approach Dated 5th April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">CcngpTUNZZE</HTML5video>

==Session for Zimbra Mail Log Analysis Approach (part2) Dated 6th April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">nSb4il5IlvE</HTML5video>

==Session for Essel and Spectra (part2) Dated 2nd October 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">sN3e-nhIp2U</HTML5video>

==Session for Client Introduction with Technologies (Part1). Dated 2nd November 2021 - Tetra Support Staff - Chandra Kant Shakya==

<HTML5video type="youtube" width="640" height="480" autoplay="false">ESNTkWXlFr4</HTML5video>

==Session for Client Introduction with Technologies (Part2). Dated 3rd November 2021 - Tetra Support Staff - Chandra Kant Shakya==

<HTML5video type="youtube" width="640" height="480" autoplay="false">YoFE2jhswa8</HTML5video>

Technical Training Serssions 2021 Linux Team

2021-11-02T11:37:56Z

Chandrakant:

File:Bls-for-windows.pdf

2021-10-27T16:25:10Z

Chandrakant:

BLS-Active-Sync

2021-10-27T16:17:03Z

Chandrakant:

Set up Exchange Email on Android Devices(via ActiveSync)

1. On your device, go to Menu > Settings.

2. At the bottom of the Settings screen, tap Accounts and sync.

3. At the bottom of the Accounts and sync screen, tap Add account.

4. On the Add account screen, tap Exchange .

5. Enter your workplace email address.

6. Touch Password and enter your email account Password.

7. Fill all details.
• Server Name:Type in the Exchange Proxy Server.
• Domain: Enter your domain

8. Your email is now ready to be used on your device.

BLS-Active-Sync

2021-10-27T16:16:37Z

Chandrakant:

Set up Exchange Email on Android Devices(via ActiveSync)

1. On your device, go to Menu > Settings.

2. At the bottom of the Settings screen, tap Accounts and sync.

3. At the bottom of the Accounts and sync screen, tap Add account.
4. On the Add account screen, tap Exchange .
5. Enter your workplace email address.
6. Touch Password and enter your email account Password.
7. Fill all details.
• Server Name:Type in the Exchange Proxy Server.
• Domain: Enter your domain
8. Your email is now ready to be used on your device.

BLS-Active-Sync

2021-10-27T16:16:10Z

Chandrakant:

Set up Exchange Email on Android Devices(via ActiveSync)

1. On your device, go to Menu > Settings.
2. At the bottom of the Settings screen, tap Accounts and sync.
3. At the bottom of the Accounts and sync screen, tap Add account.
4. On the Add account screen, tap Exchange .
5. Enter your workplace email address.
6. Touch Password and enter your email account Password.
7. Fill all details.
• Server Name:Type in the Exchange Proxy Server.
• Domain: Enter your domain
8. Your email is now ready to be used on your device.

BLS-Active-Sync

2021-10-27T16:12:15Z

Chandrakant: Replaced content with " BLS Active sysnc for IOS mobile 1) First you click on your mobile settings."

BLS Active sysnc for IOS mobile

1) First you click on your mobile settings.

BLS-Active-Sync

2021-10-27T16:07:32Z

Chandrakant: Created page with "Exchange ActiveSync in Exchange Server 08/20/2021 3 minutes to read +2 Exchange ActiveSync is an Exchange synchronization protocol that's optimized to work together with..."

Exchange ActiveSync in Exchange Server
08/20/2021
3 minutes to read

+2
Exchange ActiveSync is an Exchange synchronization protocol that's optimized to work together with high-latency and low-bandwidth networks. The protocol, based on HTTP and XML, lets mobile phones access an organization's information on a server that's running Microsoft Exchange.

Overview of Exchange ActiveSync

Exchange ActiveSync lets mobile phone users access their email, calendar, contacts, and tasks, and lets them continue to access this information when they're working offline.

Standard encryption services add security to mobile communication with the server. You can configure Exchange ActiveSync to use Secure Sockets Layer (SSL) encryption for communications between the Exchange server and the mobile device.

Features in Exchange ActiveSync

Exchange ActiveSync provides the following:

Support for HTML messages

Support for follow-up flags

Conversation grouping of email messages

Ability to synchronize or not synchronize an entire conversation

Synchronization of Short Message Service (SMS) messages with a user's Exchange mailbox

Support for viewing message reply status

Support for fast message retrieval

Meeting attendee information

Enhanced Exchange Search

PIN reset

Enhanced device security through password policies

Autodiscover for over-the-air provisioning

Support for setting automatic replies when users are away, on vacation, or out of the office

Support for task synchronization

Direct Push

Support for availability information for contacts

Managing Exchange ActiveSync

By default, Exchange ActiveSync is enabled. All users who have an Exchange mailbox can synchronize their mobile device with the Microsoft Exchange server.

You can perform the following Exchange ActiveSync tasks:

Enable and disable Exchange ActiveSync for users

Set policies such as minimum password length, device locking, and maximum failed password attempts

Initiate a remote wipe to clear all data from a lost or stolen mobile phone

Run a variety of reports for viewing or exporting into a variety of formats

Control which types of mobile devices can synchronize with your organization through device access rules

Managing mobile device access in Exchange ActiveSync
You can control which mobile devices can synchronize with Exchange Server. You do this by monitoring new mobile devices as they connect to your organization or by setting up rules that determine which types of mobile devices are allowed to connect. Regardless of the method you choose to specify which mobile devices can synchronize, you can approve or deny access for any specific mobile device for a specific user at any time.

Device security features in Exchange ActiveSync
In addition to the ability to configure security options for communications between the Exchange server and your mobile devices, Exchange ActiveSync offers the following features to enhance the security of mobile devices:

Remote wipe: If a mobile device is lost, stolen, or otherwise compromised, you can issue a remote wipe command from the Exchange Server computer or from any Web browser by using Outlook Web App. This command erases all data from the mobile device.

Device password policies: Exchange ActiveSync lets you configure several options for device passwords. The device password options include the following:

Minimum password length (characters): This option specifies the length of the password for the mobile device. The default length is 4 characters, but as many as 18 can be included.

Minimum number of character sets: Use this text box to specify the complexity of the alphanumeric password and force users to use a number of different sets of characters from among the following: lowercase letters, uppercase letters, symbols, and numbers.

Require alphanumeric password: This option determines password strength. You can enforce the usage of a character or symbol in the password in addition to numbers.

Inactivity time (seconds): This option determines how long the mobile device must be inactive before the user is prompted for a password to unlock the mobile device.

Enforce password history: Select this check box to force the mobile phone to prevent the user from reusing their previous passwords. The number that you set determines the number of past passwords that the user won't be allowed to reuse.

Enable password recovery: Select this check box to enable password recovery for the mobile device. Administrators can use the Get-ActiveSyncDeviceStatistics cmdlet to look up the user's recovery password.

Wipe device after failed (attempts): This option lets you specify whether you want the phone's memory to be wiped after multiple failed password attempts.

Device encryption policies: There are a number of mobile device encryption policies that you can enforce for a group of users. These policies include the following:

Require encryption on device: Select this check box to require encryption on the mobile device. This increases security by encrypting all information on the mobile device.

Require encryption on storage cards: Select this check box to require encryption on the mobile device's removable storage card. This increases security by encrypting all information on the storage cards for the mobile device.

Category:BLS INTERNATIONAL

2021-10-27T16:04:56Z

Chandrakant:

[[BLS-Active-Sync]]

Category:BLS INTERNATIONAL

2021-10-27T16:03:45Z

Chandrakant: Blanked the page

Category:BLS INTERNATIONAL

2021-10-27T16:03:07Z

Chandrakant:

[[File:Example.jpg]][[category:Tetra Clients]]
BLS Active sysnc for IOS mobile
1) First you click on your mobile settings.2) Now click on the mail option.3) Click on accounts.
4) Click on Add Account Then show like this.5) Click on other option and fill details.6) Now Click Configure Manually.
Next7. Fill the details be carefully because servername and domain is incorrect so can not connect

Category talk:BLS INTERNATIONAL

2021-10-27T15:57:04Z

Chandrakant: Blanked the page

Category talk:BLS INTERNATIONAL

2021-10-27T15:56:51Z

Chandrakant: Created page with "BLS"

BLS

Category:BLS INTERNATIONAL

2021-10-27T15:56:30Z

Chandrakant:

[[category:Tetra Clients]]

Category:BLS INTERNATIONAL

2021-10-27T15:56:09Z

Chandrakant:

[[category:Tetra Clients]]
BLS-active sync

User:Chandrakant

2021-10-21T03:56:16Z

Chandrakant: Blanked the page

Category:BLS-Active-Sync-Mobile

2021-10-21T03:31:48Z

Chandrakant: Created page with "BLS-Mobile"

[[BLS-Mobile]]

User:Chandrakant

2021-10-21T03:29:48Z

Chandrakant: Created page with "category:BLS-Active-Sync-Mobile"

[[category:BLS-Active-Sync-Mobile]]

File:BLS-for-android.pdf

2021-10-21T03:23:57Z

Chandrakant: BLS-Active-sync-Mobile

BLS-Active-sync-Mobile

Technical Training Serssions 2021 Linux Team

2021-10-11T15:44:20Z

Chandrakant:

Technical Training Serssions 2021 Linux Team

2021-10-11T14:25:10Z

Chandrakant:

Technical Training Serssions 2021 Linux Team

2021-10-11T14:21:27Z

Chandrakant:

Technical Training Serssions 2021 Linux Team

2021-10-11T11:21:25Z

Chandrakant:

Technical Training Serssions 2021 Linux Team

2021-10-11T11:16:00Z

Chandrakant:

[[category:Training‏‎]]

==Session for Client Introduction with Technologies (Part1) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee==

<HTML5video type="youtube" width="640" height="480" autoplay="false">Okd_MQE2oqw</HTML5video>

==Session for Client Introduction with Technologies (Part2) . Dated 16th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">7VX1kXFQWEs</HTML5video>

==Session for Client Introduction with Technologies - capital bank . Dated 18th Jan 2021 - Tetra Support Staff - Biswajit Banerjee ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">9rHaInJVD84</HTML5video>

==Session for Client Introduction with Technologies - JBOSS/POSTGRESQL Brijraj/Beetel . Dated 19th Jan 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">MZZKR0Lt8FQ</HTML5video>

==Session for Client Introduction with Technologies - LAMP . Dated 20th Jan 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">Jw5dVkNqy5w</HTML5video>

==Session for Introduction with Technologies - Generic . Dated 24th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">PGeTUt9vj50</HTML5video>

==Session Harsh for Team about Infosys-ITD zimbra Deployment . Dated 25th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">ar1q3ufH2jk</HTML5video>

==Session for Introduction with Mail Concept . Dated 25th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">uN8iTDPr9bQ</HTML5video>

==Session Harsh for Team about Infosys-ITD ELK Deployment . Dated 26th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">e7AfaibdCVM</HTML5video>

==Session for Mail Concept (Contd). Dated 26th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">k4wIxQVnf7I</HTML5video>

==Session Harsh for Team about Samba and Desktop Central Deployment at Triburg. Dated 27th Mar 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">6CHqu7iuY68</HTML5video>

==Session Harsh for Team about NextCloud deployment at Triburg. Dated 1st April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">RFTOkS71vRM</HTML5video>

==Session Harsh for Team about Various Clients deployments. Dated 2nd April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">jdxJAKkfUTs</HTML5video>

==Session for Zimbra Mail Concept (Contd).Part2 Dated 2nd April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">QIvBgsFTEiA</HTML5video>

==Session for Zimbra Mail Log Analysis Approach Dated 5th April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">CcngpTUNZZE</HTML5video>

==Session for Zimbra Mail Log Analysis Approach (part2) Dated 6th April 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">nSb4il5IlvE</HTML5video>

==Session for Zimbra Mail Log Analysis Approach (part2) Dated 2nd October 2021 ==

<HTML5video type="youtube" width="640" height="480" autoplay="false">W</HTML5video>

Archive user addition for triburg main server

2021-04-01T05:18:35Z

Chandrakant:

[[category:Triburg]]
[[category:Zimbra]]

== Manual Addition of Archive users for triburg Mail server ==

* User @tetraiburg.co.in should be create on mail.triburg.co.in
* Create same user in archive server via cli
zmprov ca user@archive.triburg.co.in "very_secure_PW_31812"

* Add user and archive user in /opt/zimbra/data/archivelist

user@triburg.co.in user@archive.triburg.co.in

*postmap /opt/zimbra/data/archivelist

Archive user addition for triburg main server

2021-04-01T05:13:14Z

Chandrakant: Created page with "category:Triburg category:Zimbra == Manual Addition of Archive users for triburg Mail server == * User @tetraiburg.co.in should be create on mail.triburg.co.in * C..."

Zimbra Archive Server

2021-04-01T05:05:14Z

Chandrakant: /* Postfix */

[[Category:Zimbra]]
[[Category:Sandhar Technologies]]
[[Category:Triburg]]

==Simple archival server for Zimbra OSE==

==Introduction==

This document shows how to create a simple archiving server. If you have a user 'keyur@example.com', all mails sent to and from this email ID will be forwarded to 'keyur@archive.example.com'.
We will need two servers for this. Both will be installed with Zimbra, one being the live mail server 'example.com', and the other the archiving server, 'archive.example.com'. The archiving server should have a much larger HDD drive than the mail server, preferably formatted using LVM, to allow for expansion later.

The installation on each server will be independent, ie, this isn't a multi-server setup. Each server will be a single-server, with the only difference being the domain names.

In this example, let's assume the live server's domain is 'example.com', with IP 192.168.1.5, and the archiving server is 'archive.example.com', with IP 192.168.1.18. Install Zimbra on both as usual.

==DNS==

The servers will require a local DNS, as we use this to forward the mails. In this example, I will assume that we have set up a caching name server using bind on the live server. Typical entries would be something like this:
example.com. IN A 192.0.43.10
mail.example.com. IN A 192.168.1.5
example.com. IN MX 10 mail.example.com.
Along with this, we need to add an A and MX record for archive.example.com as well.
archive.example.com. IN A 192.168.1.18
archive.example.com. IN MX 10 archive.example.com.
Now all mails addressed to 'archive.example.com' will be forwarded to the archive server.

==Postfix==
In postfix, we can specify an email address to which all incoming and outgoing mails from a particular email ID will be forwarded to. This is done using 'sender_bcc_maps' and 'recipient_bcc_maps'. All these changes are done only on the main server.
We make the following entries at the end of /opt/zimbra/postfix/conf/main.cf

sender_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist

The file '/opt/zimbra/postfix/conf/archivelist' will have users in the following format: keyur@example.com keyur@archive.example.com
All mails to and from keyur@example.com will be forwarded to keyur@archive.example.com.

In case of Zimbra 8.7 and Above add the following in /opt/zimbra/common/conf/main.cf

sender_bcc_maps = lmdb:/opt/zimbra/data/archivelist
recipient_bcc_maps = lmdb:/opt/zimbra/data/archivelist

==Manual addition==
Create a user on the main server, and then the corresponding user on the archive server. Then add the users in the format as show above to the file '/opt/zimbra/data/archivelist', and then run the postmap command as the zimbra user:
$ postmap /opt/zimbra/data/archivelist
$ postfix reload

==Script==
The following script to add users automatically on the archive server, and also to the 'archivelist' file. Run this on the main server, and all users will be automatically added. You can place it in the crontab for every half an hour, so that when a new user is created on the main server, he/she will be automatically added to the archive server. SSH using keys (password-less ssh) between the main and archive server is necessary for the script to function.

#!/bin/bash
# ENSURE ALL THE SERVERS HAVE PASSWORDLESS SSH AUTHENTICATON (Login using keys),
# OR THE SCRIPT WILL FAIL
# -----------------------------------------------------------------------------
# Zimbra Archiving
#
# This script will add users that are present on the main Zimbra server, but not
# on the archival server. It will also make the appropriate changes in postfix.
# ------------------------------------------------------------------------------
# IP of the archive server (archive.example.com)
ARCHIP=172.16.1.17
# File names of example.com and archive.example.com users
# MAINLST is the userlist from the main server (example.com)
# ARLST is the userlist from the archive server (archive.example.com)
MAINLST=mainserverlist
ARLST=archiveuserlist
# Emptying out the input file for zmprov
echo "" > /tmp/zmprovarchiv
# Getting userlist from the archive server
ssh $ARCHIP 'su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/archiveuserlist" -l zimbra'
rsync -Pa $ARCHIP:/tmp/archiveuserlist /tmp/$ARLIST
# Getting userlist from local (main) server
su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/$MAINLST" -l zimbra
# Sorting the files for comparison
sort /tmp/$MAINLST > /tmp/sorted$MAINLST
sort /tmp/$ARLST > /tmp/sorted$ARLST
# Comparing the files, and getting the unique users of the example.com domain
# This will get the new users created on example.com, but not present on the archive server
comm -23 /tmp/sorted$MAINLST /tmp/sorted$ARLST > /tmp/newusers
echo "Checking if there are new users"
if [ -s /tmp/newusers ]; then
# Loop to read users one by one
for newuser in `cat /tmp/newusers`; do
# Creating a file that will be the input for zmprov.
# This will create the new user accounts on the archive server.
# The user's passwords have been set to 'very_secure_PW_31812'
echo "ca $newuser@archive.triburg.co.in very_secure_PW_31812" >> /tmp/zmprovarchiv
done
# Creates the file for postfix mapping. This file contains users in the form of 'from' and 'to'
awk '{print $1"@triburg.co.in","\t",$1"@archive.triburg.co.in"}' /tmp/newusers >> /opt/zimbra/postfix/conf/archivelist
# rsync the zmprov file to the archive server
rsync -Pa /tmp/zmprovarchiv $ARCHIP:/tmp
# Runs the zmprov command to add users on the archive server
ssh $ARCHIP 'su -l zimbra -c zmprov < /tmp/zmprovarchiv'
# Postmapping on the servers
su -c "postmap /opt/zimbra/postfix/conf/archivelist" -l zimbra
su -c "postfix reload" -l zimbra
else
exit
fi

Made By
Abhinav Sharma

Zimbra Archive Server

2021-04-01T05:02:42Z

Chandrakant: /* Postfix */

[[Category:Zimbra]]
[[Category:Sandhar Technologies]]
[[Category:Triburg]]

==Simple archival server for Zimbra OSE==

==Introduction==

This document shows how to create a simple archiving server. If you have a user 'keyur@example.com', all mails sent to and from this email ID will be forwarded to 'keyur@archive.example.com'.
We will need two servers for this. Both will be installed with Zimbra, one being the live mail server 'example.com', and the other the archiving server, 'archive.example.com'. The archiving server should have a much larger HDD drive than the mail server, preferably formatted using LVM, to allow for expansion later.

The installation on each server will be independent, ie, this isn't a multi-server setup. Each server will be a single-server, with the only difference being the domain names.

In this example, let's assume the live server's domain is 'example.com', with IP 192.168.1.5, and the archiving server is 'archive.example.com', with IP 192.168.1.18. Install Zimbra on both as usual.

==DNS==

The servers will require a local DNS, as we use this to forward the mails. In this example, I will assume that we have set up a caching name server using bind on the live server. Typical entries would be something like this:
example.com. IN A 192.0.43.10
mail.example.com. IN A 192.168.1.5
example.com. IN MX 10 mail.example.com.
Along with this, we need to add an A and MX record for archive.example.com as well.
archive.example.com. IN A 192.168.1.18
archive.example.com. IN MX 10 archive.example.com.
Now all mails addressed to 'archive.example.com' will be forwarded to the archive server.

==Postfix==
In postfix, we can specify an email address to which all incoming and outgoing mails from a particular email ID will be forwarded to. This is done using 'sender_bcc_maps' and 'recipient_bcc_maps'. All these changes are done only on the main server.
We make the following entries at the end of /opt/zimbra/postfix/conf/main.cf

sender_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist

The file '/opt/zimbra/postfix/conf/archivelist' will have users in the following format: keyur@example.com keyur@archive.example.com
All mails to and from keyur@example.com will be forwarded to keyur@archive.example.com.

In case of Zimbra 8.5 and Above add the following in /opt/zimbra/postfix/main.cf

sender_bcc_maps = lmdb:/opt/zimbra/data/archivelist
recipient_bcc_maps = lmdb:/opt/zimbra/data/archivelist

==Manual addition==
Create a user on the main server, and then the corresponding user on the archive server. Then add the users in the format as show above to the file '/opt/zimbra/data/archivelist', and then run the postmap command as the zimbra user:
$ postmap /opt/zimbra/data/archivelist
$ postfix reload

==Script==
The following script to add users automatically on the archive server, and also to the 'archivelist' file. Run this on the main server, and all users will be automatically added. You can place it in the crontab for every half an hour, so that when a new user is created on the main server, he/she will be automatically added to the archive server. SSH using keys (password-less ssh) between the main and archive server is necessary for the script to function.

#!/bin/bash
# ENSURE ALL THE SERVERS HAVE PASSWORDLESS SSH AUTHENTICATON (Login using keys),
# OR THE SCRIPT WILL FAIL
# -----------------------------------------------------------------------------
# Zimbra Archiving
#
# This script will add users that are present on the main Zimbra server, but not
# on the archival server. It will also make the appropriate changes in postfix.
# ------------------------------------------------------------------------------
# IP of the archive server (archive.example.com)
ARCHIP=172.16.1.17
# File names of example.com and archive.example.com users
# MAINLST is the userlist from the main server (example.com)
# ARLST is the userlist from the archive server (archive.example.com)
MAINLST=mainserverlist
ARLST=archiveuserlist
# Emptying out the input file for zmprov
echo "" > /tmp/zmprovarchiv
# Getting userlist from the archive server
ssh $ARCHIP 'su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/archiveuserlist" -l zimbra'
rsync -Pa $ARCHIP:/tmp/archiveuserlist /tmp/$ARLIST
# Getting userlist from local (main) server
su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/$MAINLST" -l zimbra
# Sorting the files for comparison
sort /tmp/$MAINLST > /tmp/sorted$MAINLST
sort /tmp/$ARLST > /tmp/sorted$ARLST
# Comparing the files, and getting the unique users of the example.com domain
# This will get the new users created on example.com, but not present on the archive server
comm -23 /tmp/sorted$MAINLST /tmp/sorted$ARLST > /tmp/newusers
echo "Checking if there are new users"
if [ -s /tmp/newusers ]; then
# Loop to read users one by one
for newuser in `cat /tmp/newusers`; do
# Creating a file that will be the input for zmprov.
# This will create the new user accounts on the archive server.
# The user's passwords have been set to 'very_secure_PW_31812'
echo "ca $newuser@archive.triburg.co.in very_secure_PW_31812" >> /tmp/zmprovarchiv
done
# Creates the file for postfix mapping. This file contains users in the form of 'from' and 'to'
awk '{print $1"@triburg.co.in","\t",$1"@archive.triburg.co.in"}' /tmp/newusers >> /opt/zimbra/postfix/conf/archivelist
# rsync the zmprov file to the archive server
rsync -Pa /tmp/zmprovarchiv $ARCHIP:/tmp
# Runs the zmprov command to add users on the archive server
ssh $ARCHIP 'su -l zimbra -c zmprov < /tmp/zmprovarchiv'
# Postmapping on the servers
su -c "postmap /opt/zimbra/postfix/conf/archivelist" -l zimbra
su -c "postfix reload" -l zimbra
else
exit
fi

Made By
Abhinav Sharma

Zimbra Archive Server

2021-04-01T05:01:19Z

Chandrakant: /* Manual addition */

[[Category:Zimbra]]
[[Category:Sandhar Technologies]]
[[Category:Triburg]]

==Simple archival server for Zimbra OSE==

==Introduction==

This document shows how to create a simple archiving server. If you have a user 'keyur@example.com', all mails sent to and from this email ID will be forwarded to 'keyur@archive.example.com'.
We will need two servers for this. Both will be installed with Zimbra, one being the live mail server 'example.com', and the other the archiving server, 'archive.example.com'. The archiving server should have a much larger HDD drive than the mail server, preferably formatted using LVM, to allow for expansion later.

The installation on each server will be independent, ie, this isn't a multi-server setup. Each server will be a single-server, with the only difference being the domain names.

In this example, let's assume the live server's domain is 'example.com', with IP 192.168.1.5, and the archiving server is 'archive.example.com', with IP 192.168.1.18. Install Zimbra on both as usual.

==DNS==

The servers will require a local DNS, as we use this to forward the mails. In this example, I will assume that we have set up a caching name server using bind on the live server. Typical entries would be something like this:
example.com. IN A 192.0.43.10
mail.example.com. IN A 192.168.1.5
example.com. IN MX 10 mail.example.com.
Along with this, we need to add an A and MX record for archive.example.com as well.
archive.example.com. IN A 192.168.1.18
archive.example.com. IN MX 10 archive.example.com.
Now all mails addressed to 'archive.example.com' will be forwarded to the archive server.

==Postfix==
In postfix, we can specify an email address to which all incoming and outgoing mails from a particular email ID will be forwarded to. This is done using 'sender_bcc_maps' and 'recipient_bcc_maps'. All these changes are done only on the main server.
We make the following entries at the end of /opt/zimbra/postfix/conf/main.cf

sender_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = hash:/opt/zimbra/postfix/conf/archivelist

The file '/opt/zimbra/postfix/conf/archivelist' will have users in the following format: keyur@example.com keyur@archive.example.com
All mails to and from keyur@example.com will be forwarded to keyur@archive.example.com.

In case of Zimbra 8.5 and Above add the following in /opt/zimbra/postfix/main.cf

sender_bcc_maps = lmdb:/opt/zimbra/postfix/conf/archivelist
recipient_bcc_maps = lmdb:/opt/zimbra/postfix/conf/archivelist

==Manual addition==
Create a user on the main server, and then the corresponding user on the archive server. Then add the users in the format as show above to the file '/opt/zimbra/data/archivelist', and then run the postmap command as the zimbra user:
$ postmap /opt/zimbra/data/archivelist
$ postfix reload

==Script==
The following script to add users automatically on the archive server, and also to the 'archivelist' file. Run this on the main server, and all users will be automatically added. You can place it in the crontab for every half an hour, so that when a new user is created on the main server, he/she will be automatically added to the archive server. SSH using keys (password-less ssh) between the main and archive server is necessary for the script to function.

#!/bin/bash
# ENSURE ALL THE SERVERS HAVE PASSWORDLESS SSH AUTHENTICATON (Login using keys),
# OR THE SCRIPT WILL FAIL
# -----------------------------------------------------------------------------
# Zimbra Archiving
#
# This script will add users that are present on the main Zimbra server, but not
# on the archival server. It will also make the appropriate changes in postfix.
# ------------------------------------------------------------------------------
# IP of the archive server (archive.example.com)
ARCHIP=172.16.1.17
# File names of example.com and archive.example.com users
# MAINLST is the userlist from the main server (example.com)
# ARLST is the userlist from the archive server (archive.example.com)
MAINLST=mainserverlist
ARLST=archiveuserlist
# Emptying out the input file for zmprov
echo "" > /tmp/zmprovarchiv
# Getting userlist from the archive server
ssh $ARCHIP 'su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/archiveuserlist" -l zimbra'
rsync -Pa $ARCHIP:/tmp/archiveuserlist /tmp/$ARLIST
# Getting userlist from local (main) server
su -c "zmprov -l gaa | cut -d\@ -f1 > /tmp/$MAINLST" -l zimbra
# Sorting the files for comparison
sort /tmp/$MAINLST > /tmp/sorted$MAINLST
sort /tmp/$ARLST > /tmp/sorted$ARLST
# Comparing the files, and getting the unique users of the example.com domain
# This will get the new users created on example.com, but not present on the archive server
comm -23 /tmp/sorted$MAINLST /tmp/sorted$ARLST > /tmp/newusers
echo "Checking if there are new users"
if [ -s /tmp/newusers ]; then
# Loop to read users one by one
for newuser in `cat /tmp/newusers`; do
# Creating a file that will be the input for zmprov.
# This will create the new user accounts on the archive server.
# The user's passwords have been set to 'very_secure_PW_31812'
echo "ca $newuser@archive.triburg.co.in very_secure_PW_31812" >> /tmp/zmprovarchiv
done
# Creates the file for postfix mapping. This file contains users in the form of 'from' and 'to'
awk '{print $1"@triburg.co.in","\t",$1"@archive.triburg.co.in"}' /tmp/newusers >> /opt/zimbra/postfix/conf/archivelist
# rsync the zmprov file to the archive server
rsync -Pa /tmp/zmprovarchiv $ARCHIP:/tmp
# Runs the zmprov command to add users on the archive server
ssh $ARCHIP 'su -l zimbra -c zmprov < /tmp/zmprovarchiv'
# Postmapping on the servers
su -c "postmap /opt/zimbra/postfix/conf/archivelist" -l zimbra
su -c "postfix reload" -l zimbra
else
exit
fi

Made By
Abhinav Sharma