TetraWiki - User contributions [en]

Category:JIL

2026-01-03T11:36:16Z

Biswajit:

[[Category:JIL]]

[[File:Jalindia_cluster_installation_and_configuration.pdf]]

Category:JIL

2026-01-03T11:35:39Z

Biswajit:

[[Category:JIL]]

[[File:Example.jpg]]

Category:JIL

2026-01-03T11:27:05Z

Biswajit:

[[Category:JIL]]

CSC Cloudstack Mariadb Galera Cluster Corruption issue

2025-12-04T01:15:48Z

Biswajit:

[[category:CSC]]
[[Category:Cloudstack]]

Issue : The Mariadb Galera Cluster Got Stuck , Data Corruption and Cloudstack Failed

Diagnosis and Solution Process

1. Stop the Mariadb process on both the nodes . if not successful , disable , mask and then kill the Process on both the node .

''ps -ef | grep mysql''
OR
''systemctl status mariadb''
if not successful then do
''systemctl disable mariadb''
''systemctl mask mariadb''
''pkill -9 -u mysql''
''systemctl status mariadb''

2.This step is only preferred , but you can use own judgement for which node's data will be more reliable .
sudo -u mysql mariadbd --wsrep-recover # run on both nodes
What you are looking for: You will see a line that looks like this: ... [Note] WSREP: Recovered position: 5a7b3b-.... : 10540
The number after the colon (e.g., 10540) is your Sequence Number.
The Winner: The node with the HIGHER number.

3. On the Winner Node ONLY:( Or on the Preferred node )

Edit /var/lib/mysql/grastate.dat.
Set safe_to_bootstrap: 1.
Unmask and start:
systemctl unmask mariadb
galera_new_cluster

4. Verify Mysql is running on the Node
mysql -u root -p -e "SHOW STATUS LIKE 'wsrep_cluster_size';"
Target Output: Value should be 1.

5. Now we need to bring other Node back into the cluster. Since we "masked" it earlier to stop the restart loop, we must unmask it first.
systemctl unmask mariadb
systemctl start mariadb
SHOW STATUS LIKE 'wsrep_cluster_size';
Target Output: Value should be 2.

6, Enable Autostart: If you disabled the services earlier, re-enable them so they start on reboot:
systemctl enable mariadb

CSC Cloudstack Mariadb Galera Cluster Corruption issue

2025-12-04T01:04:38Z

Biswajit: Created page with "category:CSC Category:Cloudstack Issue : The Mariadb Galera Cluster Got Stuck , Data Corruption and Cloudstack Failed Diagnosis and Solution Process 1. Stop the M..."

Zimbra-OSS-10.1-How-to-Use-S3-compatible-object-Store-as-Mailbox-Store

2025-11-18T04:45:26Z

Biswajit:

[[category:Zimbra]]

== Zimbra 10.1 FOSS: Using S3-Compatible Storage ==

[[Step-by-Step Guide: Using JuiceFS with Zimbra FOSS]]

'''Os Platform tested on is Rocky 9.6 '''

This guide assumes you want to move your /opt/zimbra/store directory to a JuiceFS mount backed by an S3-compatible service (like AWS S3, MinIO, or Wasabi).

