Email subject line and spam: do caps and emojis hurt?

The subject line carries disproportionate weight in spam scoring because it's the part most directly designed to manipulate. Filters apply different rules to subjects than to bodies — the threshold for "all caps", "excessive punctuation", and "emoji density" is meaningfully lower in subjects. At the same time, subject-line engagement (open rate adjusted for MPP, reply rate) is one of the strongest signals filters use to assess whether the recipient wants this sender.

All-caps and the visible penalty

All-caps subject lines ("FREE TRIAL ENDING TODAY") have been a spam signal since the 1990s. They still are. From controlled testing across 18 seed mailboxes in 2025-2026:

• Fully all-caps subject: 8-12% lower inbox rate vs the same subject in title case.
• Mostly-caps with a few lowercase words: still 5-7% penalty.
• One word in caps for emphasis ("Quick UPDATE on Q4"): negligible penalty.
• Brand name capitalisation ("NASA report attached"): fine — filters recognise common all-caps proper nouns.

The penalty is also user-perception driven. Recipients consistently rate all-caps subjects as less professional and more likely to be marketing — which translates to lower open rates, less engagement, and weaker reputation signals over time.

Emojis: the count threshold

The era of "emojis are spam" is over. A well-placed emoji can lift open rates measurably (~5-10% for B2C, less for B2B). Filters score emojis on count and on category:

• Zero emojis: baseline.
• One emoji at start or end: positive engagement effect, no spam penalty.
• Two emojis: still positive on engagement, near-zero penalty.
• Three+ emojis: scored as marketing template; small penalty.
• Five+ emojis: bulk-marketing pattern; meaningful penalty.

Emoji category matters less than count. The classic "suspicious" emojis (money bags, fire, party poppers) carry slightly more bulk-marketing weight than neutral emojis (calendar, document, clock), but the count effect dominates.

RE: and FW: abuse

Adding "Re:" or "Fwd:" to a cold email subject line to fake an existing thread is a well-known cold-email hack. It worked briefly. Modern filters detect it.

How filters know:

1. Headers don't carry the In-Reply-To or References headers that real replies always have.
2. The recipient has no prior thread with this sender — Gmail and Outlook check thread history.
3. The body doesn't contain quoted prior content, which real replies almost always include.

When detected, the "Re:" prefix triggers a deception-class signal that scores worse than the original cold email would have without it. The trick is now actively harmful.

Subject length

Length affects engagement more than spam scoring directly, but engagement feeds back into reputation. Real measurements:

• Under 20 characters: highest open rates on mobile (where most opens happen). Risk of looking sparse.
• 20-40 characters: sweet spot. Renders fully on most mobile previews.
• 40-60 characters: still good. May truncate on smaller screens.
• 60-80 characters: truncated on most mobile views. Open rates drop measurably.
• 80+ characters: only the first ~50 chars matter; the rest is for filter scoring, not human reading.

The first 30 characters carry the engagement decision. Pack the message into them.

Personalisation that doesn't look automated

Putting the recipient's first name in the subject was novel in 2010. Today every spam-filter user has seen the pattern thousands of times. Filters have learned that first-name-in-subject is mildly correlated with bulk mail-merge. Engagement effect is mixed — sometimes positive, sometimes negligible, audience-dependent.

Personalisation that does help:

• Company name + specific reference: "Question about Acme's pricing tier".
• Mutual context: "Met at SaaStr last month".
• Public action reference: "Saw your launch on Product Hunt".
• Industry-specific framing the recipient cares about.

Personalisation that doesn't:

• First name only — too obviously templated.
• Job title — usually wrong from data sources.
• City — increasingly obvious as auto-personalisation.

Punctuation rules

• Multiple exclamation marks ("!!!"): minor penalty per occurrence.
• Question mark + exclamation ("?!"): no penalty.
• Multiple question marks ("????"): minor penalty.
• Dollar signs ("$$$"): noticeable penalty for stacks.
• Percent signs in financial context ("50% off"): no penalty on its own.
• Brackets [ ] in subjects: no penalty; readers actually respond well to bracketed prefix patterns.

A/B testing subject lines properly

For meaningful subject-line testing:

1. Send variants to seed mailboxes first to confirm placement parity. Inbox vs spam difference dominates any open-rate measurement.
2. Send to randomised user-list segments simultaneously, not sequentially.
3. Measure replies more than opens. MPP has destroyed open-rate accuracy on Apple devices (~50% of opens).
4. Hold the rest of the email constant. Subject test means subject test.
5. Run for 7+ days minimum to capture day-of-week variation.

Practical subject-line rules

• Title case or sentence case. Never all-caps.
• One emoji max for B2B, two for B2C.
• Never fake a Re: or Fwd: prefix.
• 30-60 characters.
• Specific personalisation, not first-name-merge.
• One question mark or one exclamation max — not both.
• Match subject to body: bait-and-switch is detected and penalised.

Frequently asked questions