Requirements

Published on: March 16, 2026

Last updated: March 16, 2026

Requirements

Dispatch Pro has the same server requirements as Dispatch Core, plus two additional prerequisites.

Prerequisites (Pro-specific)

  • Dispatch Core must be installed and active — Dispatch Pro is an extension, not a standalone plugin. Both plugins must be active simultaneously.
  • A valid Dispatch Pro license key — obtained at purchase from mmediasoftwarelab.com. Required to activate Pro features after installation.

WordPress & PHP

  • WordPress: 6.0 or later — latest stable release recommended
  • PHP: 7.4 minimum — PHP 8.1 or 8.2 recommended
  • Database: MySQL 5.7+ or MariaDB 10.3+

PHP extensions

  • openssl — required for TLS/SSL SMTP connections
  • mbstring — required for multi-byte string handling

Browser (for Visual Builder)

The Visual Builder runs in your browser inside the WordPress admin. For the best experience:

  • Use a modern browser — Chrome or Edge recommended; Firefox and Safari also supported
  • JavaScript must be enabled
  • If the builder opens blank or behaves oddly, try disabling other admin-side plugins temporarily — JavaScript conflicts are the most common cause

WP-Cron & SMTP

Same requirements as Core: WP-Cron must be functional, and SMTP credentials are required for sending campaigns and transactional emails. See Dispatch Core Requirements for full details.

Next: Installation

Dispatch Pro

Premium self-hosted email marketing for WordPress. Everything in Core, plus the Visual Builder, customizable transactional emails, and CSV import/export.

Quick Links

Need support?

Dispatch Pro Support →

🤖
Support Bot
"Have you tried restarting your computer? Please check our knowledge base. Your ticket has been escalated. Estimated response: 5-7 business days."
❌ Corporate Script Theater
👨‍💻
Developer (M Media)
"Checked your logs. Line 247 in config.php — the timeout value needs to be increased. Here's the exact fix + why it happened. Pushed a patch in v2.1.3."
✓ Real Technical Support

Support From People Who Understand the Code

Ever contact support and immediately know you're talking to someone reading a script? Someone who's never actually used the product? Yeah, we hate that too.

M Media support means talking to developers who wrote the code, understand the edge cases, and have probably hit the same problem you're dealing with. No ticket escalation theatrics. No "have you tried restarting?" when your question is clearly technical.

Documentation written by people who got stuck first. Support from people who fixed it.

We don't outsource support to the lowest bidder or train AI on canned responses. When you ask a question, you get an answer from someone who can actually read the logs, check the source code, and explain what's happening under the hood.

✓ Real troubleshooting, not corporate scripts
✓ Documentation that assumes you're competent
✓ Email support that doesn't auto-close tickets
✓ Updates based on actual user feedback
// real.developer.js
const approach = {
investors: false,
buzzwords: false,
actualUse: true,
problems: ['real', 'solved']
};
// Ship it.

Built by People Who Actually Use the Software

M Media software isn't venture-funded, trend-chasing, or built to look good in pitch decks. It's built by developers who run their own servers, ship their own products, and rely on these tools every day.

That means fewer abstractions, fewer dependencies, and fewer "coming soon" promises. Our software exists because we needed it to exist — to automate real work, solve real problems, and keep systems running without babysitting.

We build software the way it used to be built: practical, durable, and accountable. If a feature doesn't save time, reduce friction, or make something more reliable, it doesn't ship.

✓ Every feature solves a problem we actually had
✓ No investor timelines forcing half-baked releases
✓ Updates add value, not just version numbers
✓ Documentation written by people who got stuck first

This is software designed to stay installed — not be replaced next quarter.