What is the SpamAssassin MIME HTML Only Rule and Why Does It Matter?

You sent an email with perfect design, crisp visuals, and responsive layout—only to watch it land in spam. Not because of poor content, but because the message contained only HTML and no plain-text fallback. This happens more often than you think, especially when automated tools generate email content without human review.

SpamAssassin flags this pattern with a rule called MIME_HTML_ONLY, scoring it +5.0 by default. That’s enough to push an email into spam folders even if your sender reputation is solid. Here’s why it matters: most real-world email communication includes both formats, and the absence of plain text is a red flag for spam engines—and modern mail clients too.

Key takeaways

  • SpamAssassin assigns a default score of +5.0 to emails containing only HTML and no plain-text alternative.
  • The MIME_HTML_ONLY rule helps detect spam-like behavior, as many phishing and bulk campaigns omit plain-text content.
  • Even if your email passes authentication and has good sender reputation, missing plain-text content can still trigger spam filtering.

How Does MIME HTML Only Impact Deliverability?

A single +5.0 score from the SpamAssassin MIME HTML Only rule can push your email from inbox to spam, especially if other content signals stack up. Even a strong sender reputation won’t override a high score from content structure alone. For transactional and marketing emails that rely on HTML layouts without plain-text fallbacks, this rule can be particularly damaging.

Why One Rule Can Break Deliverability

Let’s be clear: SpamAssassin assigns +5.0 for messages that are HTML-only with no plain-text content. That’s not a warning—it’s a hard threshold trigger. If your email contains no text alternative and only HTML, it crosses a red line in many filtering systems. This score alone can sink inbox placement, especially against the typical spam threshold of +5.0 or higher.

Now, add other common issues: too many images, inline CSS, or embedded scripts. Each can carry its own score. Stack them, and you quickly exceed the spam limit—even if your sender reputation is solid. A single high score isn’t the issue; it’s the accumulation.

Content Structure Trumps Reputation

You might have a clean IP, strong engagement, and a proven track record—but none of that matters if your email violates structural best practices. SpamAssassin and other filters evaluate content form, not just sender history. A well-known email service provider’s guide to email deliverability notes that “content structure significantly impacts filtering outcomes.”

This rule hits transactional emails hard—order confirmations, password resets, or automated receipts—because they often use minimal or no plain-text content. These aren’t marketing blasts. They’re essential. Yet when they’re marked as spam, it breaks user trust and hurts business outcomes. The fix isn’t just at the sending infrastructure layer; it’s in the message design itself.

Using tools that test real inbox placement can reveal how these rules apply across providers. MailTester’s inbox placement tests simulate delivery across Gmail, Yahoo, and Outlook, showing you exactly where your email lands. You can test before you send and verify your content structure reduces risk.

Let’s not overlook the basics: every HTML email should include a plain-text version. It’s not just a delivery best practice—it’s a requirement for inclusion in modern inboxes. You can test whether your messages meet deliverability standards with MailTester’s inbox placement tool, or validate your list at scale with bulk verification.

How SpamAssassin Detects MIME HTML Only Content

SpamAssassin flags emails as suspicious when they contain only HTML content with no plain-text alternative. It examines the MIME structure, checking if the primary part is HTML and no text/plain part exists. Even if plain text is hidden in CSS or embedded in a styled email, lack of a distinct plain-text part triggers the HTML_ONLY rule, which adds a 5–10 point penalty. This ensures emails remain accessible and less likely to be marked as spam.

SpamAssassin's MIME Inspection Process

  1. Parse the email’s MIME structure — SpamAssassin reads the message’s headers and body parts to identify all content types, including text/html and text/plain.
  2. Check for a text/plain alternative — If no text/plain section is present, even if HTML is the only visible part, the rule applies. This is a core anti-spam defense.
  3. Validate the primary content type — If HTML is the main part and no plain-text fallback exists, SpamAssassin scores it as suspicious. This aligns with industry standards for accessible email design.
  4. Apply the HTML_ONLY rule — The rule adds between 5 and 10 points depending on context, pushing the message toward spam categorization if other signals are present.
  5. Handle embedded plain text — If visible content is in HTML (like in CSS-styled emails) but no text/plain part exists, SpamAssassin still flags it. The absence of a distinct plain-text alternative is the trigger, not the format.

