Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Category:JIL
(section)
Category
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training about JIL project. Dated 23 January 2026 - Tetra Support Staff - Takshay== {{#ev:youtube|En0M0GLU_HQ|640}} '''Video summary:''' Architecture training on JP Associates/JIL's Zimbra Network Edition setup, which is unusual in that it's really *two* separate multi-server Zimbra clusters (one for ~1650 users, one for ~500) sharing the same external domain. Each cluster has active-active MTA pairs, multi-master LDAP replication (MMR, not the default single-master replica type), an active-passive PCS-clustered mailbox pair, plus its own archive and log server, fronted by HAProxy for high availability. Internal mail between the two clusters routes MTA-to-MTA based on domain-level split routing rules; if a user isn't found on one cluster the mail retries against the other before bouncing. External-facing access goes through a separate single-URL server running an Nginx + Python/Flask app that looks up which cluster a given user's mailbox lives on and redirects the login accordingly (mobile/IMAP/POP/ActiveSync instead go directly through per-cluster virtual IPs, since the single-URL server only handles web/443). Also covers why a dedicated OpenLDAP lookup server was built in front of the Barracuda spam gateway -- Barracuda can't hold two entries for the same domain, so this lookup server independently mirrors valid usernames from both Zimbra clusters so Barracuda can bounce mail for nonexistent users before it ever reaches the mail servers. Full configuration docs and server details for this setup are pointed to on the wiki's own "JIL" special category page. [[File:Jalindia_cluster_installation_and_configuration.pdf]]
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)