Editing Training 2022 Linux team/ (section)

==Training Zimbra Cli part 2. Dated 19 Feb 2022 - Tetra Support Staff - Biswajit Banerjee==

{{#ev:youtube|tokCcT2SjTo|640}}

'''Video summary:''' "Zimbra Cli Training part2" -- continues the `zmprov` deep-dive live against a real SysNet Global Zimbra server. Establishes the core naming convention that unlocks the whole command family: the first letter(s) tell you the operation -- `g` = get/query (safe, read-only), `c` = create, `m` = modify, `d` = delete, `sp` = set password -- so `ga` = get all accounts, `ca` = create account, `ga <account>` = get one account's full attribute dump, `am` = modify account, `gs`/`ms` = get/modify server (per-host settings, requires specifying the hostname), `gcf`/`mcf` = get/modify the global config (environment-wide settings, no hostname needed). Demonstrates: listing all accounts (`zmprov ga | wc -l` to count ~4000 accounts) and grepping the output for a specific surname to find matching accounts; reading and then safely (without actually applying) walking through changing a server's MTA relay-host (`zimbraMTArelayhost`) setting via `gs`/`ms`; and inspecting `zimbraMtaMyNetworks`, explaining its security significance -- any IP listed there is fully trusted to relay mail through the server without authentication, so it should only ever contain localhost and the server's own IP, plus rare, deliberate additions for specific non-authenticating applications (each addition requires copying the full existing value, appending the new IP, and re-running the modify command since it's a single space-delimited attribute, not an appendable list). Also shows the equivalent lookup for global SMTP settings via `gcf`/`zimbraSmtpHostname`. Closes by encouraging trainees to build their own personal Zimbra server to practice `zmprov` hands-on, take a live Q&A question about the practical risk of an unauthenticated relay IP (confirming any user, not just a specific account, could send mail from a trusted IP without credentials), and ends with an unrelated live production interruption (the presenter noticing and fixing an unexpected configuration value change on a real server before closing the session).