Configuration

Published on: January 12, 2026

Last updated: January 12, 2026

Configuration

Configuration is where Dispatch goes from “installed” to “actually usable.” Set SMTP, choose safe sending limits, add compliance info, then brand your emails.

SMTP setup (recommended)

  1. Go to Dispatch – Settings – SMTP Configuration
  2. Enable Use SMTP
  3. Enter host, port, username, password
  4. Choose encryption: TLS (587) or SSL (465)
  5. Click Test SMTP Connection
  6. Send a test email to yourself

Safe sending limits

Lower rates usually mean better deliverability. Start conservative and ramp up after you confirm consistency.

  • Emails per minute: 30 (good starting point)
  • Emails per hour: 500 (adjust based on reputation and server resources)

Compliance

  • Add your physical mailing address (CAN-SPAM requirement)
  • Keep double opt-in enabled (strongly recommended)
  • Only send to people who opted in (never buy lists)

Email branding

Branding applies to campaigns and transactional emails. Set it once, then stop thinking about it.

  1. Go to Dispatch – Email Branding
  2. Upload logo via the Media Library
  3. Set primary and secondary colors
  4. Set header/body/footer background colors
  5. Save branding settings

Transactional email templates

  • Confirmation email (double opt-in): uses {{CONFIRMATION_URL}}, {{EXPIRY_HOURS}}, {{SITE_NAME}}
  • Welcome email (post-confirm): can use brand gradient header and CTA
  • Unsubscribe email: includes {{UNSUBSCRIBE_URL}} and site tokens

Dispatch

Self-hosted email campaigns for WordPress: list management, sending controls, compliance tools, and privacy-first defaults.

Quick Links

🤖
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
Tracking Scripts ❌
Telemetry Services ❌
Anonymous Statistics ❌
Your Privacy ✓

No Bloat. No Spyware. No Nonsense.

Modern software has become surveillance dressed as convenience. Every click tracked, every behavior analyzed, every action monetized. M Media software doesn't play that game.

Our apps don't phone home, don't collect telemetry, and don't require accounts for features that should work offline. No analytics dashboards measuring your "engagement." No A/B tests optimizing how long you stay trapped in the interface.

We build tools, not attention traps.

The code does what it says on the tin — nothing more, nothing less. No hidden services running in the background. No dependencies on third-party APIs that might disappear tomorrow. No frameworks that require 500MB of node_modules to display a button.

✓ Your data stays on your device
✓ No "anonymous" usage statistics
✓ Minimal dependencies, fewer risks
✓ Respects CPU, RAM, and battery