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
Help:Editing
Help page
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!
[[category:Tetra Clients]] [[category:NKDA]] ==Training on NKDA-Architecture. Dated 13 NOV 2024 - Tetra Support Staff - NARENDRA== {{#ev:youtube|SSbKY2wb5uk|640}} '''Video summary:''' Detailed architecture walkthrough (video titled "NKDA-Architecture") of a multi-site Zimbra Network Edition 10.0 mail deployment across three locations (Hyderabad, Kota, Jetsi), migrated from an earlier RainLoop/Rainmail setup. Each site runs redundant physical mail servers (MTA + LB + mailbox pairs in a PCS/DRBD HA cluster, shared NAS storage, automatic failover) plus a dedicated archive server that every user's mail is copied to. Inbound mail flow: KSMG gateway (spam/rule filtering) -> IMSVA (inbound/outbound scanning and per-domain/account rules) -> Postfix daemon -> MTA -> mailbox. Only the Hyderabad servers have direct internet mail access; Kota and Jetsi route all outbound mail through Hyderabad's MTA. Covers an "ANet" gateway used only for a set of internal-only domains (with a documented bypass procedure -- commenting those domains out of the MTA's transport file -- if that gateway goes down), quota tiers assigned by job grade/designation, scripted user creation that auto-provisions the matching archive account, a 90-day password rotation policy, blocking password-protected PDF attachments from being delivered, and the daily check needed on DRBD-based sites (Kota/Jetsi) to confirm primary/secondary storage sync hasn't fallen behind, since a failover during incomplete sync causes real data loss.
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)