Category:MPSDC (XTRANET): Difference between revisions
Created page with "category:Tetra Clients category:MPSDC (XTRANET) ==MPSDC (XTRANET) KT Session 13-July-2026- Tetra Support Staff - TAKSHAY== <HTML5video type="youtube" width="640" hei..." |
Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo) |
||
| Line 4: | Line 4: | ||
==MPSDC (XTRANET) KT Session 13-July-2026- Tetra Support Staff - TAKSHAY== | ==MPSDC (XTRANET) KT Session 13-July-2026- Tetra Support Staff - TAKSHAY== | ||
{{#ev:youtube|PpPkYHpiTQg|640}} | |||
'''Video summary:''' KT session on MPSDC/XTRANET's 5-server Zimbra Network Edition infrastructure: two MTA+proxy nodes (ZP1/ZP2, active-active, fronted by the client's own external load balancer -- not something Tetra manages), two mailbox+LDAP nodes (ZM1/ZM2, active-passive in a PCS cluster), and a dedicated archive server. Covers a recent full-stack rebuild -- RHEL 7 to RHEL 9 and Zimbra 10.0 to 10.1.13, driven by accumulated vulnerabilities on the old OS -- done by standing up five fresh RHEL 9 VMs alongside the old server and migrating mail data across via imapsync, keeping the same server naming. Also covers routine issue patterns: application relay-denied errors needing the app's IP whitelisted on both proxy nodes, mail flow via dedicated Trend Micro-hosted MX records for spam filtering on both inbound and outbound, and -- the most detailed part of the session -- the full offline license activation procedure this client requires (unlike most clients' simpler online activation): disabling/permissive-mode SELinux, installing the license daemon package, generating network/license fingerprint files from the server, submitting them through Zimbra's licensing portal to get back an XML activation file, and applying it either via the admin console or the `zmlicense` CLI. | |||
Latest revision as of 02:53, 25 July 2026
MPSDC (XTRANET) KT Session 13-July-2026- Tetra Support Staff - TAKSHAY[edit]
Video summary: KT session on MPSDC/XTRANET's 5-server Zimbra Network Edition infrastructure: two MTA+proxy nodes (ZP1/ZP2, active-active, fronted by the client's own external load balancer -- not something Tetra manages), two mailbox+LDAP nodes (ZM1/ZM2, active-passive in a PCS cluster), and a dedicated archive server. Covers a recent full-stack rebuild -- RHEL 7 to RHEL 9 and Zimbra 10.0 to 10.1.13, driven by accumulated vulnerabilities on the old OS -- done by standing up five fresh RHEL 9 VMs alongside the old server and migrating mail data across via imapsync, keeping the same server naming. Also covers routine issue patterns: application relay-denied errors needing the app's IP whitelisted on both proxy nodes, mail flow via dedicated Trend Micro-hosted MX records for spam filtering on both inbound and outbound, and -- the most detailed part of the session -- the full offline license activation procedure this client requires (unlike most clients' simpler online activation): disabling/permissive-mode SELinux, installing the license daemon package, generating network/license fingerprint files from the server, submitting them through Zimbra's licensing portal to get back an XML activation file, and applying it either via the admin console or the `zmlicense` CLI.