Dispatch

Published on: January 5, 2026

Last updated: January 10, 2026

Support and troubleshooting for Dispatch, M Media’s self-hosted email campaign system for WordPress.

📧 Contact Dispatch Support

Get help with delivery issues, configuration questions, or unexpected behavior.

Open Support Form

📚 Dispatch Documentation

Setup guides, configuration references, and operational notes.

View Dispatch Docs

Common Dispatch Issues

Email Not Sending

  • Verify SMTP credentials are correct
  • Confirm the sending domain matches SMTP configuration
  • Check server firewall rules for outbound mail

Messages Going to Spam

  • Ensure SPF, DKIM, and DMARC are configured
  • Use a dedicated sending domain
  • Avoid test campaigns with placeholder content

Subscriber Import Issues

  • Verify CSV formatting and encoding
  • Confirm required fields are present
  • Check for duplicate or malformed email addresses

Campaign Scheduling Problems

  • Confirm WordPress cron is running reliably
  • Check server time zone settings
  • Avoid overlapping large campaigns

Dispatch System Requirements

WordPress Environment

  • WordPress 6.3+
  • PHP 8.1+
  • MySQL or MariaDB 10.4+
  • HTTPS enabled

Email Infrastructure

  • Working SMTP provider
  • SPF and DKIM access
  • Dedicated sending domain recommended
  • Stable outbound connectivity

Before You Contact Dispatch Support

  • Dispatch version number
  • WordPress and PHP versions
  • SMTP provider name
  • Error messages or logs if available
  • Steps to reproduce the issue
  • License key (last 6 characters only)
// 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.

🤖
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