Ten modules, 120 hours, a clear technical decision after every lesson. You learn what we do every day in production since 2010: strategy, authentication, deliverability, PowerMTA, KumoMTA, reputation recovery, and Law 81 compliance. No inflated theory. No panel demos. Real operations.
In sixteen years operating email marketing from Panama, we arrived at an observation that repeats with new clients every month. The CMO arrives with an agency that knows how to craft copy and flashy templates but when you ask about DMARC alignment they just stare. The engineer arrives who can stand up Postfix with eyes closed but does not understand why their welcome campaign has 12% open rate when the sector benchmark sits at 28%. The SaaS founder arrives who paid 4,800 dollars monthly for HubSpot Enterprise and discovers that the inbox placement problem does not get solved with a more expensive panel because the root cause is in the domain configuration.
Email marketing in 2026 lives at that intersection. Gmail and Yahoo since February 2024 force high-volume senders to have SPF, DKIM and DMARC aligned, spam rate below 0.3 percent (with 0.1 percent as the real target for stable inbox placement), functional one-click unsubscribe, and valid PTR records on every sending IP. Microsoft Outlook joined in 2025 with the same requirements for senders above 5,000 daily messages. Google retired the IP and domain reputation dashboards in Postmaster Tools on September 30, 2025 and moved the model to compliance-first. This shifted the conversation: it is no longer enough to say "I have good reputation", now you have to demonstrate intentional authentication and controlled complaint rate every day.
If all you need is to send a monthly newsletter to 3,000 contacts at your company, this course is not for you. A free Mailchimp panel or Brevo on its starter tier will be cheaper. This course makes sense when there is already infrastructure to operate, when there is reputation to protect, when the ROI of sending justifies knowing what happens between the "send campaign" button and the recipient inbox.
We decided to open the knowledge we use in productive operation because we got tired of the regional market depending on US courses that assume clean Amazon SES IPs and compliance that does not apply to Latin American operators. Here we cover PowerMTA because it is the commercial standard with two decades in production and because half the industry still runs on it. We cover KumoMTA because it is the serious open-source answer, written in Rust by Wez Furlong, the engineer who originally designed PowerMTA and Momentum, and because for many clients the right decision in 2026 is no longer to pay 3,000 dollars annually for a license. We cover both in operational depth because the decision between one and the other depends on project context, not on the instructor personal preference.
Worth being explicit because charging 899 dollars for a technical course demands clarity about who ends up better after taking it and who does not. We run small quarterly cohorts with limited seats to preserve interaction quality. We admit selectively and prefer that the wrong person does not enroll.
Platform engineer who operates or will operate an MTA in production. If your job is maintaining sending servers, tuning performance, parsing delivery logs, and sleeping well knowing the infrastructure holds up under the next Black Friday, this course gives you the full playbook. You will come out able to install and configure PowerMTA with deep knowledge of its directives file (more than 200 parameters relevant in serious operations), and you will come out able to do the equivalent in KumoMTA with Lua configuration files. You will understand which decision suits which project.
Deliverability specialist managing high-volume campaigns. If your day is diagnosing why client X campaign dropped from 87% to 62% inbox placement, this course brings you two things you do not find together elsewhere: the deep technical side (how Gmail behavior shifts when soft bounce ratio rises above a certain threshold, what specific Microsoft signal triggers throttling, how to diagnose a DKIM body hash problem with headers rewritten by an intermediate MTA) and the operational side (what to document, how to recover burned reputation, how to negotiate with Postmaster when automated feedback does not answer).
In-house team at company sending more than five million monthly messages. At that volume Mailchimp stops making economic sense and it starts making sense to evaluate own or managed infrastructure. But the decision requires understanding what operating really means. This course gives you the foundation to make that decision with data instead of faith, and if you decide to move, it gives you the technical playbook to do it without losing reputation during the transition.
Independent consultant who advises clients on email marketing. The consulting market is saturated with people who know how to click buttons in panels. Real differentiation comes when you can technically audit a client configuration, identify the five things costing them 15% inbox placement, and propose concrete changes with defensible technical rationale. That is what we teach.
Founder or CTO of SaaS startup with concrete operational problem. If your product sends critical transactional emails (password resets, magic links, payment confirmations) and you start getting reports of "the email did not arrive", this course saves you months of misdirected diagnosis. You will come out able to identify whether the problem is authentication, reputation, content, infrastructure, or client configuration.
If what you want is a copywriting course for sales emails, this is not it. If you want to learn to design responsive HTML templates that look good in Outlook, this is not it. If you will operate exclusively on Mailchimp or HubSpot because your volume does not justify more, this is not it. Those courses exist and are useful, but they address a different problem.
The program is designed to be completed in 8 to 12 weeks dedicating 10 hours weekly. Each module combines applied theory with hands-on lab on a shared KumoMTA instance and a sandbox domain owned by the student. The sequence respects technical dependencies: you cannot understand IP warming without understanding authentication, you cannot operate an MTA without understanding SMTP, you cannot recover reputation without understanding what damaged it.
Before configuring a single DNS record you have to understand the commercial context. This module covers the real economics of the channel: effective CPM by vertical, multi-touch attribution, honest cost comparison between managed ESP and own operation at different volumes, and platform decision framework based on client context.
The foundation everything else assumes. SMTP protocol in detail (relevant ESMTP extensions, pipelining behavior, STARTTLS, connection reuse handling), DNS applied to email (A, AAAA, MX, TXT, PTR, CNAME records), reverse lookup behavior, and why a misconfigured PTR tanks deliverability even with perfect SPF and DKIM.
The technical heart of modern email. SPF with its traps (the 10 DNS lookups limit, flattening, when to use include vs redirect), DKIM with rotatable selectors, key management, body hash and how an intermediate MTA that rewrites headers breaks it. DMARC strict vs relaxed alignment, progressive policy from p=none to p=reject, reading RUA and RUF reports, and how to migrate to p=reject without breaking third parties.
The modern authentication stack that separates the professional operator from the amateur. BIMI with its two paths: VMC for brands with registered trademark and CMC as the alternative opened in 2025. MTA-STS to force TLS in transport (only 1.7% of domains have it, big differentiation opportunity). DANE with TLSA records over DNSSEC. TLS-RPT to receive automated reports of encrypted transport failures.
The commercial standard with 20 years on the market. Installation on Linux and Windows, directive-based configuration file (more than 200 operationally relevant parameters), virtual MTAs and IP pools, bounce processing with custom scripts, log parsing and delivery metrics, integration with own management systems.
The serious open-source MTA of 2026. Built in Rust with Lua as configuration language, Apache 2.0, capable of processing up to 60 million messages per hour on adequate hardware per benchmarks published by the KumoMTA team. Installation, architecture, Lua configuration, queue management, monitoring, and deployment patterns on modern clouds.
The art of introducing a new IP to the world without getting it burned in the first week. Realistic schedules based on target volume, segmentation by engagement during warming (first 30-day actives, then 60, then 90), daily monitoring in Google Postmaster Tools and Microsoft SNDS, handling dormant IPs that require rewarming, and the 2026 reality where domain reputation weighs more than IP reputation.
The module people underestimate until they need it. How to recover an IP or domain when reputation got burned. Analysis of provider-specific bounce codes (Gmail codes 421-4.7.32, 550-5.7.26, 421-4.7.28 have specific meaning that defines tactical response). Negotiation with FBL (Feedback Loops). Recovery post-blocklist (Spamhaus, SpamRats, Barracuda). Recovery post-Postmaster Tools retirement, where the model shifts to compliance-first without reputation dashboards.
Email marketing in 2026 lives under regulation. Panama Law 81 with the 2026 reform that raises the ANTAI sanction ceiling to B/.100,000, GDPR for European contacts with its particularities of international transfer without adequacy decision, CAN-SPAM for US audience, CASL for Canada. How to document consent, how to implement functional opt-out, what to keep and for how long. No abstract legal theory: this module is taught by our in-house legal team.
The module that integrates everything. How to launch a new program from zero, what metrics to monitor day-to-day, how to structure the team (even if you are the whole team), how to document operations so they survive your departure, how to handle incidents (IP outage, mass blocking, complaint storm), how to present reports to non-technical stakeholders. Real cases from the Email Marketing Panama team with anonymized names.
This is the most consequential architectural decision in any email operation at scale. For two decades the answer was PowerMTA and done. The landscape shifted in 2023 when KumoMTA arrived as a serious open-source alternative built by Wez Furlong, the same architect behind PowerMTA and Momentum. The course does not push you to one; it teaches you the criteria to decide based on context.
| Criterion | PowerMTA | KumoMTA |
|---|---|---|
| License and cost | Commercial, from ~$3,000/year per server | Apache 2.0, free without restrictions |
| Age and maturity | Since early 2000s, de facto standard in ESPs | Since 2023, accelerated adoption in 2025-2026 |
| Operating systems | Linux and Windows | Linux only, cloud-native by design |
| Configuration language | Own directive file with 200+ parameters | Lua for configuration and scripting |
| Core language | Proprietary C/C++ | Open-source Rust |
| Maximum throughput | Excellent, requires specific tuning | Up to 60M msg/hour on 96 cores per benchmarks |
| Community and support | Commercial support, closed ESP community | Active Discord, open GitHub, maintained by dedicated team |
| When to pick it | When you already have PowerMTA-trained teams, integration with legacy systems, requirement for formal commercial support | When license cost matters, when the stack is modern cloud-native, when open source and freedom to fork are valued |
The course dedicates 32 combined hours (16 per MTA) to hands-on operation with both. It ends with a migration exercise: given an existing PowerMTA setup, migrate it to KumoMTA without reputation loss and with controlled downtime.
The difference between a course that stays in theory and a course that leaves you operationally capable is the lab. This course includes three layers of practice during the 12 months of access.
Layer one: sandbox domain per student. Each participant receives a personal subdomain of the form yourname-lab.empcursos.com with full control over its DNS records. There you publish your SPF, DKIM, DMARC, BIMI, MTA-STS, DANE and TLS-RPT, see how they propagate, validate them with MXToolbox, dmarcian, and internal tools we provide, and you understand in practice what other courses only show in a slide.
Layer two: shared KumoMTA instance. Access to a preconfigured KumoMTA node with individual per-student quotas (200 daily messages to lab-controlled test inboxes, not to real contacts). There you exercise real configuration, parse real logs, observe behavior under different scenarios. For PowerMTA we provide an isolated VM under the course academic license, where you repeat the equivalent exercises.
Layer three: two technical consultations with an EMP team engineer. 60-minute sessions where you bring your real case (could be your work, a client, a personal project) and a senior Email Marketing Panama engineer helps you diagnose and solve. For many students this is the most valuable thing in the course: direct access to someone who operates productive infrastructure every day, for 12 months.
Access to the real productive infrastructure of Email Marketing Panama. That would violate contractual obligations with active clients and is non-negotiable. The course lab is functionally equivalent for learning purposes, but it is not the real operation nor does it replace it.
To make good email architecture decisions you have to look at the current state of the ecosystem without makeup. What follows are verified data points as of this course publication date, not projections or internal estimates. The course starts from these figures to build the decision criteria.
Real DMARC adoption. According to the 2026 US adoption report published by PowerDMARC, 95.8% of analyzed domains have a DMARC record published, but only 49% are on p=reject policy. Translation: half the market has nominal DMARC without real enforcement. SPF is on 95.7% of domains. DNSSEC barely 18%. And MTA-STS, the standard that forces TLS in transport, lives on a dramatic 1.7% of domains. This gap between presence and enforcement is where deliverability risk concentrates today.
Spam complaint rate as the real ceiling. Gmail official threshold sits at 0.3% per their bulk sender documentation. But that 0.3% is where enforcement begins, not where your program works well. 2026 benchmarks show the stable sender operates below 0.1% sustained. The Postmaster Tools team recommends aiming at 0.1% to avoid problems; above that there is risk. A sender dispatching 10,000 daily messages only needs 30 spam complaints to cross 0.3%. The operational calculation shifts: complaint rate management is no longer a vanity metric, it is a survival metric.
Average commercial inbox placement. 2026 benchmarks place average commercial inbox placement at 89%, per the industry benchmarks published in 2026. A figure that has remained notably stable since the Gmail/Yahoo February 2024 requirements took effect. But there is wide dispersion: compliant senders operate between 92% and 97%, while non-compliant ones fall between 66% and 78%. The gap between the good and the bad widened. Almost a third of senders is still non-compliant on at least one requirement two years after they entered force. The course takes you to the high band.
The retirement of Google Postmaster reputation. On September 30, 2025 Google retired the IP reputation and domain reputation dashboards in Postmaster Tools. And the operational model changed entirely. Before, the practice was looking at the reputation metric in the panel and reacting. Now, the model is compliance-first: obsessive focus on authentication health and complaint rate, without a visible score to correct. It has upsides and downsides. Good because it removes the false precision of the score. Bad because it demands operational knowledge to infer reputation from indirect indicators. The course teaches this new model in module 8.
Apple Mail Privacy Protection inflating opens. Approximately half of reported opens since 2021 are artificial, generated by automatic tracking pixel loading in iOS and macOS Mail. Any historical open rate metric post-2021 is overestimated. The industry is still adapting. The course teaches how to segment Apple Mail Privacy from real opens and how to build alternative engagement metrics that are actionable.
Microsoft Outlook joined the requirements in 2025. Until 2024, strict authentication requirements were a Gmail/Yahoo issue. In 2025 Microsoft began requiring SPF, DKIM and DMARC for senders dispatching more than 5,000 daily messages to Outlook.com. No exceptions. The change extended the enforcement reach to the Microsoft ecosystem and raised the technical bar for all serious operators. The course covers Outlook particularities (SNDS, JMRP, Microsoft filter behavior, IP handling in the Microsoft cloud) in module 8.
The figures above are not trivia. They are the parameters that define which technical decisions make sense in 2026. An email marketing course designed in 2022 teaches you to look at Postmaster dashboards that no longer exist, to optimize for a spam threshold that became obsolete, and to configure DMARC at p=none as if it were enough. This course starts from the current state and builds from there.
The "what you will learn" bullet lists tend to be generic. We prefer to describe real operational scenarios — situations we saw happen more than once in productive accounts — where after the course you will know exactly what to do. Each one has its reference module and associated tool set.
30,000 monthly magic links the first quarter, scaling to 200,000 by year-end. Today they send via SES with the CTO account and emails land in Outlook spam in 22% of cases. After the course you identify in 90 minutes that the problem is triple: subdomain shared with marketing, absence of DKIM aligned with From, and SES default IP with mixed reputation. You design the right solution for that volume and context: dedicated subdomain txn.domain.com, rotatable DKIM, progressive DMARC, and the architectural decision between staying on SES with dedicated IP or migrating to own KumoMTA based on 18-month cost projection.
15 million monthly messages running since 2018 on three PowerMTA servers with 11,000 dollars annual license. The board asks to reduce OpEx. When you finish the course you conduct the honest evaluation: you size an equivalent KumoMTA cluster, calculate the real annual saving considering refactor cost, design the 12-week migration plan with incremental cutover by traffic type, execute the exercise without inbox placement drop or visible interruption for the end user. And you document everything so the new team can maintain it when you move on.
Monday 8 AM, monitoring alert: the IP sending 600,000 daily messages showed up in Spamhaus CSS. The client panics, management demands immediate response. With the course playbook in hand you execute the response: pause sending, identify root cause (typically a complaint spike, a spamtrap hit, or a client account compromise), prepare the delisting case with documented evidence, submit the delisting request through the correct channel, and design the back-to-sending strategy without triggering another blocklist entry. Most importantly: you learn when it is better to rotate the IP and start from zero instead of investing three weeks in a recovery that will end up costing reputation.
Fintech client requests BIMI to reinforce trust in their inbox. The course trains you to evaluate prerequisites honestly before starting: do they have DMARC at p=quarantine or p=reject? If not, that is the first job. Do they have a valid SVG Tiny PS logo? If not, it needs to be prepared. VMC or CMC? If they have a registered trademark VMC is the golden route (display in more MBPs, stronger trust signal). If not, CMC is the valid alternative for Gmail since 2025. You coordinate certificate issuance with an approved CA, publish the BIMI record in DNS, monitor the rollout, and handle the edge case where some MBPs still do not honor CMC.
Support gets complaints from clients saying they are receiving emails from "support@client.com" asking to verify card. Phishing using the client domain. With the tools the course gives you, you diagnose the scope by analyzing DMARC reports received in RUA, identify unauthorized origin IPs, escalate DMARC from p=none to p=reject in a controlled way (not overnight, that breaks legitimate non-inventoried services), implement BIMI to visually reinforce the legitimate sender, and design continuous monitoring to detect future attempts.
Client pays 2,400 dollars monthly on Mailchimp Premium for 180,000 contacts. Volume grew to the point where own infrastructure makes sense. But the marketing team has workflows built in Mailchimp and the transition scares them. Coming out of the course you propose the transition in three measurable phases: first replicate the technical infrastructure with new domain and controlled warming in parallel to Mailchimp, second migrate email types by category (first low-risk transactional, then newsletters, finally promotional), third retire Mailchimp after validating that inbox and engagement metrics hold. Realistic 90-day timeline, net monthly savings of 1,400 dollars after own infrastructure costs.
The six cases above are not hypothetical. They are anonymized adaptations of cases the Email Marketing Panama team has resolved in production. Each is discussed in the course with the technical details that led to the outcome, the hard decisions taken along the way, and the mistakes we avoided repeating.
This list is not a buzzword storm. Each item is a concrete technical capability that gets evaluated in the course practical exercises and that is considered prerequisite to issue the completion certificate.
Install and configure an MTA from zero in production. Be it PowerMTA or KumoMTA according to what the project needs. Includes sizing the server correctly, configuring IPs, bringing up the service with systemd, integrating monitoring, and having a documented runbook for incidents.
Configure full authentication for a new domain. SPF with flattening if needed, DKIM with 2048-bit key and rotatable selector, progressive DMARC from p=none to p=reject with report reading, BIMI with CMC or VMC depending on budget, MTA-STS to force TLS, TLS-RPT for monitoring. All validated in external tools.
Warm up a new dedicated IP. Realistic 4 to 6 week schedule adapted to target volume, engagement segmentation, daily monitoring, tactical adjustment when any signal deviates. Process documentation for later audit.
Diagnose inbox placement problems with methodology. No guessing. The course delivers a decision tree that runs authentication first, reputation second, content third, infrastructure fourth, receiver configuration fifth. Each node of the tree has specific checks and validated tools.
Recover a burned IP or domain. Identify root cause, execute the remediation plan, negotiate with feedback loops if applicable, do rewarming from zero reputation. The reality is that many cases do not fully recover; the course teaches when to rotate the IP instead of investing time in an impossible recovery.
Configure a complete email marketing program for a new client. From the initial architecture decision (managed ESP or own infrastructure? shared IP or dedicated? PowerMTA or KumoMTA?) to the first send, going through all legal documentation Law 81 or GDPR.
Migrate between MTAs without losing reputation. Classic case: client with old PowerMTA who wants to move to KumoMTA for cost. The course teaches the step-by-step sequence to migrate without visible downtime and without reputation being affected during the transition.
Technically defend operational decisions to non-technical stakeholders. Sounds like a soft skill, but it is the real bottleneck for many engineers: knowing how to explain to a CEO why the investment in BIMI with VMC is worth the 1,500 dollars annual certificate, or why migrating from Mailchimp to own infrastructure pays for itself in 7 months. The course includes business case and communication templates.
This is the central difference. It is not a course taught by consultants who read blogs and put together a curriculum. It is taught by engineers from the Email Marketing Panama team who operate PowerMTA and KumoMTA in production every day since 2010, who have served more than 400 B2B accounts during those years, who have recovered burned IPs and migrated full infrastructures for clients in banking, retail, SaaS and agencies.
The teaching team is composed of five people from the EMP technical staff. Each module is taught by the specialist in the corresponding area. The PowerMTA and KumoMTA modules are taught by our lead platform engineer, with six years operating PowerMTA in production and active participation in the KumoMTA community since its release. The Law 81 compliance module is taught by our internal DPO with official certification. The strategy and deliverability modules are taught by engineers with direct operational responsibility over productive accounts.
The difference shows in class. When someone asks "what would happen if the soft bounce ratio rises from 4% to 7% in a week on a dedicated IP sending to Outlook", the answer is not general theory; it is what we saw happen on March 14 in a fintech account, what we did to diagnose, and what worked.
2026 cohort with limited seats. The launch promotion at $899 USD active while it lasts. A team advisor responds within 4 business hours with all program details, payment method and enrollment availability in the current cohort.
Request course information