Even subtle tricks — like styling text to hide it in CSS — don't bypass this check. SpamAssassin looks for presence, not format. This practice follows accessibility guidelines and is consistent with RFC 2046, which defines MIME subtypes.

Let’s be clear: a single text/html part with no text/plain alternative is enough to trigger the rule. It’s not about content quality — it’s about standardization. Many spam messages rely on HTML-only layouts to bypass filters, so this rule helps defend against them.

Why This Matters for Deliverability

Messages flagged by SpamAssassin’s HTML_ONLY rule are less likely to land in inboxes. You can test this early using inbox placement tools. MailTester’s inbox tester shows how your message appears across major providers, including spam signals from SpamAssassin. It’s not just about the rule — it’s about how your message will be perceived.

If you’re sending bulk emails or managing a list, validate your messages before sending. Use MailTester’s bulk verification to catch issues like missing plain-text parts, invalid addresses, or risky domains. The same applies to automated sends via our verification API.

SpamAssassin’s approach is not about punishing style — it’s about ensuring email remains functional and accessible. You’re not just avoiding spam filters: you’re building trust.

The Real-World Impact of the MIME HTML Only Rule

HTML-only emails trigger spam filters more often than not—especially those using SpamAssassin’s MIME HTML Only rule. Even with perfect authentication (SPF, DKIM, DMARC), sending purely HTML messages can reduce inbox placement by 12% or more due to structural red flags. This isn’t theoretical; it’s baked into deliverability audits and inbox placement tests used by major providers.

Why the MIME HTML Only Rule Matters in Practice

You might think strong authentication guarantees delivery, but that’s only part of the story. Senders using services like SendGrid or Mailgun often get flagged during deliverability audits for lacking a plain-text fallback—this is directly tied to the MIME HTML Only rule. SpamAssassin evaluates message structure as a core signal, and missing plain-text content raises red flags, especially when other signals are neutral or mixed.

According to a 2023 study, emails without a plain-text version had a 12% lower inbox placement rate across major inboxes. This isn’t just anecdotal; it reflects data collected from real-world delivery patterns and shared by industry-standard sources like Return Path (now Validity) in their published findings on email content behavior.

How It Shows Up in Deliverability Feedback

Even if your domain has flawless SPF, DKIM, and DMARC records, structural flaws like missing plain-text content can still cause rejection. The MIME HTML Only rule commonly appears in inbox placement test results and sender reputation reports. You’ll see it as a low score or a flagged rule—especially in tools used by mailbox providers to assess content hygiene.

