Category:CRPF: Difference between revisions

Training on CRPF Session 1. Dated 02 NOV 2024 - Tetra Support Staff - TAKSHAY[edit]

Video summary: KT session (Part 1) on CRPF's mail environment, migrated from Lotus Notes to Zimbra and split across two parallel deployments: a Network Edition environment (~5000 users) and an Open Source environment (~10000 users), each with its own pair of MTA, LDAP, and mailbox servers plus an HA pair in front. To hide this split from end users, a single-URL login server (Python/Flask, itself HA'd via a shared virtual IP between two identical instances) looks up which environment a given user belongs to via a text file that's regenerated from both environments' user lists every 5 minutes by cron -- meaning a newly-created account needs up to a 5-minute wait before it can log in through the unified URL. Also covers CRPF's specific requirement around their 429 physical offices: accounts are provisioned with an office-suffixed internal domain and restricted so a user can only mail within their own office's user group, while an email alias masks that internal office-specific address so the outside-facing address a correspondent sees never reveals which office the user belongs to.

Training on CRPF KT Session Part 1. Dated 16 July 2026 - Tetra Support Staff - TAKSHAY[edit]

Video summary: Another CRPF KT session covering the same dual Network Edition / Open Source Zimbra split described in "CRPF Session 1" (VuCx41rFxds) on this page, with additional detail. Clarifies the split is rank-based: senior/high-rank staff (~5000 of ~14000-15000 total users) sit on the Network Edition side, regular staff on Open Source. Covers OS installation basics for these servers (minimal RHEL-family install, local-only root credentials, no external access), and explains cross-environment mail delivery via split-domain routing: since the same domain exists on both sides, a mail from an Open Source user to a Network Edition user (or vice versa) is routed by checking whether the recipient exists locally; if not found on either side after being relayed back and forth up to three times, it bounces back to the sender. Also notes structural differences from the other session's description: mailbox servers here are standalone (no HA clustering) and each environment has its own log server rather than a shared archive server. Full installation documentation was noted as being covered in a following session.

Training on CRPF KT Session Part 2. Dated 16 July 2026 - Tetra Support Staff - TAKSHAY[edit]

Video summary: A third, more complete CRPF KT session covering the same dual Network Edition / Open Source Zimbra architecture as the other two videos on this page (VuCx41rFxds, IqYu4dBUpNU) -- same 429-domain, rank-based split, single-URL Flask/nginx login router (here specified as active-passive via a shared virtual IP, not active-active) -- but adds several details not covered elsewhere: LDAP uses true MMR (multi-master) replication between the two LDAP nodes so either can go down without impact; "archiving" here isn't Zimbra's built-in archive feature but a simpler BCC-style mechanism -- each user has a paired hidden "username_in"/"username_out" mailbox that silently receives a copy of every inbound/outbound mail; authentication is handled entirely through the client's own Windows Active Directory server rather than Zimbra's native LDAP auth, with a self-service password change/reset page (OTP sent to the user's registered number) integrated against that AD server; and a NextCloud server is deployed separately for document/file management. Confirms overall scale: ~5000 licensed users (Network Edition) plus additional Open Source users, across 429 total domains, as two separate multi-server Zimbra instances.