Troubleshooting: messages delivered to the junk folder

RassamNov 16, 2026邮箱预热
Troubleshooting: messages delivered to the junk folder

This article describes how to diagnose and correct the delivery of outbound messages to the junk folder. It applies to organizations that send first-contact sales messages from their own domains and that have confirmed that the messages are being delivered but are not reaching the inbox.

Symptoms

The following symptoms indicate the condition that this article addresses.

  • The message is not returned as a bounce, but the recipient reports that it was not received.
  • The message appears in the recipient's junk folder, spam folder, or promotions tab.
  • The reply rate declines without a change to the recipient list or the message.
  • The receiving provider's postmaster data shows a low reputation rating for the domain.

Before you begin

Three delivery outcomes are frequently confused, and each has different causes.

  • A bounce means that the message was not delivered. The sender receives an error code.
  • Junk folder delivery means that the message was delivered and then classified as unwanted. The sender receives no error.
  • A block means that the receiving server refused the connection or the message during the SMTP transaction.

A 550 response indicates a rejection rather than a junk folder classification. Authentication changes will not correct a list that contains invalid or purchased addresses.

Causes and resolutions

The following table lists twelve causes, the method for identifying each cause, the corrective action, and the approximate time required for the correction to take effect.

Cause Method of identification Corrective action Time to take effect
Purchased or collected list Spam trap hits, complaint rate above 0.1 percent, sudden blocklist entry Discontinue the list and rebuild it from a verifiable source Immediate
Domain with a poor history Postmaster reputation is low before sending begins; blocklist entries appear immediately Use a new domain and establish a new history Two to six weeks
Shared IP address with unreliable senders Placement declines without any change to the campaign Move to managed or dedicated IP addresses One to seven days
SPF record missing or exceeding the DNS lookup limit Authentication fails; the headers report spf=neutral or spf=permerror Flatten the record and remove inactive include statements Hours
DKIM signature missing or invalid The signature fails after forwarding; the headers report dkim=fail Enable signing in the provider and rotate the keys Hours
DMARC record missing or not aligned No policy is published, or the policy is p=none without alignment Publish a policy with alignment, beginning with p=none and progressing to quarantine One to two weeks
Blocklisted link domain or URL shortener Content is filtered although the sending domain is clean Use the organization's own domain for links and avoid public shorteners Days
Excessive images or attachments The spam score increases with the image ratio; attachments are removed Use a text-first message with one link and send attachments only on request Immediate
Subject line and body patterns Capitalization, repeated exclamation marks, and promotional terms Rewrite the message in the form that a person would use for one recipient Immediate
Missing unsubscribe mechanism The complaint rate increases and bulk sending rules apply Add a working opt-out and a List-Unsubscribe header Days
Excessive HTML and tracking The HTML part is large, or the message contains hidden text and redirects Use a template that renders as text and reduce tracking Days
Sending behaviour A sudden increase in volume, identical content, or no replies Increase volume gradually, vary content, and remove unresponsive segments One to four weeks

Procedure: diagnose the problem

Perform the following steps in order. Changing message content before completing the first four steps usually results in no improvement, because the cause is rarely the content.

  1. Review the bounce codes. A 550 response indicates that the address or domain was rejected, a 421 or 450 response indicates throttling, and a 5.7.x response usually indicates a policy or reputation block.
  2. Verify authentication. Send one message to a seed address and examine the headers for the spf=, dkim=, and dmarc= results. Correct any failing result before continuing.
  3. Check the blocklists. Query the sending domain and the sending IP address against the Spamhaus and Barracuda lists. A single listing can explain several days of declined delivery.
  4. Review the postmaster data. Google Postmaster Tools reports domain reputation and spam complaint rate. A low reputation rating indicates a history problem rather than a content problem.
  5. Perform a placement test. Send the campaign to a seed testing service and compare inbox, junk folder, and promotions placement for each receiving provider.
  6. Compare domains and mailboxes. If one domain is affected and the others are not, the cause is specific to that domain rather than to the message.
  7. Test the content last, and change one variable at a time.

Determine whether the cause is configuration, reputation, or the list

The following classification is useful when a corrective plan is prepared.

Configuration, which can be corrected immediately: SPF, DKIM, DMARC, the unsubscribe mechanism, HTML size, attachments, and link domains.

Reputation, which requires weeks to correct: domain age, IP address history, blocklist removal, postmaster recovery, and complaint rate.

The recipient list, which can only be corrected by replacement: purchased data, collected addresses, role accounts, expired event lists, and recipients who have no reason to expect the message.

Most organizations that report a delivery problem have a list problem. Authentication changes do not correct a list that contains spam traps.

What a sending platform can and cannot resolve

A sending platform can authenticate each domain, maintain warmed IP addresses and replace them when they are listed, enforce hourly and monthly limits for each domain, and report bounce, complaint, and placement data for each mailbox and domain.

A sending platform cannot correct a purchased list, make identical messages appear personal, restore a domain that has been unusable for an extended period, or replace the value of the offer. If the recipient has no reason to reply, delivery to the inbox does not produce a result.

ColdSend provides the authentication and the sending infrastructure described above. The recipient list and the message remain the responsibility of the organization.

About ColdSend

ColdSend includes automatic domain authentication, warmed Azure IP addresses with automatic replacement, per-domain hourly and monthly limits, and delivery reporting for each domain and mailbox. The first domain includes 100 mailboxes and 25,000 messages per month for $99, and each additional domain costs $30 per month.

Got Questions? We’ve
Got Answers

A change in behaviour or reputation is the usual cause. Examples include an increase in volume, a new segment of the recipient list, a DNS record that was lost during a provider migration, or an IP address that was added to a blocklist. Authentication and blocklists should be checked before the message is changed.

Not always, but a new domain has no reputation. A new domain that sends five messages per mailbox per day with correct authentication is normally delivered to the inbox. The same domain sending 500 messages on its first day is not.

No. Warmup establishes sender reputation by generating engagement with the sending account. It does not remove spam traps from the recipient data, and it does not create a reason for the recipient to reply. A provider that claims otherwise should be asked how warmup removes invalid addresses from a purchased list.

Configuration corrections take effect within days. Reputation recovery requires two to six weeks of consistent, low-volume sending with measurable engagement. If the domain has an extended poor history, establishing a new domain is often faster than repairing the existing one.

A message that renders as plain text is generally preferable, with one link and no image-only layout. A purely plain text message can appear unusual for a business sender, and a message with extensive HTML resembles a newsletter. The format should resemble the message that a person would send to one recipient.

You Might Also Like