Mailmodo deliverability: what the platform covers and what you own

Mailmodo is an email marketing platform best known for interactive AMP emails — forms, polls and widgets that work inside the message in Gmail. Like every ESP, it can give you sending infrastructure, authentication tooling and suppression handling. It cannot give you a reputation. If your Mailmodo campaigns are landing in spam, the cause is almost always on your side of that line: authentication, an unwarmed sending domain, a volume spike, or the list.

What the platform handles

• Outbound infrastructure: MTAs, IP pools, queueing, retry behaviour and TLS on the connection.
• Authentication setup: the DNS records to publish for your sending domain, and DKIM signing at send time.
• Bounce and complaint processing: parsing delivery status notifications and feedback-loop reports into suppression.
• Unsubscribe plumbing: the footer link and the List-Unsubscribe headers.
• AMP delivery: sending the text/x-amp-html part alongside HTML and plain text.

Where the platform's coverage ends

The last two are the ones that cause arguments with support. A 99.5% delivery rate in the platform dashboard is an acceptance figure; it is consistent with most of your campaign sitting in spam.

Work through these in order

1. Authentication, verified on delivered mail. Publish what the platform asks for, then confirm it on a real received message:

Authentication-Results: mx.google.com;
  dkim=pass header.i=@mail.example.com;
  spf=pass smtp.mailfrom=bounce.platform.example;
  dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=example.com

You need all three passing *and* alignment on the From domain. Then check SPF for overflow — one record per domain, at most 10 DNS-querying mechanisms and 2 void lookups. Stacks that add a reviews tool, a helpdesk and a shipping notifier blow this limit routinely, and the result is permerror, which many receivers treat as a failure.

2. Sending domain state. If you connected a brand-new subdomain and immediately sent a campaign, that is the problem. New domains need to exist, then send low volume with real engagement, then ramp. Send transactional or lifecycle mail through the subdomain first — it has the best engagement you will get.

3. Volume pattern. Ramp no faster than roughly 30–50% day over day while reputation is young. A 421 or 450 deferral is the receiver telling you to slow down; backing off is correct, retrying harder converts a defer into a block.

4. List quality. Check hard bounce rate (target under 1%), complaint rate (Google's published threshold is 0.3%; aim below 0.1%), and whether the list was imported, bought or collected without a real opt-in. Verify anything older than six months before its first send, and hold catch-all and unknown verdicts out of bulk sends — Microsoft 365 commonly accepts at RCPT TO and bounces later, which is where "verified" addresses still fail.

5. Reputation signals. Google Postmaster Tools for spam rate and authentication rates; the domain reputation chart was retired, so use the spam rate and user-reported spam graphs. Check the domain and your link domains against Spamhaus, Barracuda, SpamCop, Abusix and the URI lists. Validity's Heatwave blocklist launched on 3 September 2026; SORBS shut down in June 2024.

6. Streams. Marketing, transactional and outbound prospecting belong on different subdomains with different From addresses. A campaign that collects complaints should not be able to delay a password reset.

AMP-specific considerations

Interactive AMP email is the reason most teams choose this platform, and it carries a few delivery-specific details:

• Gmail renders AMP email, and sending requires registering your sending domain with Google. Support outside Gmail has narrowed rather than widened over time, so verify current coverage for your audience before building an AMP-only experience.
• The AMP part is an addition, not a replacement. Every message still needs a complete HTML part and a plain-text part. Clients that do not support AMP fall back to the HTML, so the HTML must stand alone.
• Interactive submissions are requests from the message. Keep the endpoint on your own domain, keep it idempotent — scanners and link-preview bots will fetch your URLs — and never put an email address or a guessable identifier in the URL.
• Weight still matters. Keep the HTML part under about 100KB so Gmail does not clip the message and hide the unsubscribe link behind "View entire message".
• Interactivity does not improve placement. It improves response once the message is in the inbox. A form in a spam-foldered email is a form nobody sees.

What not to do

• Do not judge the campaign by the platform's delivery rate. Acceptance is not placement.
• Do not open a support ticket about spam placement before verifying authentication on a delivered message.
• Do not migrate platform, change subdomain and redesign templates in the same week; you lose all attribution.
• Do not import your full historical contact table during onboarding.
• Do not use a public link shortener; keep tracking on your own subdomain via CNAME.
• Do not move to a dedicated IP to escape a shared pool unless your volume is high and consistent enough to keep it warm.
• Do not test placement by mailing your own account — your mailbox has engagement history with you.

MailPilot covers the half an ESP cannot: it warms mailboxes over OAuth (Gmail, Outlook) or SMTP/IMAP — including SendGrid, Amazon SES, Mailgun, Postmark and custom SMTP — checks SPF, DKIM and DMARC against delivered mail, tracks per-mailbox reputation daily, and measures real inbox placement per provider with a seed-inbox network, so you can tell a platform problem from a reputation problem with data rather than inference.