CRITICAL: Perform a full backup of your Zimbra server before starting. Test this entire procedure in a staging environment first.
1. Prerequisites
Zimbra 10.1 FOSS Server: A running and configured server.
S3-Compatible Object Storage:
An endpoint URL (e.g., https://s3.us-east-1.amazonaws.com).
A bucket name (e.g., my-zimbra-store-bucket).
An Access Key and a Secret Key.
Metadata Database for JuiceFS: For production, a dedicated Redis or MySQL/MariaDB server is recommended. For this guide, we'll use Redis.
Root access to your Zimbra server.

2. Install and Configure JuiceFS

Install the JuiceFS Client Follow the official instructions for your Linux distribution from the JuiceFS GitHub page. A common method is:
bash

curl -sSL https://d.juicefs.com/install | sh -

Install the Redis Client (if using Redis)
bash

# For Ubuntu/Debian
sudo apt-get update && sudo apt-get install redis-tools -y

# For CentOS/RHEL
sudo yum install redis -y

Redis Config File

[root@mail ~]# cat /etc/redis/redis.conf
bind 127.0.0.1 -::1
port 6379
daemonize yes
protected-mode yes
maxmemory 256mb
maxmemory-policy allkeys-lru
tcp-keepalive 300
loglevel notice
logfile /var/log/redis/redis.log
requirepass YOUR_VERY_STRONG_REDIS_PASSWORD
dir /var/lib/redis
# The filename where to dump the DB
dbfilename dump.rdb
# The filename for the AOF file
appendfilename "appendonly.aof"
# Enable AOF persistence
appendonly yes
appendfsync everysec
# RDB snapshots
save 900 1
save 300 10
save 60 10000
# Allow writes even if bgsave fails (unblock temporarily)
stop-writes-on-bgsave-error no

Ensure /etc/fuse.conf has:

user_allow_other

Format the JuiceFS Filesystem This command initializes the JuiceFS volume. It tells JuiceFS how to connect to your metadata database (Redis) and your data storage (S3). It only needs to be run once.

Replace the placeholders with your actual details.
bash

juicefs format \
--storage s3 \
--bucket https://del1.vultrobjects.com/zimbra-store-bucket \
--access-key Access_key \
--secret-key YOUR_VULTR_SECRET_KEY \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
zimbra-vultr-store

--storage s3: Specifies the object storage type.
--bucket: The full endpoint and bucket name.
"redis://...": Your Redis connection string. The /1 at the end specifies Redis database #1.
zimbra-vultr-store: The name you are giving to this new volume.

3. Mount the JuiceFS Filesystem

Create a Mount Point We will mount the new filesystem to a temporary location first.
bash

# Create a directory for the JuiceFS mount
sudo mkdir /mnt/zimbra_vultr

# Create a directory on a fast local disk (SSD recommended) for the cache
sudo mkdir /var/jfsCache

Mount the Filesystem
bash

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

-d: Run in the background (daemonize).
--cache-dir: A path on a local, fast disk (SSD is ideal) for caching. This is critical for performance.
--cache-size: Cache size in MiB. Here, it's 10GB. Adjust based on your available disk space.

Verify the Mount Run df -h. You should see /mnt/zimbra_vultr listed.

4. Migrate Zimbra Data

Schedule a maintenance window for these steps. Zimbra services must be stopped.

Stop Zimbra Services
bash

su - zimbra -c "zmcontrol stop"

Wait for all services to report "Stopped."

Copy the Data Use rsync to preserve permissions and ownership. This will take a long time depending on the size of your store.
bash

sudo rsync -avp /opt/zimbra/store/ /mnt/zimbra_vultr

Prepare the Original Store Directory Once the copy is complete and verified, move the original directory out of the way. Do not delete it yet!
bash

sudo mv /opt/zimbra/store /opt/zimbra/store_local_backup

Create the New Mount Point and Bind Mount Now, create an empty store directory and bind mount our JuiceFS location to it. A bind mount makes the contents of one directory appear in another.
bash

sudo mkdir /opt/zimbra/store
# Bind mount our JuiceFS directory over the new empty one
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
Set Final Permissions Ensure the zimbra user owns the new mount point.
bash

sudo chown zimbra:zimbra /opt/zimbra/store

5. Start Zimbra and Test

Start Zimbra Services
bash

su - zimbra -c "zmcontrol start"

Monitor Logs Closely watch the logs for any I/O errors or strange behavior.
bash

tail -f /opt/zimbra/log/mailbox.log

Test Vigorously
Send and receive emails, especially with large attachments.
Log in as a user and browse through old emails.
Check that search indexing is working.
Monitor the server's CPU, memory, and I/O wait times.

== Ensure The Reboot is taken care ==

Put following in /etc/rc.local

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

# Bind mount
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
sleep 30
/etc/init.d/zimbra start

Zimbra-OSS-10.1-How-to-Use-S3-compatible-object-Store-as-Mailbox-Store

2025-11-18T01:41:08Z

Biswajit:

[[category:Zimbra]]

== Zimbra 10.1 FOSS: Using S3-Compatible Storage ==

[[Step-by-Step Guide: Using JuiceFS with Zimbra FOSS]]

'''Os Platform tested on is Rocky 9.6 '''

This guide assumes you want to move your /opt/zimbra/store directory to a JuiceFS mount backed by an S3-compatible service (like AWS S3, MinIO, or Wasabi).

CRITICAL: Perform a full backup of your Zimbra server before starting. Test this entire procedure in a staging environment first.
1. Prerequisites
Zimbra 10.1 FOSS Server: A running and configured server.
S3-Compatible Object Storage:
An endpoint URL (e.g., https://s3.us-east-1.amazonaws.com).
A bucket name (e.g., my-zimbra-store-bucket).
An Access Key and a Secret Key.
Metadata Database for JuiceFS: For production, a dedicated Redis or MySQL/MariaDB server is recommended. For this guide, we'll use Redis.
Root access to your Zimbra server.

2. Install and Configure JuiceFS

Install the JuiceFS Client Follow the official instructions for your Linux distribution from the JuiceFS GitHub page. A common method is:
bash

curl -sSL https://d.juicefs.com/install | sh -

Install the Redis Client (if using Redis)
bash

# For Ubuntu/Debian
sudo apt-get update && sudo apt-get install redis-tools -y

# For CentOS/RHEL
sudo yum install redis -y

Redis Config File

[root@mail ~]# cat /etc/redis/redis.conf
bind 127.0.0.1 -::1
port 6379
daemonize yes
protected-mode yes
maxmemory 256mb
maxmemory-policy allkeys-lru
tcp-keepalive 300
loglevel notice
logfile /var/log/redis/redis.log
requirepass YOUR_VERY_STRONG_REDIS_PASSWORD
dir /var/lib/redis
# The filename where to dump the DB
dbfilename dump.rdb
# The filename for the AOF file
appendfilename "appendonly.aof"
# Enable AOF persistence
appendonly yes
appendfsync everysec
# RDB snapshots
save 900 1
save 300 10
save 60 10000
# Allow writes even if bgsave fails (unblock temporarily)
stop-writes-on-bgsave-error no

Ensure /etc/fuse.conf has:

user_allow_other

Format the JuiceFS Filesystem This command initializes the JuiceFS volume. It tells JuiceFS how to connect to your metadata database (Redis) and your data storage (S3). It only needs to be run once.

Replace the placeholders with your actual details.
bash

juicefs format \
--storage s3 \
--bucket https://del1.vultrobjects.com/zimbra-store-bucket \
--access-key Access_key \
--secret-key YOUR_VULTR_SECRET_KEY \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
zimbra-vultr-store

--storage s3: Specifies the object storage type.
--bucket: The full endpoint and bucket name.
"redis://...": Your Redis connection string. The /1 at the end specifies Redis database #1.
zimbra-vultr-store: The name you are giving to this new volume.

3. Mount the JuiceFS Filesystem

Create a Mount Point We will mount the new filesystem to a temporary location first.
bash

# Create a directory for the JuiceFS mount
sudo mkdir /mnt/zimbra_vultr

# Create a directory on a fast local disk (SSD recommended) for the cache
sudo mkdir /var/jfsCache

Mount the Filesystem
bash

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

-d: Run in the background (daemonize).
--cache-dir: A path on a local, fast disk (SSD is ideal) for caching. This is critical for performance.
--cache-size: Cache size in MiB. Here, it's 10GB. Adjust based on your available disk space.

Verify the Mount Run df -h. You should see /mnt/jfs_store listed.

4. Migrate Zimbra Data

Schedule a maintenance window for these steps. Zimbra services must be stopped.

Stop Zimbra Services
bash

su - zimbra -c "zmcontrol stop"

Wait for all services to report "Stopped."

Copy the Data Use rsync to preserve permissions and ownership. This will take a long time depending on the size of your store.
bash

sudo rsync -avp /opt/zimbra/store/ /mnt/jfs_store/

Prepare the Original Store Directory Once the copy is complete and verified, move the original directory out of the way. Do not delete it yet!
bash

sudo mv /opt/zimbra/store /opt/zimbra/store_local_backup

Create the New Mount Point and Bind Mount Now, create an empty store directory and bind mount our JuiceFS location to it. A bind mount makes the contents of one directory appear in another.
bash

sudo mkdir /opt/zimbra/store
# Bind mount our JuiceFS directory over the new empty one
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
Set Final Permissions Ensure the zimbra user owns the new mount point.
bash

sudo chown zimbra:zimbra /opt/zimbra/store

5. Start Zimbra and Test

Start Zimbra Services
bash

su - zimbra -c "zmcontrol start"

Monitor Logs Closely watch the logs for any I/O errors or strange behavior.
bash

tail -f /opt/zimbra/log/mailbox.log

Test Vigorously
Send and receive emails, especially with large attachments.
Log in as a user and browse through old emails.
Check that search indexing is working.
Monitor the server's CPU, memory, and I/O wait times.

== Ensure The Reboot is taken care ==

Put following in /etc/rc.local

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

# Bind mount
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
sleep 30
/etc/init.d/zimbra start

Zimbra-OSS-10.1-How-to-Use-S3-compatible-object-Store-as-Mailbox-Store

2025-11-18T01:40:50Z

Biswajit:

[[category:Zimbra]]

== Zimbra 10.1 FOSS: Using S3-Compatible Storage ==

[[Step-by-Step Guide: Using JuiceFS with Zimbra FOSS]]

'''Os Platform tested on is Rocky 9.6 '''
This guide assumes you want to move your /opt/zimbra/store directory to a JuiceFS mount backed by an S3-compatible service (like AWS S3, MinIO, or Wasabi).

CRITICAL: Perform a full backup of your Zimbra server before starting. Test this entire procedure in a staging environment first.
1. Prerequisites
Zimbra 10.1 FOSS Server: A running and configured server.
S3-Compatible Object Storage:
An endpoint URL (e.g., https://s3.us-east-1.amazonaws.com).
A bucket name (e.g., my-zimbra-store-bucket).
An Access Key and a Secret Key.
Metadata Database for JuiceFS: For production, a dedicated Redis or MySQL/MariaDB server is recommended. For this guide, we'll use Redis.
Root access to your Zimbra server.

2. Install and Configure JuiceFS

Install the JuiceFS Client Follow the official instructions for your Linux distribution from the JuiceFS GitHub page. A common method is:
bash

curl -sSL https://d.juicefs.com/install | sh -

Install the Redis Client (if using Redis)
bash

# For Ubuntu/Debian
sudo apt-get update && sudo apt-get install redis-tools -y

# For CentOS/RHEL
sudo yum install redis -y

Redis Config File

[root@mail ~]# cat /etc/redis/redis.conf
bind 127.0.0.1 -::1
port 6379
daemonize yes
protected-mode yes
maxmemory 256mb
maxmemory-policy allkeys-lru
tcp-keepalive 300
loglevel notice
logfile /var/log/redis/redis.log
requirepass YOUR_VERY_STRONG_REDIS_PASSWORD
dir /var/lib/redis
# The filename where to dump the DB
dbfilename dump.rdb
# The filename for the AOF file
appendfilename "appendonly.aof"
# Enable AOF persistence
appendonly yes
appendfsync everysec
# RDB snapshots
save 900 1
save 300 10
save 60 10000
# Allow writes even if bgsave fails (unblock temporarily)
stop-writes-on-bgsave-error no

Ensure /etc/fuse.conf has:

user_allow_other

Format the JuiceFS Filesystem This command initializes the JuiceFS volume. It tells JuiceFS how to connect to your metadata database (Redis) and your data storage (S3). It only needs to be run once.

Replace the placeholders with your actual details.
bash

juicefs format \
--storage s3 \
--bucket https://del1.vultrobjects.com/zimbra-store-bucket \
--access-key Access_key \
--secret-key YOUR_VULTR_SECRET_KEY \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
zimbra-vultr-store

--storage s3: Specifies the object storage type.
--bucket: The full endpoint and bucket name.
"redis://...": Your Redis connection string. The /1 at the end specifies Redis database #1.
zimbra-vultr-store: The name you are giving to this new volume.

3. Mount the JuiceFS Filesystem

Create a Mount Point We will mount the new filesystem to a temporary location first.
bash

# Create a directory for the JuiceFS mount
sudo mkdir /mnt/zimbra_vultr

# Create a directory on a fast local disk (SSD recommended) for the cache
sudo mkdir /var/jfsCache

Mount the Filesystem
bash

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

-d: Run in the background (daemonize).
--cache-dir: A path on a local, fast disk (SSD is ideal) for caching. This is critical for performance.
--cache-size: Cache size in MiB. Here, it's 10GB. Adjust based on your available disk space.

Verify the Mount Run df -h. You should see /mnt/jfs_store listed.

4. Migrate Zimbra Data

Schedule a maintenance window for these steps. Zimbra services must be stopped.

Stop Zimbra Services
bash

su - zimbra -c "zmcontrol stop"

Wait for all services to report "Stopped."

Copy the Data Use rsync to preserve permissions and ownership. This will take a long time depending on the size of your store.
bash

sudo rsync -avp /opt/zimbra/store/ /mnt/jfs_store/

Prepare the Original Store Directory Once the copy is complete and verified, move the original directory out of the way. Do not delete it yet!
bash

sudo mv /opt/zimbra/store /opt/zimbra/store_local_backup

Create the New Mount Point and Bind Mount Now, create an empty store directory and bind mount our JuiceFS location to it. A bind mount makes the contents of one directory appear in another.
bash

sudo mkdir /opt/zimbra/store
# Bind mount our JuiceFS directory over the new empty one
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
Set Final Permissions Ensure the zimbra user owns the new mount point.
bash

sudo chown zimbra:zimbra /opt/zimbra/store

5. Start Zimbra and Test

Start Zimbra Services
bash

su - zimbra -c "zmcontrol start"

Monitor Logs Closely watch the logs for any I/O errors or strange behavior.
bash

tail -f /opt/zimbra/log/mailbox.log

Test Vigorously
Send and receive emails, especially with large attachments.
Log in as a user and browse through old emails.
Check that search indexing is working.
Monitor the server's CPU, memory, and I/O wait times.

== Ensure The Reboot is taken care ==

Put following in /etc/rc.local

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

# Bind mount
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
sleep 30
/etc/init.d/zimbra start

Zimbra-OSS-10.1-How-to-Use-S3-compatible-object-Store-as-Mailbox-Store

2025-11-18T01:39:21Z

Biswajit:

[[category:Zimbra]]

== Zimbra 10.1 FOSS: Using S3-Compatible Storage ==

[[Step-by-Step Guide: Using JuiceFS with Zimbra FOSS]]
This guide assumes you want to move your /opt/zimbra/store directory to a JuiceFS mount backed by an S3-compatible service (like AWS S3, MinIO, or Wasabi).

CRITICAL: Perform a full backup of your Zimbra server before starting. Test this entire procedure in a staging environment first.
1. Prerequisites
Zimbra 10.1 FOSS Server: A running and configured server.
S3-Compatible Object Storage:
An endpoint URL (e.g., https://s3.us-east-1.amazonaws.com).
A bucket name (e.g., my-zimbra-store-bucket).
An Access Key and a Secret Key.
Metadata Database for JuiceFS: For production, a dedicated Redis or MySQL/MariaDB server is recommended. For this guide, we'll use Redis.
Root access to your Zimbra server.

2. Install and Configure JuiceFS

Install the JuiceFS Client Follow the official instructions for your Linux distribution from the JuiceFS GitHub page. A common method is:
bash

curl -sSL https://d.juicefs.com/install | sh -

Install the Redis Client (if using Redis)
bash

# For Ubuntu/Debian
sudo apt-get update && sudo apt-get install redis-tools -y

# For CentOS/RHEL
sudo yum install redis -y

Redis Config File

[root@mail ~]# cat /etc/redis/redis.conf
bind 127.0.0.1 -::1
port 6379
daemonize yes
protected-mode yes
maxmemory 256mb
maxmemory-policy allkeys-lru
tcp-keepalive 300
loglevel notice
logfile /var/log/redis/redis.log
requirepass YOUR_VERY_STRONG_REDIS_PASSWORD
dir /var/lib/redis
# The filename where to dump the DB
dbfilename dump.rdb
# The filename for the AOF file
appendfilename "appendonly.aof"
# Enable AOF persistence
appendonly yes
appendfsync everysec
# RDB snapshots
save 900 1
save 300 10
save 60 10000
# Allow writes even if bgsave fails (unblock temporarily)
stop-writes-on-bgsave-error no

Ensure /etc/fuse.conf has:

user_allow_other

Format the JuiceFS Filesystem This command initializes the JuiceFS volume. It tells JuiceFS how to connect to your metadata database (Redis) and your data storage (S3). It only needs to be run once.

Replace the placeholders with your actual details.
bash

juicefs format \
--storage s3 \
--bucket https://del1.vultrobjects.com/zimbra-store-bucket \
--access-key Access_key \
--secret-key YOUR_VULTR_SECRET_KEY \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
zimbra-vultr-store

--storage s3: Specifies the object storage type.
--bucket: The full endpoint and bucket name.
"redis://...": Your Redis connection string. The /1 at the end specifies Redis database #1.
zimbra-vultr-store: The name you are giving to this new volume.

3. Mount the JuiceFS Filesystem

Create a Mount Point We will mount the new filesystem to a temporary location first.
bash

# Create a directory for the JuiceFS mount
sudo mkdir /mnt/zimbra_vultr

# Create a directory on a fast local disk (SSD recommended) for the cache
sudo mkdir /var/jfsCache

Mount the Filesystem
bash

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

-d: Run in the background (daemonize).
--cache-dir: A path on a local, fast disk (SSD is ideal) for caching. This is critical for performance.
--cache-size: Cache size in MiB. Here, it's 10GB. Adjust based on your available disk space.

Verify the Mount Run df -h. You should see /mnt/jfs_store listed.

4. Migrate Zimbra Data

Schedule a maintenance window for these steps. Zimbra services must be stopped.

Stop Zimbra Services
bash

su - zimbra -c "zmcontrol stop"

Wait for all services to report "Stopped."

Copy the Data Use rsync to preserve permissions and ownership. This will take a long time depending on the size of your store.
bash

sudo rsync -avp /opt/zimbra/store/ /mnt/jfs_store/

Prepare the Original Store Directory Once the copy is complete and verified, move the original directory out of the way. Do not delete it yet!
bash

sudo mv /opt/zimbra/store /opt/zimbra/store_local_backup

Create the New Mount Point and Bind Mount Now, create an empty store directory and bind mount our JuiceFS location to it. A bind mount makes the contents of one directory appear in another.
bash

sudo mkdir /opt/zimbra/store
# Bind mount our JuiceFS directory over the new empty one
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
Set Final Permissions Ensure the zimbra user owns the new mount point.
bash

sudo chown zimbra:zimbra /opt/zimbra/store

5. Start Zimbra and Test

Start Zimbra Services
bash

su - zimbra -c "zmcontrol start"

Monitor Logs Closely watch the logs for any I/O errors or strange behavior.
bash

tail -f /opt/zimbra/log/mailbox.log

Test Vigorously
Send and receive emails, especially with large attachments.
Log in as a user and browse through old emails.
Check that search indexing is working.
Monitor the server's CPU, memory, and I/O wait times.

== Ensure The Reboot is taken care ==

Put following in /etc/rc.local

juicefs mount -d \
--cache-dir /var/jfsCache \
--cache-size 10240 \
"redis://:YOUR_VERY_STRONG_REDIS_PASSWORD@127.0.0.1:6379/1" \
/mnt/zimbra_vultr \
-o allow_other

# Bind mount
sudo mount --bind /mnt/zimbra_vultr /opt/zimbra/store
sleep 30
/etc/init.d/zimbra start

Zimbra-OSS-10.1-How-to-Use-S3-compatible-object-Store-as-Mailbox-Store

2025-11-18T01:36:11Z

Biswajit: Created page with "category:Zimbra == Zimbra 10.1 FOSS: Using S3-Compatible Storage == Step-by-Step Guide: Using JuiceFS with Zimbra FOSS This guide assumes you want to move your /opt/..."

Zimbra-BSP-Business-only-Edition-Restrictions

2025-11-13T08:57:14Z

Biswajit: Created page with "Category:Zimbra link - https://wiki.zimbra.com/wiki/Create_a_COS_for_Standard,_Professional,_BusinessPlus_and_Business_licenses --------------------------------- Creat..."

[[Category:Zimbra]]

link - https://wiki.zimbra.com/wiki/Create_a_COS_for_Standard,_Professional,_BusinessPlus_and_Business_licenses

---------------------------------

Create business COS

zmprov cc Business zimbraFeatureMAPIConnectorEnabled FALSE zimbraFeatureMobileSyncEnabled FALSE zimbraArchiveEnabled FALSE zimbraFeatureConversationsEnabled FALSE zimbraFeatureTaggingEnabled FALSE zimbraAttachmentsIndexingEnabled FALSE zimbraFeatureViewInHtmlEnabled FALSE zimbraFeatureGroupCalendarEnabled FALSE zimbraFreebusyExchangeURL FALSE zimbraFeatureSharingEnabled FALSE zimbraFeatureTasksEnabled FALSE zimbraFeatureBriefcasesEnabled FALSE zimbraFeatureSMIMEEnabled FALSE zimbraFeatureVoiceEnabled FALSE zimbraFeatureManageZimlets FALSE zimbraFeatureCalendarEnabled FALSE zimbraFeatureGalEnabled TRUE

-----------------------------------

Set the default COS business

link - https://imanudin.net/2015/02/01/zimbra-tips-how-to-define-default-cos-for-a-domain/

-----------------------------------

Change admin account password

---------------------------------

Create a new admin user with limited privileges

For example -

1. zmprov ca administrator@isgecynr.com supp0rt@123 zimbraIsDelegatedAdminAccount TRUE zimbraAdminConsoleUIComponents COSListView zimbraAdminConsoleUIComponents accountListView zimbraAdminConsoleUIComponents downloadsView zimbraAdminConsoleUIComponents DLListView zimbraAdminConsoleUIComponents aliasListView zimbraAdminConsoleUIComponents resourceListView

2. zmprov grr global usr administrator@isgecynr.com adminLoginCalendarResourceAs

3. zmprov grr global usr administrator@isgecynr.com domainAdminZimletRights

4. zmprov grr domain isgecynr.com usr administrator@isgecynr.com domainAdminRights

5. zmprov grr domain isgecynr.com usr administrator@isgecynr.com domainAdminConsoleRights

6. zmprov grr domain isgecynr.com usr administrator@isgecynr.com adminConsoleAliasRights

7. zmprov grr domain isgecynr.com usr administrator@isgecynr.com countAlias

LDAP Implementation at Deshwal

2025-02-06T05:22:58Z

Biswajit:

Referance Link : https://www.server-world.info/en/note?os=CentOS_Stream_9&p=openldap&f=1

OS - Centos 9 Stream or RHEL 9

[[install from EPEL]]

dnf --enablerepo=epel -y install openldap-servers openldap-clients
systemctl enable --now slapd
systemctl restart slapd

[[Set OpenLDAP admin password. ]]

slappasswd
New password:
Re-enter new password:
{SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root]# vi chrootpw.ldif
# specify the password generated above for [olcRootPW] section
dn: olcDatabase={0}config,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root]# ldapadd -Y EXTERNAL -H ldapi:/// -f chrootpw.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={0}config,cn=config"

[[Import basic Schemas. ]]

[root]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/cosine.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=cosine,cn=schema,cn=config"

[root@dlp ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/nis.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=nis,cn=schema,cn=config"

[root@dlp ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/inetorgperson.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=inetorgperson,cn=schema,cn=config"

[[Set your domain name on LDAP DB]]
# generate directory manager's password

[root@dlp ~]# slappasswd
New password:
Re-enter new password:
{SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root@ldap ~]# vi chdomain.ldif
# replace to your own domain name for [dc=***,dc=***] section
# specify the password generated above for [olcRootPW] section

dn: olcDatabase={1}monitor,cn=config
changetype: modify
replace: olcAccess
olcAccess: {0}to * by dn.base="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth"
read by dn.base="cn=Manager,dc=bluemonk,dc=com" read by * none

dn: olcDatabase={2}mdb,cn=config
changetype: modify
replace: olcSuffix
olcSuffix: dc=bluemonk,dc=com

dn: olcDatabase={2}mdb,cn=config
changetype: modify
replace: olcRootDN
olcRootDN: cn=Manager,dc=bluemonk,dc=com

dn: olcDatabase={2}mdb,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}0eQj3z0tjTCkz4Elh4X61hlJ3lkqhS8V

dn: olcDatabase={2}mdb,cn=config
changetype: modify
add: olcAccess
olcAccess: {0}to attrs=userPassword,shadowLastChange by
dn="cn=Manager,dc=bluemonk,dc=com" write by anonymous auth by self write by * none
olcAccess: {1}to dn.base="" by * read
olcAccess: {2}to * by dn="cn=Manager,dc=bluemonk,dc=com" write by * read

[root@dlp ~]# ldapmodify -Y EXTERNAL -H ldapi:/// -f chdomain.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={1}monitor,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

[[Add Base OUs]]

[root@ldap ~]# vi base.ldif
dn: dc=bluemonk,dc=com
objectClass: top
objectClass: domain
dc: bluemonk

dn: ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: PROTAIGA GLOBAL

dn: ou=Bluemonk Ventures,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: Bluemonk Ventures

dn: ou=Deshwal,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: Deshwal

dn: ou=devit,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: devit

dn: ou=oxypc,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: oxypc

dn: ou=customers,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: customers

dn: cn=Manager,dc=bluemonk,dc=com
objectClass: organizationalRole
cn: Manager
description: LDAP Administrator

[root@ldap ~]# ldapadd -x -D cn=Manager,dc=bluemonk,dc=com -W -f base.ldif
Enter LDAP Password:
adding new entry "dc=bluemonk,dc=com"

adding new entry "ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com"

adding new entry "ou=Bluemonk Ventures,dc=bluemonk,dc=com"

adding new entry "ou=Deshwal,dc=bluemonk,dc=com"

adding new entry "ou=devit,dc=bluemonk,dc=com"

adding new entry "ou=oxypc,dc=bluemonk,dc=com"

adding new entry "ou=customers,dc=bluemonk,dc=com"

adding new entry "cn=Manager,dc=bluemonk,dc=com"

[[Add User with Right Attributes]]
[root@ldap ~]# vi user.ldif
dn: uid=jsmith,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
uid: jsmith
cn: John Smith
sn: Smith
employeeNumber: 1001
mail: jsmith@bluemonk.com
mobile: +1 555-123-4567
title: Software Engineer
departmentNumber: IT
l: New York
manager: uid=mbrown,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
userPassword: {SSHA}6eGKqoklEjwwi6HABhmbbY1OaBi39cIG

[root@ldap ~]# ldapadd -x -D cn=Manager,dc=bluemonk,dc=com -W -f user.ldif
Enter LDAP Password:
adding new entry "uid=jsmith,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com"

LDAP Implementation at Deshwal

2025-02-06T05:06:44Z

Biswajit:

Referance Link : https://www.server-world.info/en/note?os=CentOS_Stream_9&p=openldap&f=1

OS - Centos 9 Stream or RHEL 9

[[install from EPEL]]

dnf --enablerepo=epel -y install openldap-servers openldap-clients
systemctl enable --now slapd

[[Set OpenLDAP admin password. ]]

slappasswd
New password:
Re-enter new password:
{SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root]# vi chrootpw.ldif
# specify the password generated above for [olcRootPW] section
dn: olcDatabase={0}config,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root]# ldapadd -Y EXTERNAL -H ldapi:/// -f chrootpw.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={0}config,cn=config"

[[Import basic Schemas. ]]

[root]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/cosine.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=cosine,cn=schema,cn=config"

[root@dlp ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/nis.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=nis,cn=schema,cn=config"

[root@dlp ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/inetorgperson.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=inetorgperson,cn=schema,cn=config"

[[Set your domain name on LDAP DB]]
# generate directory manager's password

[root@dlp ~]# slappasswd
New password:
Re-enter new password:
{SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root@ldap ~]# vi chdomain.ldif
# replace to your own domain name for [dc=***,dc=***] section
# specify the password generated above for [olcRootPW] section

dn: olcDatabase={1}monitor,cn=config
changetype: modify
replace: olcAccess
olcAccess: {0}to * by dn.base="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth"
read by dn.base="cn=Manager,dc=bluemonk,dc=com" read by * none

dn: olcDatabase={2}mdb,cn=config
changetype: modify
replace: olcSuffix
olcSuffix: dc=bluemonk,dc=com

dn: olcDatabase={2}mdb,cn=config
changetype: modify
replace: olcRootDN
olcRootDN: cn=Manager,dc=bluemonk,dc=com

dn: olcDatabase={2}mdb,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}0eQj3z0tjTCkz4Elh4X61hlJ3lkqhS8V

dn: olcDatabase={2}mdb,cn=config
changetype: modify
add: olcAccess
olcAccess: {0}to attrs=userPassword,shadowLastChange by
dn="cn=Manager,dc=bluemonk,dc=com" write by anonymous auth by self write by * none
olcAccess: {1}to dn.base="" by * read
olcAccess: {2}to * by dn="cn=Manager,dc=bluemonk,dc=com" write by * read

[root@dlp ~]# ldapmodify -Y EXTERNAL -H ldapi:/// -f chdomain.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={1}monitor,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

[[Add Base OUs]]

[root@ldap ~]# vi base.ldif
dn: dc=bluemonk,dc=com
objectClass: top
objectClass: domain
dc: bluemonk

dn: ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: PROTAIGA GLOBAL

dn: ou=Bluemonk Ventures,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: Bluemonk Ventures

dn: ou=Deshwal,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: Deshwal

dn: ou=devit,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: devit

dn: ou=oxypc,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: oxypc

dn: ou=customers,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: customers

dn: cn=Manager,dc=bluemonk,dc=com
objectClass: organizationalRole
cn: Manager
description: LDAP Administrator

[root@ldap ~]# ldapadd -x -D cn=Manager,dc=bluemonk,dc=com -W -f base.ldif
Enter LDAP Password:
adding new entry "dc=bluemonk,dc=com"

adding new entry "ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com"

adding new entry "ou=Bluemonk Ventures,dc=bluemonk,dc=com"

adding new entry "ou=Deshwal,dc=bluemonk,dc=com"

adding new entry "ou=devit,dc=bluemonk,dc=com"

adding new entry "ou=oxypc,dc=bluemonk,dc=com"

adding new entry "ou=customers,dc=bluemonk,dc=com"

adding new entry "cn=Manager,dc=bluemonk,dc=com"

[[Add User with Right Attributes]]
[root@ldap ~]# vi user.ldif
dn: uid=jsmith,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
uid: jsmith
cn: John Smith
sn: Smith
employeeNumber: 1001
mail: jsmith@bluemonk.com
mobile: +1 555-123-4567
title: Software Engineer
departmentNumber: IT
l: New York
manager: uid=mbrown,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
userPassword: {SSHA}6eGKqoklEjwwi6HABhmbbY1OaBi39cIG

[root@ldap ~]# ldapadd -x -D cn=Manager,dc=bluemonk,dc=com -W -f user.ldif
Enter LDAP Password:
adding new entry "uid=jsmith,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com"

LDAP Implementation at Deshwal

2025-02-06T05:04:52Z

Biswajit:

Referance Link : https://www.server-world.info/en/note?os=CentOS_Stream_9&p=openldap&f=1

OS - Centos 9 Stream or RHEL 9

[[install from EPEL]]

dnf --enablerepo=epel -y install openldap-servers openldap-clients
systemctl enable --now slapd

[[Set OpenLDAP admin password. ]]

slappasswd
New password:
Re-enter new password:
{SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root]# vi chrootpw.ldif
# specify the password generated above for [olcRootPW] section
dn: olcDatabase={0}config,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root]# ldapadd -Y EXTERNAL -H ldapi:/// -f chrootpw.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={0}config,cn=config"

[[Import basic Schemas. ]]

[root]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/cosine.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=cosine,cn=schema,cn=config"

[root@dlp ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/nis.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=nis,cn=schema,cn=config"

[root@dlp ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/inetorgperson.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=inetorgperson,cn=schema,cn=config"

[[Set your domain name on LDAP DB]]
# generate directory manager's password

[root@dlp ~]# slappasswd
New password:
Re-enter new password:
{SSHA}xxxxxxxxxxxxxxxxxxxxxxxx

[root@ldap ~]# vi chdomain.ldif
# replace to your own domain name for [dc=***,dc=***] section
# specify the password generated above for [olcRootPW] section

dn: olcDatabase={1}monitor,cn=config
changetype: modify
replace: olcAccess
olcAccess: {0}to * by dn.base="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth"
read by dn.base="cn=Manager,dc=bluemonk,dc=com" read by * none

dn: olcDatabase={2}mdb,cn=config
changetype: modify
replace: olcSuffix
olcSuffix: dc=bluemonk,dc=com

dn: olcDatabase={2}mdb,cn=config
changetype: modify
replace: olcRootDN
olcRootDN: cn=Manager,dc=bluemonk,dc=com

dn: olcDatabase={2}mdb,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}0eQj3z0tjTCkz4Elh4X61hlJ3lkqhS8V

dn: olcDatabase={2}mdb,cn=config
changetype: modify
add: olcAccess
olcAccess: {0}to attrs=userPassword,shadowLastChange by
dn="cn=Manager,dc=bluemonk,dc=com" write by anonymous auth by self write by * none
olcAccess: {1}to dn.base="" by * read
olcAccess: {2}to * by dn="cn=Manager,dc=bluemonk,dc=com" write by * read

[root@dlp ~]# ldapmodify -Y EXTERNAL -H ldapi:/// -f chdomain.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={1}monitor,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

modifying entry "olcDatabase={2}mdb,cn=config"

[root@ldap ~]# vi base.ldif
dn: dc=bluemonk,dc=com
objectClass: top
objectClass: domain
dc: bluemonk

dn: ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: PROTAIGA GLOBAL

dn: ou=Bluemonk Ventures,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: Bluemonk Ventures

dn: ou=Deshwal,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: Deshwal

dn: ou=devit,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: devit

dn: ou=oxypc,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: oxypc

dn: ou=customers,dc=bluemonk,dc=com
objectClass: organizationalUnit
ou: customers

dn: cn=Manager,dc=bluemonk,dc=com
objectClass: organizationalRole
cn: Manager
description: LDAP Administrator

[root@ldap ~]# ldapadd -x -D cn=Manager,dc=bluemonk,dc=com -W -f base.ldif
Enter LDAP Password:
adding new entry "dc=bluemonk,dc=com"

adding new entry "ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com"

adding new entry "ou=Bluemonk Ventures,dc=bluemonk,dc=com"

adding new entry "ou=Deshwal,dc=bluemonk,dc=com"

adding new entry "ou=devit,dc=bluemonk,dc=com"

adding new entry "ou=oxypc,dc=bluemonk,dc=com"

adding new entry "ou=customers,dc=bluemonk,dc=com"

adding new entry "cn=Manager,dc=bluemonk,dc=com"

[root@ldap ~]# vi user.ldif
dn: uid=jsmith,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
uid: jsmith
cn: John Smith
sn: Smith
employeeNumber: 1001
mail: jsmith@bluemonk.com
mobile: +1 555-123-4567
title: Software Engineer
departmentNumber: IT
l: New York
manager: uid=mbrown,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com
userPassword: {SSHA}6eGKqoklEjwwi6HABhmbbY1OaBi39cIG

[root@ldap ~]# ldapadd -x -D cn=Manager,dc=bluemonk,dc=com -W -f user.ldif
Enter LDAP Password:
adding new entry "uid=jsmith,ou=PROTAIGA GLOBAL,dc=bluemonk,dc=com"

LDAP Implementation at Deshwal

2025-02-06T04:58:37Z

Biswajit:

LDAP Implementation at Deshwal

2025-02-06T04:57:10Z

Biswajit:

LDAP Implementation at Deshwal

2025-02-06T04:56:04Z

Biswajit:

LDAP Implementation at Deshwal

2025-02-06T04:50:43Z

Biswajit: Created page with "Referance Link : https://www.server-world.info/en/note?os=CentOS_Stream_9&p=openldap&f=1 OS - Centos 9 Stream or RHEL 9 install from EPEL dnf --enablerepo=epel -y ins..."

How to Implement Sender Restricted Groups on Qmail-LDAP

2024-05-02T07:29:32Z

Biswajit: Created page with "category:SHROFF'S CHARITY EYE HOSPITAL Media:How to Implement Sender Restricted Groups on Qmail-LDAP environment.txt"

[[category:SHROFF'S CHARITY EYE HOSPITAL]]

[[Media:How to Implement Sender Restricted Groups on Qmail-LDAP environment.txt]]

Category:O365

2024-05-02T07:24:15Z

Biswajit: Created page with "Category:Tetra Clients"

[[Category:Tetra Clients]]

Category:SHROFF'S CHARITY EYE HOSPITAL

2024-05-02T07:23:44Z

Biswajit: Created page with "Category:Tetra Clients"

[[Category:Tetra Clients]]

Shroff hospital partial hosting of Zimbra and O365

2024-05-02T07:18:36Z

Biswajit:

[[category:SHROFF'S CHARITY EYE HOSPITAL]]
[[category:O365]]

== O365 Hosting with Zimbra ==

Some Accounts got migrated from Zimbra to O365 Platform as split domain mail hosting concept

Document for the Same is at [[Media:SHROFF%27S_CHARITY_EYE_HOSPITAL--ZIMBRA_TO_M365_MIGRATION_DOCUMENT.pdf]]

Shroff hospital partial hosting of Zimbra and O365

2024-05-02T07:17:29Z

Biswajit: Created page with "category:SHROFF'S CHARITY EYE HOSPITAL category:O365 == O365 Hosting with Zimbra == Some Accounts got migrated from Zimbra to O365 Platform as split domain mail hos..."

[[category:SHROFF'S CHARITY EYE HOSPITAL]]
[[category:O365]]

== O365 Hosting with Zimbra ==

Some Accounts got migrated from Zimbra to O365 Platform as split domain mail hosting concept

Document for the Same is at [[File:SHROFF%27S_CHARITY_EYE_HOSPITAL--ZIMBRA_TO_M365_MIGRATION_DOCUMENT.pdf]]

Tips Trick on Creation managing wiki pages

2024-05-02T07:12:28Z

Biswajit: minor

[[category:How To]]

==Creation of New Wiki Page==

# On the URL of wiki type the Subject of the Document . for example if I want to create a page with Title "Tips Trick on Creation managing wiki pages" Then please have the URL as http://wiki.tetrain.com/wiki/index.php/Tips_Trick_on_Creation_managing_wiki_pages .
# This will prompt for editing this page . Please start editing .
# Fist on the Top , define the Category ( if you know ) , for example <nowiki>[[category:How To]]</nowiki> . The uppercase or lower case of the category needs to be same . If you are not sure about category , you can skip it .
# Now you can Either start writing or copy / paste the content and Save it

'''Your page is Ready and will be visible'''

but without any formating

=Formating Tips=

== Direct Formating ==

# Define category on the top by <nowiki>[[category:Category name]]</nowiki> e.g <nowiki>[[category:Tetra Clients]]</nowiki>
# Bold any text by putting <nowiki>'''</nowiki>at the begining and end of the text. Or the wiki editor also have these formatting like bold,italics ,big font, underline etc.
# Content of Index can easily by putting "==" or "=" at the begining and ending of Heading .
# put image by uloading the image and in the text mention <nowiki>"[[Image:Image_name]]"</nowiki> at the place you want the image .
# For more complecated formating refer to http://www.mediawiki.org/wiki/Help:Formatting

''' I find the Best way is to Open a any Formatted already Incorporated Page, and see what has been done , And just learn and follow '''

Let's Encrypt Certificate Issue deployment Issue at Pahwa

2024-01-20T17:40:16Z

Biswajit:

[[category:Zimbra]]

Issue Deployment of Let's Encrypt Certificate on pahwa and Modelama exports

curl https://get.acme.sh | sh
yum install socat
cd .acme.sh/
For Zimbra 8.6 and below ( Only in case of zimbra proxy is not running )

./acme.sh --issue --alpn -d mail21c.pahwa.com --pre-hook "su - zimbra -c 'zmmailboxdctl stop'" --post-hook "su - zimbra -c 'zmmailboxdctl start'"

for 8.7 and Above ( also in case of 8.6 where zimbra proxy is running )

./acme.sh --issue --alpn -d mail21c.pahwa.com --pre-hook "su - zimbra -c 'zmproxyctl stop'" --post-hook "su - zimbra -c 'zmproxyctl start'"

[[In case it does not work and give error "Error, can not get domain token entry mail21c.pahwa.com for tls-alpn-01" ]]

./acme.sh --issue --standalone -d mail21c.pahwa.com --server letsencrypt --pre-hook "su - zimbra -c 'zmmailboxdctl stop'" --post-hook "su - zimbra -c 'zmmailboxdctl start'"

'''In Case of Renewal , use --renew in place of --issue . You can use --renew --force also .'''

cd mail21c.pahwa.com/
cp mail21c.pahwa.com.cer mail21c.pahwa.com.key fullchain.cer /tmp
cd /tmp/

Delete fullchain.cer and create new fullchain.cer as shown below
-----BEGIN CERTIFICATE-----
MIIFazCCA1OgAwIBAgIRAIIQz7DSQONZRGPgu2OCiwAwDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMTUwNjA0MTEwNDM4
WhcNMzUwNjA0MTEwNDM4WjBPMQswCQYDVQQGEwJVUzEpMCcGA1UEChMgSW50ZXJu
ZXQgU2VjdXJpdHkgUmVzZWFyY2ggR3JvdXAxFTATBgNVBAMTDElTUkcgUm9vdCBY
MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAK3oJHP0FDfzm54rVygc
h77ct984kIxuPOZXoHj3dcKi/vVqbvYATyjb3miGbESTtrFj/RQSa78f0uoxmyF+
0TM8ukj13Xnfs7j/EvEhmkvBioZxaUpmZmyPfjxwv60pIgbz5MDmgK7iS4+3mX6U
A5/TR5d8mUgjU+g4rk8Kb4Mu0UlXjIB0ttov0DiNewNwIRt18jA8+o+u3dpjq+sW
T8KOEUt+zwvo/7V3LvSye0rgTBIlDHCNAymg4VMk7BPZ7hm/ELNKjD+Jo2FR3qyH
B5T0Y3HsLuJvW5iB4YlcNHlsdu87kGJ55tukmi8mxdAQ4Q7e2RCOFvu396j3x+UC
B5iPNgiV5+I3lg02dZ77DnKxHZu8A/lJBdiB3QW0KtZB6awBdpUKD9jf1b0SHzUv
KBds0pjBqAlkd25HN7rOrFleaJ1/ctaJxQZBKT5ZPt0m9STJEadao0xAH0ahmbWn
OlFuhjuefXKnEgV4We0+UXgVCwOPjdAvBbI+e0ocS3MFEvzG6uBQE3xDk3SzynTn
jh8BCNAw1FtxNrQHusEwMFxIt4I7mKZ9YIqioymCzLq9gwQbooMDQaHWBfEbwrbw
qHyGO0aoSCqI3Haadr8faqU9GY/rOPNk3sgrDQoo//fb4hVC1CLQJ13hef4Y53CI
rU7m2Ys6xt0nUW7/vGT1M0NPAgMBAAGjQjBAMA4GA1UdDwEB/wQEAwIBBjAPBgNV
HRMBAf8EBTADAQH/MB0GA1UdDgQWBBR5tFnme7bl5AFzgAiIyBpY9umbbjANBgkq
hkiG9w0BAQsFAAOCAgEAVR9YqbyyqFDQDLHYGmkgJykIrGF1XIpu+ILlaS/V9lZL
ubhzEFnTIZd+50xx+7LSYK05qAvqFyFWhfFQDlnrzuBZ6brJFe+GnY+EgPbk6ZGQ
3BebYhtF8GaV0nxvwuo77x/Py9auJ/GpsMiu/X1+mvoiBOv/2X/qkSsisRcOj/KK
NFtY2PwByVS5uCbMiogziUwthDyC3+6WVwW6LLv3xLfHTjuCvjHIInNzktHCgKQ5
ORAzI4JMPJ+GslWYHb4phowim57iaztXOoJwTdwJx4nLCgdNbOhdjsnvzqvHu7Ur
TkXWStAmzOVyyghqpZXjFaH3pO3JLF+l+/+sKAIuvtd7u+Nxe5AW0wdeRlN8NwdC
jNPElpzVmbUq4JUagEiuTDkHzsxHpFKVK7q4+63SM1N95R1NbdWhscdCb+ZAJzVc
oyi3B43njTOQ5yOf+1CceWxG1bQVs5ZufpsMljq4Ui0/1lvh+wjChP4kqKOJ2qxq
4RgqsahDYVvTH9w7jXbyLeiNdd8XM2w9U/t7y0Ff/9yi0GE44Za4rF2LN9d11TPA
mRGunUHBcnWEvgJBQl9nJEiU0Zsnvgc/ubhPgXRR4Xq37Z0j4r7g1SgEEzwxA57d
emyPxgcYxn/eR44/KJ4EBs+lVDR3veyJm+kXQ99b21/+jh5Xos1AnX5iItreGCc=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjAwOTA0MDAwMDAw
WhcNMjUwOTE1MTYwMDAwWjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCUjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7AhUozPaglNMPEuyNVZLD+ILxmaZ6QoinXSaqtSu5xUyxr45r+XXIo9cP
R5QUVTVXjJ6oojkZ9YI8QqlObvU7wy7bjcCwXPNZOOftz2nwWgsbvsCUJCWH+jdx
sxPnHKzhm+/b5DtFUkWWqcFTzjTIUu61ru2P3mBw4qVUq7ZtDpelQDRrK9O8Zutm
NHz6a4uPVymZ+DAXXbpyb/uBxa3Shlg9F8fnCbvxK/eG3MHacV3URuPMrSXBiLxg
Z3Vms/EY96Jc5lP/Ooi2R6X/ExjqmAl3P51T+c8B5fWmcBcUr2Ok/5mzk53cU6cG
/kiFHaFpriV1uxPMUgP17VGhi9sVAgMBAAGjggEIMIIBBDAOBgNVHQ8BAf8EBAMC
AYYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMBIGA1UdEwEB/wQIMAYB
Af8CAQAwHQYDVR0OBBYEFBQusxe3WFbLrlAJQOYfr52LFMLGMB8GA1UdIwQYMBaA
FHm0WeZ7tuXkAXOACIjIGlj26ZtuMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcw
AoYWaHR0cDovL3gxLmkubGVuY3Iub3JnLzAnBgNVHR8EIDAeMBygGqAYhhZodHRw
Oi8veDEuYy5sZW5jci5vcmcvMCIGA1UdIAQbMBkwCAYGZ4EMAQIBMA0GCysGAQQB
gt8TAQEBMA0GCSqGSIb3DQEBCwUAA4ICAQCFyk5HPqP3hUSFvNVneLKYY611TR6W
PTNlclQtgaDqw+34IL9fzLdwALduO/ZelN7kIJ+m74uyA+eitRY8kc607TkC53wl
ikfmZW4/RvTZ8M6UK+5UzhK8jCdLuMGYL6KvzXGRSgi3yLgjewQtCPkIVz6D2QQz
CkcheAmCJ8MqyJu5zlzyZMjAvnnAT45tRAxekrsu94sQ4egdRCnbWSDtY7kh+BIm
lJNXoB1lBMEKIq4QDUOXoRgffuDghje1WrG9ML+Hbisq/yFOGwXD9RiX8F6sw6W4
avAuvDszue5L3sz85K+EC4Y/wFVDNvZo4TYXao6Z0f+lQKc0t8DQYzk1OXVu8rp2
yJMC6alLbBfODALZvYH7n7do1AZls4I9d1P4jnkDrQoxB3UqQ9hVl3LEKQ73xF1O
yK5GhDDX8oVfGKF5u+decIsH4YaTw7mP3GFxJSqv3+0lUFJoi5Lc5da149p90Ids
hCExroL1+7mryIkXPeFM5TgO9r0rvZaBFOvV2z0gp35Z0+L4WPlbuEjN/lxPFin+
HlUjr8gRsI3qfJOQFy/9rKIJR0Y/8Omwt/8oTWgy1mdeHmmjk7j1nYsvC9JSQ6Zv
MldlTTKB3zhThV1+XWYp6rjd5JW1zbVWEkLNxE7GJThEUG3szgBVGP7pSWTUTsqX
nLRbwHOoq7hHwg==
-----END CERTIFICATE-----

Verify the Certificate

/opt/zimbra/bin/zmcertmgr verifycrt comm mail21c.pahwa.com.key mail21c.pahwa.com.cer fullchain.cer

Copy the SSL Files

cp -a /opt/zimbra/ssl/zimbra /opt/zimbra/ssl/zimbra.$(date "+%Y%m%d")

Copy the Key

cp mail21c.pahwa.com.key /opt/zimbra/ssl/zimbra/commercial/commercial.key

Deploy the Certificate

/opt/zimbra/bin/zmcertmgr deploycrt comm mail21c.pahwa.com.cer fullchain.cer

Restart Zimbra

su - zimbra
zmcontrol restart

Let's Encrypt Certificate Issue deployment Issue at Pahwa

2024-01-20T17:31:28Z

Biswajit:

MediaWiki:Createaccount-text

2022-08-05T10:37:27Z

Biswajit:

Biswajit has created an account for your e-mail address on {{SITENAME}} ($4) named "$2", with password "$3".
You should log in and change your password now.

You may ignore this message, if this account was created in error.

Please do not share this above information to any one including your colleges too
The URL which can be used are

http://wiki.tetrain.com/wiki

Nagios Upgrade Process with PCS cluster

2022-05-08T02:29:36Z

Biswajit: Created page with "category:Spectranet https://youtu.be/lWkX0EPfvho ==Nagios Upgrade Process with PCS cluster Dated 7th May 2022 - Tetra Support Staff - Biswajit Banerjee== <HTML5video ty..."

[[category:Spectranet]]

https://youtu.be/lWkX0EPfvho

==Nagios Upgrade Process with PCS cluster Dated 7th May 2022 - Tetra Support Staff - Biswajit Banerjee==

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

Category:Training

2022-02-26T13:07:00Z

Biswajit:

[[category:Tetra Clients]]

Category:Training

2022-02-26T13:06:30Z

Biswajit: Created page with "category:Tetra Client"

[[category:Tetra Client]]

Category:ISONBPO

2022-02-26T12:50:45Z

Biswajit: Created page with "category:Tetra Clients"

[[category:Tetra Clients]]

Nextcloud Issue where folder was copied from backup but not reflecting on nextcloud UI

2022-02-25T14:22:48Z

Biswajit: Created page with "category:ISGEC '''ISSUE :''' Customer has lost the folder accidentally having huge amount of files . The folder was restored from backup but it was not visible on Nextclo..."

[[category:ISGEC]]

'''ISSUE :''' Customer has lost the folder accidentally having huge amount of files . The folder was restored from backup but it was not visible on Nextcloud web console .

'''[[Solution]]'''

Referance URL : https://medium.com/code-enigma/adding-files-to-nextcloud-using-the-command-line-9fe0074b843a

sudo -u apache /usr/bin/php /var/www/html/nextcloud/occ files:scan --path="/admin/files"

Using Nextcloud CLI the files of the concerning user ( admin in our case ) was scanned , Solved the issue

Mail migration from send mail to Qmail prime-pci

2022-02-19T06:33:00Z

Biswajit:

[[category:Prime PCI]]
[[category:Qmail]]

'''[[****The is an OLD Document can be only used for technical Referance , This might not be Valid , Needs to be used with Caution ****]]'''

Price-pci wanted transferred sent item of sendmail server to qmail server.

Download the Mailbox to Maildir script from http://batleth.sapienti-sat.org/projects/mb2md/ and satisfy its dependency .

This has been done as below

First mount sendmail home directory to qmail server with nfs with proper permission and ownership

/mb2md-3.20.pl -s /mnthome/rajendrababu/ -R -d /home/vmail/prime-pci.com/rajendrababu/Maildir/

After this there will be created some extra folders in webmail (inbox sentitem etc.)

Right now it is downloaded at /root/mailbox_to_maildir/mb2md-3.20.pl location in Qmail server

Mail migration from send mail to Qmail prime-pci

2022-02-19T06:32:25Z

Biswajit:

[[category:Prime PCI]]
[[category:Qmail]]

'''[[The is an OLD Document can be only used for technical Referance , This might not be Valid , Needs to be used with Caution ]]'''

Price-pci wanted transferred sent item of sendmail server to qmail server.

Download the Mailbox to Maildir script from http://batleth.sapienti-sat.org/projects/mb2md/ and satisfy its dependency .

This has been done as below

First mount sendmail home directory to qmail server with nfs with proper permission and ownership

/mb2md-3.20.pl -s /mnthome/rajendrababu/ -R -d /home/vmail/prime-pci.com/rajendrababu/Maildir/

After this there will be created some extra folders in webmail (inbox sentitem etc.)

Right now it is downloaded at /root/mailbox_to_maildir/mb2md-3.20.pl location in Qmail server

Mail migration from send mail to Qmail prime-pci

2022-02-19T06:31:00Z

Biswajit:

[[category:Prime PCI]]
[[category:Qmail]]

'''The is an OLD Document can be only used for technical Referance , This might not be Valid , Needs to be used with Caution '''

Price-pci wanted transferred sent item of sendmail server to qmail server.

Download the Mailbox to Maildir script from http://batleth.sapienti-sat.org/projects/mb2md/ and satisfy its dependency .

This has been done as below

First mount sendmail home directory to qmail server with nfs with proper permission and ownership

/mb2md-3.20.pl -s /mnthome/rajendrababu/ -R -d /home/vmail/prime-pci.com/rajendrababu/Maildir/

After this there will be created some extra folders in webmail (inbox sentitem etc.)

Right now it is downloaded at /root/mailbox_to_maildir/mb2md-3.20.pl location in Qmail server

How To Block Encrypted Archives In Zimbra alpha(Natiion Today)

2022-02-19T06:24:41Z

Biswajit:

[[category:NEWSNATION]]
[[category:Zimbra]]

== ISSUE ==

Mail was not delivered and it was flagged as virus, Due to pdf attached with it.

'''By default Zimbra will block encrypted archives such as ZIP or PDF that cannot be scanned. You can disable this function from the Global Settings.
'''

== Solution ==

Block encrypted archives from GUI

You can disable this function from the Global Settings by unchecking Block encrypted archives from the AS/AV tab.

[[File:block-encrypted-archives.png]]

Block encrypted archives from command line

vi /opt/zimbra/clamav-0.97.5/etc/clamd.conf

In this file you can set ArchiveBlockEncrypted to NO or comment it out because NO is the default value

# Mark encrypted archives as viruses (Encrypted.Zip, Encrypted.RAR).
# Default: no
# ArchiveBlockEncrypted no

Alpha Client's Zimbra Architecture

2022-02-19T06:23:55Z

Biswajit:

[[category:NEWSNATION]]

[[Image:IMG 7638.jpeg]]

Multiple IP for Single Host on Nagios done for Spectranet

2022-02-15T08:03:17Z

Biswajit:

[[category:Spectranet]]
[[category:Nagios]]

== Objective : ==
As of now, we have scenario in which 2 different ISP with 2 different IP are connected in single device. We have no measure to configure loopback or management IP. In that situation we only monitoring via public IP.

# From monitoring prospective it is very challanging if we add single ip and in service 2 interface doesn’t mean if one interface or ISP1 gets down.
# Also if we add same device with different name then for same probe we have multiple alarm.

[[Image:Image001-spectra.png]]

== Solution ==

Download check_muliaddr.pl from https://exchange.nagios.org/directory/Plugins/Others/check_multiaddr/details

And Deploy to NagiosXI Server and Attached '''pollers''' in ''/usr/local/nagios/libexec directory''

Also do chown to nagios and chmod to 755

== Basic Testing ==

Our testing Host is '''BGL-MWIFI-STANZA-9078408-DENVR-BNGINV00S3_001''' and IP are '''119.82.126.244,103.5.132.187'''
cd /usr/local/nagios/libexec
./check_multiaddr.pl ./check_ping -H 119.82.126.244,103.5.132.187 -w 800.0,20% -c 999.0,60% -p 5
Should have proper output

== Deployment Process ==

Now with Nagios XI admin Panel

- create Command via CCM
'''example''' check_xi_service_ifoperstatus_multiaddr ( copy check_xi_service_ifoperstatus) and change command to
original Command
$USER1$/check_ifoperstatus -H $HOSTADDRESS$ -C $ARG1$ -k $ARG2$ $ARG3$
to
'''$USER1$/check_multiaddr.pl''' $USER1$/check_ifoperstatus -H $HOSTADDRESS$ -C $ARG1$ -k $ARG2$ $ARG3$

'''example''' check-host-alive_multiaddr ( copy check-host-alive) and change command to
'''$USER1$/check_multiaddr.pl''' $USER1$/check_icmp -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 5

[[Image:Screenshot_from_2019-11-26_20-00-52.png]]

Via CCM Choose Host --> add both IP 119.82.126.244,103.5.132.187 on IP Address and Save .

On All Services create Service Command like check_xi_service_ifoperstatus_multiaddr or check-host-alive_multiaddr and Apply to the Services .

Once you have Applied the configuration , you are online
[[Image:Screenshot_from_2019-11-26_15-00-56.png]]

TR69 Nagios Custom API Deployment For Spectra

2022-02-15T08:02:20Z

Biswajit:

[[category:Nagios]]
[[category:Spectranet]]

==TR69 Device addition NagiosXi Spectra 2022 02 14 11 16 00. Dated 14 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

<HTML5video type="youtube" width="640" height="480" autoplay="false">dYXGu-5k35c</HTML5video>

Category:AIMIL

2022-02-11T14:32:16Z

Biswajit:

[[:Category:Tetra Clients]]

'''[[All documents are OLD , Kept only for Reference ]]'''

ISGEC Issue of user not able to login

2022-02-05T13:27:14Z

Biswajit: Created page with "category:ISGEC category:Zimbra ==ISGEC issue of user not able to login in Zimbra . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee== <HTML5video type="yo..."

[[category:ISGEC]]
[[category:Zimbra]]

==ISGEC issue of user not able to login in Zimbra . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

<HTML5video type="youtube" width="640" height="480" autoplay="false">P42mTIX-QuE</HTML5video>

Category:ISGEC

2022-02-05T13:25:12Z

Biswajit:

[[category:Tetra Clients]]
[[category:Zimbra]]

Newsnation Saturday Zimbra Backup Process

2022-02-05T11:01:35Z

Biswajit: Created page with "category:NEWSNATION category:Zimbra ==NewsNation Every Saturday Mail Backup Process As Discussed With Alok . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Baner..."

[[category:NEWSNATION]]
[[category:Zimbra]]

==NewsNation Every Saturday Mail Backup Process As Discussed With Alok . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

Training 2022 Linux team/

2022-02-05T11:00:55Z

Biswajit:

[[Category:Training_2022]]

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-1 . Dated 01 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-2 . Dated 02 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-3 . Dated 03 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

==Training on Mail Sending & Receving Problem & Bouncing Problem Part-4 . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

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

==ISGEC issue of user not able to login in Zimbra . Dated 05 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

<HTML5video type="youtube" width="640" height="480" autoplay="false">P42mTIX-QuE</HTML5video>

Allow blocked compressed format extensions for all users in zimbra

2022-02-05T10:58:45Z

Biswajit:

[[category:NEWSNATION]]

==Objective==
Allow blocked compressed format extensions for all users in zimbra for Newsnation

1. First log in to the zimbra admin penal and go to the globel setting then in Attachments option And check in the right side Box which Show “urrently blocked extensions by MTA”.

2. If there is showing extesion list then select zip, rar, 7zip and remove them. And then save the changes.

3. If the “Currently blocked extensions by MTA” is empty then login to the IP 115.112.117.163 and then login to zimbra server.

4. now open the given file
vi /opt/zimbra/postfix/conf/main.cf

in this file go to the last line in which you will find the following line
mime_header_checks = regexp:/opt/zimbra/conf/mime_header_checks

5. Now copy the file and open it.
Vim /opt/zimbra/conf/mime_header_checks

6. Now delete the extensions name like zip, rar, 7zip. And arrange the remaining with the same format as before.

7. After saving this file restart postfix service.

Tips Trick on Creation managing wiki pages

2022-02-02T10:34:53Z

Biswajit: /* Use Media Wiki Plugin with Libra Office */

[[category:How To]]

==Creation of New Wiki Page==

# On the URL of wiki type the Subject of the Document . for example if I want to create a page with Title "Tips Trick on Creation managing wiki pages" Then please have the URL as http://192.168.1.15/wiki/index.php/Tips_Trick_on_Creation_managing_wiki_pages .
# This will prompt for editing this page . Please start editing .
# Fist on the Top , define the Category ( if you know ) , for example <nowiki>[[category:How To]]</nowiki> . The uppercase or lower case of the category needs to be same . If you are not sure about category , you can skip it .
# Now you can Either start writing or copy / paste the content and Save it

'''Your page is Ready and will be visible'''

but without any formating

=Formating Tips=

== Direct Formating ==

# Define category on the top by <nowiki>[[category:Category name]]</nowiki> e.g <nowiki>[[category:Tetra Clients]]</nowiki>
# Bold any text by putting <nowiki>'''</nowiki>at the begining and end of the text. Or the wiki editor also have these formatting like bold,italics ,big font, underline etc.
# Content of Index can easily by putting "==" or "=" at the begining and ending of Heading .
# put image by uloading the image and in the text mention <nowiki>"[[Image:Image_name]]"</nowiki> at the place you want the image .
# For more complecated formating refer to http://www.mediawiki.org/wiki/Help:Formatting

''' I find the Best way is to Open a any Formatted already Incorporated Page, and see what has been done , And just learn and follow '''

Let's Encrypt Certificate Issue deployment Issue at Pahwa

2021-09-22T05:41:39Z

Biswajit:

Let's Encrypt Certificate Issue deployment Issue at Pahwa

2021-07-29T08:52:10Z

Biswajit:

Process for manually activating the archive users on Triburg Zimbra mail archive server

2021-05-28T10:12:59Z

Biswajit:

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

== '''[[OLD WIKI Page Do Not Follow This]]''' ==

Process for manually activating the archive users on Triburg Zimbra mail archive server

As the automated script is failing due to the fact , Triburg’s Admin people ( Ramesh ) delete some accounts from the archiving Server , we have to adopt following Manual process .

Prerequisite from Triburg’s Team
Accounts created recently and not able to get mails on the said accounts

Process to follow

1. Main Mail Server – mail.triburg.co.in , 124.30.5.188 ( Local IP 172.16.1.6 )
2. Archive Server – archive3.triburg.co.in ( 172.16.1.16 )
3. Login to archive server after login via mail.triburg.co.in ( key based , password less authentication)

4. confirm the existence of given users via zmprov -l gaa | grep -iE <said_user> ( as zimbra users and use only the name and not the full address as full address will be said_user@archive3@triburg.co.in)
5. if all users exists then Proceed to next step , else create user on archive server by zimbra cli as user@archive3.triburg.co.in password
For Example:
#zmprov ca sylvanus.pradhan@archive3.triburg.co.in xyzz
6. On archive server run the command to confirm the user by command
# zmprov -l gaa | grep -iE <said_user>
It will display the created user.
7. Get all account by this command on mail.triburg.co.in
#zmprov -l gaa
8. Go to mail server Edit the file /opt/zimbra/postfix/conf/archivelist make entry like this
For copy all user in execl in one column in second column paste archive user then select all and paste it in the archivelist file which should be look like this

sylvanus.pradhan@triburg.co.in sylvanus.pradhan@archive3.triburg.co.in

komal.sharma@triburg.co.in komal.sharma@archive3.triburg.co.in

raminder.kaur@triburg.co.in raminder.kaur@archive3.triburg.co.in

ashpreet.kaur@triburg.co.in ashpreet.kaur@archive3.triburg.co.in

preeti.rana@triburg.co.in preeti.rana@archive3.triburg.co.in

rajesh.sk@triburg.co.in rajesh.sk@archive3.triburg.co.in

9. Run the command on mail server to make changes
# postmap /opt/zimbra/postfix/conf/archivelist
10. Run the command on mail server to count the all account
#zmprov -l gaa | wc -l
#strings archivelist | wc -l
The count of above command output should same.

Process for manually activating the archive users on Triburg Zimbra mail archive server

2021-05-28T10:12:15Z

Biswajit:

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

== '''OLD WIKI Page Do Not Follow This''' ==

Process for manually activating the archive users on Triburg Zimbra mail archive server

As the automated script is failing due to the fact , Triburg’s Admin people ( Ramesh ) delete some accounts from the archiving Server , we have to adopt following Manual process .

Prerequisite from Triburg’s Team
Accounts created recently and not able to get mails on the said accounts

Process to follow

1. Main Mail Server – mail.triburg.co.in , 124.30.5.188 ( Local IP 172.16.1.6 )
2. Archive Server – archive3.triburg.co.in ( 172.16.1.16 )
3. Login to archive server after login via mail.triburg.co.in ( key based , password less authentication)

4. confirm the existence of given users via zmprov -l gaa | grep -iE <said_user> ( as zimbra users and use only the name and not the full address as full address will be said_user@archive3@triburg.co.in)
5. if all users exists then Proceed to next step , else create user on archive server by zimbra cli as user@archive3.triburg.co.in password
For Example:
#zmprov ca sylvanus.pradhan@archive3.triburg.co.in xyzz
6. On archive server run the command to confirm the user by command
# zmprov -l gaa | grep -iE <said_user>
It will display the created user.
7. Get all account by this command on mail.triburg.co.in
#zmprov -l gaa
8. Go to mail server Edit the file /opt/zimbra/postfix/conf/archivelist make entry like this
For copy all user in execl in one column in second column paste archive user then select all and paste it in the archivelist file which should be look like this

sylvanus.pradhan@triburg.co.in sylvanus.pradhan@archive3.triburg.co.in

komal.sharma@triburg.co.in komal.sharma@archive3.triburg.co.in

raminder.kaur@triburg.co.in raminder.kaur@archive3.triburg.co.in

ashpreet.kaur@triburg.co.in ashpreet.kaur@archive3.triburg.co.in

preeti.rana@triburg.co.in preeti.rana@archive3.triburg.co.in

rajesh.sk@triburg.co.in rajesh.sk@archive3.triburg.co.in

9. Run the command on mail server to make changes
# postmap /opt/zimbra/postfix/conf/archivelist
10. Run the command on mail server to count the all account
#zmprov -l gaa | wc -l
#strings archivelist | wc -l
The count of above command output should same.