MailReach Spam Test: Read and Act on Results

A MailReach spam test is a controlled inbox-placement snapshot. You send one campaign-like message to a seed list, and MailReach reports where those copies land while checking content and technical setup. The result is useful only when the sender, sending provider, tracking, links, and message match the real campaign, and it cannot prove universal delivery or replace provider reputation data.

What the MailReach spam test checks

MailReach's free email spam test gives the sender a list of controlled addresses. The sender delivers one copy of the intended message to that list. MailReach then displays three groups of results:

1. Deliverability reports inbox or spam placement for each seed mailbox.
2. Content Analysis inspects the message for visible risk factors.
3. Setup Analysis checks authentication, DNS, and blacklist signals it can detect.

The public example report says its overall score is based on where test messages land. It is an inbox-placement score, not a combined grade for authentication, content quality, or sender reputation.

That distinction should control every diagnosis. A message can pass SPF, DKIM, DMARC, and content checks while landing in spam. It can also reach the seed inboxes despite a configuration weakness that should still be fixed.

Reproduce the real sending path

A seed test answers a narrow question: where did this message from this sender, through this path, land in this panel at this time? Change the path and you change the question.

MailReach's sending-setup guidance tells users to preserve the production conditions. That means the same mailbox, sending provider, campaign tool, content, tracking configuration, links, signature, and formatting.

Before sending, record:

Do not paste campaign copy into a personal mailbox and send it manually if production uses a sequencer. The resulting headers, route, tracking, and formatting may differ enough to invalidate the comparison.

The free test works with a manual send through any provider. MailReach says scheduled automated tests require SMTP support. In either mode, inspect the generated seed list rather than assuming a fixed panel. Its marketing page mentions 30 or more mailboxes and names Google, Microsoft, and Yahoo, while the linked example inspected for this article showed 27 Google and Microsoft personal and professional seeds. Coverage can differ from the headline.

Read Deliverability as a placement snapshot

The Deliverability tab shows the provider, personal or professional mailbox type, and whether each message reached inbox or spam. Segment the result by the audience you serve.

A company selling only to business addresses should not let personal Gmail or Hotmail results hide weak Google Workspace or Microsoft 365 placement. A product targeting consumers has the opposite problem. A blended score can conceal the provider that matters most.

Use three questions:

• Did one provider fail while another passed?
• Did professional and personal mailboxes behave differently?
• Did every test message travel through the same route and arrive with the expected headers?

A good result means the tested copies reached those seed inboxes. It does not show placement for every recipient, future message, geography, tenant, or volume. Seed accounts also cannot reveal the complaint behaviour of the real audience.

Our opinion is that a perfect seed score should never be reported as a deliverability rate. It is a controlled observation with a small denominator, not a campaign outcome.

Use Content Analysis to find testable variables

The Content Analysis tab can report risky words, missing subjects or body text, links, insecure or broken links, blacklisted linked domains, text-to-image balance, tracking pixels, images, attachments, and heavy HTML.

Treat each flag as a hypothesis. MailReach itself says it cannot identify every spam-triggering word because provider filtering is contextual and changes over time. A green word scan does not certify the copy.

Start with factors that alter recipient risk or message structure:

1. Repair broken links and remove a linked domain that appears on a meaningful blocklist.
2. Replace insecure URLs and verify the final redirect destination.
3. Reduce unnecessary tracking and confirm the custom tracking domain resolves correctly.
4. Remove image-only content and oversized HTML.
5. Check whether signatures, calendar links, or unsubscribe links introduced extra domains.

Rerun after one controlled change. If links, tracking, formatting, and copy all change together, a better score will not identify which correction worked.

Read Setup Analysis without treating it as an inbox guarantee

The Setup Analysis tab checks signals such as SPF, DKIM, DMARC, reverse DNS, MX records, sending-IP and domain blocklists, and the DKIM selector it detects. MailReach's product page also names domain age among its analysis points.

These checks answer whether a record exists and appears valid from the tester's view. They do not expose every alignment detail, provider policy, shared-IP neighbour, reputation signal, or tenant-specific filter.

Authentication supports identity and anti-spoofing controls. It does not purchase inbox placement. Google's sender guidelines require authentication and valid forward and reverse DNS for relevant senders, while also pointing to spam complaints and shared-IP behaviour. Microsoft's authentication documentation likewise explains SPF, DKIM, and DMARC as anti-spoofing controls rather than inbox promises.

Fix a clear setup failure before evaluating copy. A missing DKIM signature or broken SPF policy can make later content experiments hard to interpret. After repair, send a fresh test and confirm the actual message carries the expected authentication result.

Blacklist findings need restraint. MailReach's blocklist guidance says presence on a list does not automatically cause spam placement, and MailReach cannot remove the listing. Identify the list, affected domain or IP, evidence of impact, and the list operator's official remediation process before changing infrastructure.

Run a plain-message isolation test

If the original message lands in spam while Content and Setup show no clear failure, MailReach recommends a deliberately plain control message.

Use one or two ordinary professional sentences, a natural lowercase subject, plain text, and no signature, image, URL, personalization, open pixel, click tracking, or browser tracking extension. Send it through the same mailbox, provider, IP path, and campaign tool.

Interpret the comparison:

• The plain message reaches inbox. Reintroduce the production elements one at a time. Start with the signature and necessary link, then tracking, formatting, and the original copy.
• The plain message still reaches spam. Investigate the sender, provider, IP path, custom SMTP setup, reputation, or traffic history rather than rewriting every sentence.
• Results vary by provider. Use that provider's telemetry and requirements instead of applying one global fix.

Keep volume low during diagnosis. A seed test is meant to observe a route, not to force reputation by repeated sends.

Separate the spam test from MailReach Reputation Score

MailReach also publishes a Reputation Score for its warming product. Its score documentation says the metric appears after three days of warm-up data, weights recent days more heavily, and emphasizes Google Workspace and Office 365 placement.

That score is not the one-off spam-test score. Neither metric is Google's domain reputation or Microsoft's IP reputation. Keep the names and data windows separate in reporting.

Conflating them can produce the wrong fix. A strong warm-up score cannot clear a harmful campaign link, and a good one-off seed test cannot erase a high complaint rate.

Pair seed placement with provider data

Google Postmaster Tools reports on mail sent to personal Gmail accounts. Its dashboards cover user-reported spam rate, IP and domain reputation, authentication, and delivery errors when enough volume exists. The data is delayed and can be unavailable at low volume.

For Microsoft consumer mail, use the Outlook.com Postmaster guidance and Smart Network Data Services where you control the sending IP. Microsoft identifies IP, domain, authentication, list accuracy, complaints, content, and other factors in filtering.

A complete diagnosis combines:

• seed placement from the real campaign path;
• message headers and authentication results;
• provider reputation, complaints, and delivery errors;
• campaign bounces, replies, and unsubscribe activity;
• a change log showing what was altered between tests.

No single dashboard supplies all five.

Need a controlled deliverability test?

LeadHaste can reproduce the campaign path, isolate content from infrastructure, and document each change against seed placement and provider telemetry before production volume moves.

Book your free discovery call →