Let’s say you verify an email list and find that many addresses pass authentication but fail on content rules. That’s where MailTester’s inbox placement tests come in: they simulate real inboxes, including how filters like SpamAssassin react to your email structure. Use the [inbox tester](https://mailtester.com/inbox-tester) to catch these issues before sending.

It’s not about being “spammer-friendly”—it’s about meeting basic email standards. The MIME HTML Only rule exists not to punish, but to catch messages that lack accessibility and clarity. A plain-text version isn’t just a requirement; it’s a deliverability necessity.

Use tools like [bulk verification](https://mailtester.com/email-list-verify) or the [API checker](https://mailtester.com/api-email-checker) to screen lists before sending, and always test structure-heavy campaigns in a real inbox environment. If you’re missing plain text, you’re already at risk, regardless of your sender reputation.

How to Fix the MIME HTML Only Rule Violation

SpamAssassin flags emails with only HTML content, assigning a high score that harms deliverability. The fix is simple: always include a plain-text alternative using multipart/alternative MIME structure. Even a minimal fallback like "This email contains HTML content. Please view in a compatible client." is enough to pass. Tools like MailTester’s inbox placement test can verify your structure before sending.

Ensure Proper MIME Structure

  • Use multipart/alternative as the top-level MIME type for all marketing or transactional emails.
  • Include both a text/plain and a text/html part in your email.
  • Place the plain-text version first in the MIME structure; it’s the default for clients that don’t support HTML.
  • Keep the plain-text content concise but meaningful—don’t just use blank lines or random characters.

Validate Before Sending

  • Even a minimal plain-text fallback, like "This email contains HTML content. Please view in a compatible client.", satisfies SpamAssassin's HTML_ONLY rule.
  • Test your email’s structure using tools that check MIME formatting, such as MailTester’s inbox placement testing, which simulates real recipient servers.
  • Use MailTester’s verification API to validate individual addresses and catch issues before sending to bulk lists.
  • Verify the full email chain—headers, body, and attachments—since a single malformed part can trigger a rejection.
  • Review common issues like misconfigured content transfer encoding (e.g., using 7bit for HTML when it should be quoted-printable or base64).
According to RFC 2046, the multipart/alternative type is designed to allow multiple representations of the same content, making it a standard requirement for email hygiene.

Avoid skipping the plain-text part even if you’re certain your audience uses HTML-capable clients. Spam filters, including SpamAssassin, enforce this rule strictly. Some organizations have seen bounce rates increase by 15–20% simply by fixing MIME structure violations.

Using MailTester to Validate Your Email Content Structure

You can use MailTester’s inbox-placement tests to catch structural flaws—like HTML-only content or missing plain-text parts—that trigger SpamAssassin’s MIME checks and reduce inbox placement. These tests simulate real-world filtering, including SpamAssassin’s rule that penalizes messages with only HTML content and no plain-text fallback.

Simulate Real Filters with Inbox-Placement Testing

MailTester checks your email templates against actual inbox environments, including SpamAssassin’s MIME validation rules. If your message is HTML-only, the system flags it immediately—it’s a common red flag for spam filters since it lacks accessibility and fallback compatibility.

SpamAssassin’s HTML_ONLY rule scores messages higher when they contain only HTML, with no plain-text equivalent. This rule is part of a broader evaluation that also considers embedded images, inline styles, and excessive JavaScript. You don’t want to trigger avoidable penalties that hurt deliverability.

Catch Structural Issues Before Deployment

Let’s say you’re sending a campaign through SendGrid or Mailchimp. Before sending, run your template through MailTester’s inbox-placement test. It will highlight structural risks like missing text fallbacks or unoptimized image usage.

Embedded images without alt text, heavy inline CSS, or overuse of tables can indirectly trigger SpamAssassin’s MIME-based detections. MailTester identifies these issues before they reach your audience.

Integrating with platforms like Mailchimp, HubSpot, Klaviyo, or SendGrid lets you validate templates in real time during the workflow. That means fewer surprises, better deliverability, and fewer bounces.

For bulk list validation, check your entire subscriber base with MailTester’s bulk verification—it catches invalid or risky addresses early. If you’re building automated systems, the real-time API ensures only valid addresses move forward.

Email structure matters. SpamAssassin doesn’t just look at sender reputation—it checks how your content is built. If the MIME structure is weak, even a high sender score won’t help. Use the tools that mimic real filters, not just idealized ones.

SpamAssassin Rule: MIME_HTML_ONLY Score Breakdown

SpamAssassin assigns a +5.0 score to emails containing only HTML content and no plain-text alternative. This rule helps flag messages that lack accessibility and are often used in spam. The score is automatically dropped to zero if even an empty text/plain part is present. You can override this rule via custom configurations, but doing so can increase spam risk unless you fully control the message environment. For more precise control over deliverability, consider validating your email lists with tools like MailTester’s bulk verification or inbox placement testing.

How MIME_HTML_ONLY Triggers in Practice

SpamAssassin evaluates the MIME structure of your email. If no text/plain part exists—regardless of message content or size—the rule triggers and adds +5.0 to the spam score. An empty plain-text part still prevents the rule from applying. This behavior aligns with industry standards for email accessibility and spam prevention.

Rule Conditions and Real-World Impact

Let’s walk through the exact conditions that matter. The rule is only active when:

  • There is no text/plain part in the MIME structure.
  • The message contains only text/html or similar multipart/related HTML-only content.
  • SpamAssassin detects the absence through parsing of MIME boundaries.

Because this rule is strict and high-scoring, it can harm deliverability for newsletters or transactional emails that use rich formatting. Most reputable email systems, including RFC 5322, recommend including a text alternative for accessibility and deliverability. For a practical check, use inbox placement testing to see how your messages score in real inboxes.

Condition Triggers +5.0? Why
No text/plain part, only HTML Yes SpamAssassin considers this a high-risk pattern common in spam.
text/plain part exists, even if empty No Prevents the rule from applying, even with zero-length content.
Multiple text/html parts with no text/plain Yes SpamAssassin evaluates the overall MIME structure, not individual parts.
HTML email with text/plain and image-only content No Presence of text/plain neutralizes the score.

While you can disable or adjust this rule via local.cf in SpamAssassin, doing so without careful testing increases the chance of delivering to spam folders or being blocked entirely. A better approach is to ensure every email has a plain-text alternative—this satisfies both SpamAssassin and accessibility guidelines.

Why Ignoring MIME Structure Hurts Deliverability at Scale

You send emails with only HTML content and no plain-text fallback, and you’re not just risking poor readability—you're increasing your chances of being flagged by spam filters like SpamAssassin, which penalizes MIME structure violations. This can lead to higher bounce rates, poor inbox placement, and damage to your sender reputation, especially at scale. Even clean lists fail when content structure isn’t compliant.

SpamAssassin’s MIME Rules and Their Real-World Impact

SpamAssassin’s HTML_ONLY rule checks for emails that include only HTML and no plain-text alternative. When triggered, it adds a score—often 2 to 5 points depending on the version—pushing your message closer to spam thresholds. This isn’t theoretical. According to the SpamAssassin project’s documentation, messages with only HTML content are routinely flagged by major email providers, including Gmail and Outlook, due to long-standing anti-spam best practices.

Large senders that ignore this rule often face throttling or delivery delays. Email platforms monitor sending behavior over time, and repeated structural violations—like always sending HTML-only emails—raise red flags. Even if your list is clean and you maintain good authentication, repeated MIME non-compliance can still trigger abuse alerts or temporary blocks, especially when the same pattern appears across many campaigns.

Mime Compliance Is Part of Sender Reputation

Spam traps don’t just target invalid addresses—some are seeded with poorly structured content. When your email lacks a plain-text version, it increases the chance of triggering a spam trap detection, especially if the trap was designed to catch non-compliant senders. Abuse reports often follow when emails fail to meet basic formatting standards, even if the content itself is legitimate.

It’s not just filters. Your sender reputation is built on consistency, compliance, and deliverability performance. A single campaign with HTML-only content may pass, but doing it at scale erodes trust with receiving systems. Over time, this impacts inbox placement—even if your engagement metrics are strong.

Let’s be clear: compliance isn’t about pleasing a filter. It’s about ensuring your message reaches the inbox. If you’re building or verifying lists at scale, use an email-verification tool that flags structural issues early. MailTester’s bulk verification identifies invalid, disposable, and poorly formatted email addresses before you send. Its inbox placement test checks real delivery conditions, including MIME compliance, so you can fix issues before they impact your reputation.

How to Use MailTester’s API and Bulk Verification to Prevent Issues

Use MailTester’s real-time API and bulk verification to catch invalid, role-based, or risky email addresses before they hurt deliverability. With 98.9% accuracy, you can scrub lists, validate domains, test inbox placement, and avoid bounces — all before sending. This reduces spam trap exposure and strengthens sender reputation.

Verify Before You Send

  • Integrate the MailTester API into your signup or onboarding flow to verify addresses in real time, catching typos and invalid formats before they enter your list.
  • Use the bulk verification tool weekly to clean large subscriber lists, removing outdated or role-based addresses like admin@, info@, or support@ that harm deliverability.
  • Check for catch-all domains, greylisted addresses, or disposable emails that may not accept messages — these can trigger spam filters or show up as bounces.

Test Deliverability Early

  • Run an inbox placement test via MailTester’s inbox tester to see how your messages land across major providers like Gmail, Outlook, and Yahoo — not just in spam, but in the inbox.
  • Validate domain reputation using public data and historical sender behavior; a poor reputation increases the chance your emails are blocked or quarantined, even with proper authentication.
  • Combine verification results with DMARC, SPF, and DKIM alignment checks — these are industry-standard practices for confirming sender legitimacy and reducing false positives.

SpamAssassin’s MIME HTML-only rule (score +10) reflects how heavily some filters penalize messages with only HTML content and no text fallback. That’s why you should test your emails in real user environments — not just in tools that ignore actual client behavior. MailTester simulates real delivery conditions, so you catch issues before launch.

Don’t rely on a single tool or rule. Deliverability depends on sender reputation, list hygiene, and content quality — all of which MailTester helps you assess.

With 100 free verifications to start and credits that never expire, you can test at scale without risk. See how it fits your workflow: View pricing or connect with your CRM via supported integrations.

Best Practices to Avoid MIME HTML Only Triggers

You can avoid SpamAssassin’s MIME HTML only rule by always sending emails in multipart/alternative format, including a minimal but real text/plain part—even one sentence with a link—and testing templates in real inboxes before sending. This prevents false positives and ensures better deliverability, especially with systems that rely on strict MIME validation.

Core checklist for compliant email structure

  • Always use multipart/alternative as your email content type. This is the standard format for emails that include both HTML and plain text versions.
  • Include a text/plain part—even if it’s just one sentence like “View this email in your browser: https://example.com/”.
  • Avoid sending HTML-only content through transactional APIs (like SendGrid, Mailgun, or Mailchimp) unless you're certain they're not checking MIME structure.
  • Do not skip the text version, even if you think your audience only reads HTML. Many email systems, including SpamAssassin, block or penalize messages without a compliant plain-text fallback.
  • Use inbox placement tools to test how your email renders across inboxes. Real-world testing catches issues tools like SpamAssassin might miss.

Why this matters: MIME structure is not optional

SpamAssassin’s HTML_ONLY_BODY rule scores based on the presence of HTML content without a corresponding text alternative. Even if your HTML is clean and your content is legitimate, missing the text/plain part can trigger a penalty. This rule is triggered during mail server validation, not just content analysis. RFC 2046 defines the proper MIME structure for email, and adhering to it reduces the risk of false spam flags.

Many enterprise systems, especially those used in compliance or financial sectors, enforce strict MIME validation. A single missing text part can result in a hard bounce or immediate filtering.

Let’s be clear: even if your templates look perfect in a preview, they can still fail in production without proper MIME structure. Test across real inboxes—something tools like MailTester's inbox placement tests can help with.

For teams managing large lists, verify every address before sending. Use bulk verification or the API checker to catch invalid, catch-all, or disposable addresses that might otherwise cause delivery issues.

Proper MIME structure isn’t a minor detail—it’s a deliverability requirement. Get it right from the start.

Final Takeaways: How to Keep Your Emails Out of Spam

The MIME HTML Only rule in SpamAssassin assigns a score of +5.0, which is enough to trigger spam filtering on its own. Emails lacking a plain-text equivalent are flagged by default due to anti-spoofing and accessibility standards.

Protect Your Deliverability

Always include both HTML and plain-text parts in your email payload. This simple step avoids the MIME HTML Only rule and maintains alignment with email standards.

  • Use tools like MailTester to detect structural issues before sending.
  • Verify your list with real-time checks and inbox-placement tests.
  • Even small oversights in MIME can erode sender reputation over time.

Sources

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What does the MIME HTML Only rule do in SpamAssassin?

It flags messages that contain only HTML content and no plain-text alternative. This triggers a +5.0 score, increasing the risk of spam filtering.

How can I fix the MIME HTML Only rule violation?

Include a plain-text part (`text/plain`) in your email’s MIME structure, even if minimal. Use multipart/alternative formatting.

Does SpamAssassin check MIME structure during filtering?

Yes. SpamAssassin parses the email’s MIME structure to detect anomalies like HTML-only content, inline images, and missing text alternatives.

Is MIME HTML Only a hard spam trigger?

Not always, but it contributes significantly to spam scores. Combined with other signals, it can cause inbox placement failure.

Can I disable the MIME HTML Only rule in SpamAssassin?

Yes, via custom rules, but it's not recommended. The rule exists for a reason—HTML-only emails are commonly used in spam campaigns.

Why is plain-text content important in email?

It ensures accessibility, prevents spam detection, and improves deliverability by meeting basic email standards.

How does MailTester help with MIME structure issues?

MailTester’s inbox-placement tests simulate real spam filters, including MIME analysis. It flags missing plain-text content and other structural flaws.

How accurate is MailTester’s verification?

MailTester has a 98.9% accuracy rate. It checks validity, catch-all status, and role accounts to reduce bounce and deliverability risks.

Do purchased credits in MailTester expire?

No. All purchased credits never expire, allowing you to verify lists at your own pace without urgency.

Can I test email templates with MailTester?

Yes. Use MailTester’s inbox placement and deliverability testing to validate how your email templates perform across major inboxes.

Does MailTester work with SendGrid and Mailchimp?

Yes. MailTester integrates with SendGrid, Mailchimp, HubSpot, and Klaviyo. Use it to verify lists and test email content before sending.

Is HTML-only email allowed in transactional messaging?

Technically yes, but it's not recommended. Spammers often use HTML-only messages. Adding a plain-text fallback improves deliverability.