Help Center
Docs

Cold Outreach Troubleshooting

Resolve paused mailboxes and campaigns, stalled sequences, warnings at launch, leads a campaign did not add, import rejections, and an exhausted cold-send meter

A Mailbox Is Paused or Takes No New Leads

Find the cause, fix it, then resume a paused mailbox.

The Mailboxes tab shows why a mailbox paused, or why it takes no new leads. Match the reason to the fix:

  • Bounce rate over 2%: remove the addresses that bounced from the list, then resume. Resume shows the cause and asks you to confirm it. A clean, recently sourced list keeps the rate down.
  • Provider blocked messages: a mailbox provider blocked emails from this mailbox as possible spam. The pause ends on its own at the time the card shows. Before it does, review the step content and the list. You can resume early by confirming the cause. The recipients are not suppressed. See Provider Block Pause.
  • Your email provider limited sending: the mailbox reached its sending limit at your email provider, which counts every email the mailbox sends, from Laureo and from anywhere else. The pause ends on its own. If a warm-up tool or another app sends from this mailbox, stop it or slow it down. The alert names the mailbox.
  • Rate limited: the provider throttled the mailbox. Laureo backs off and resumes automatically; no action needed.
  • Token expired: the person who connected the mailbox reconnects it to refresh the connection.
  • Setup required, with a red DNS finding on the card such as No SPF record found: the domain of the mailbox has a DNS problem that stops new leads. This is not a pause. The mailbox takes no new leads, and emails to leads it already contacted keep sending. When the daily or pre-launch check finds the problem on a mailbox that passed before, its owner and your admins get the alert New leads stopped on a cold mailbox. A paused mailbox cannot resume until the check passes. Fix the record at your DNS host, press Re-check now on the mailbox card, then resume the mailbox if it is paused. See Domain Setup.

Reading the cause. While a mailbox is paused, a line under its card header names the cause and what ends it. Paused: provider blocked 2 messages · resumes in 23 h ends on its own. Paused: bounce rate 4% · acknowledge to resume waits for you to confirm the cause. Paused by you resumes on one click. Pressing Pause sending on a mailbox the system already paused keeps the system pause, so Resume still asks you to confirm. After a provider block or a sending limit pause, the badge reads Recovering: the mailbox sends half its daily cap for 48 hours, then 3 more each day. That is the safety net working, not a fault.

Replies while a mailbox is paused
A pause you set holds only new cold steps: replies from prospects still arrive in your inbox, and you can still answer them. A pause Laureo sets also holds your replies from that mailbox until it resumes.

Provider Rejection Codes

What common SMTP status codes mean, and the fix for each.

When a provider rejects or defers a send, it returns an enhanced status code. The Mailboxes tab and the health strip translate the code into plain language and a fix. Codes that start with 4 are temporary and usually clear on their own; codes that start with 5 are permanent and need a fix before sends succeed.

  • 4.7.23 / 4.7.26 / 4.7.27: authentication deferrals. Your domain’s SPF or DKIM did not pass or align. Check the DNS result on the mailbox card, fix the record at your DNS host, then press Re-check now.
  • 4.7.28: the provider is temporarily rate-limiting your domain. This clears as sends slow down. Keep lists clean and let the managed ramp pace the volume.
  • 5.7.26 / 5.7.515: permanent authentication failures. SPF or DKIM does not align with your sending domain, or the mailbox does not meet the provider’s sender-authentication requirements. Fix SPF, DKIM, and DMARC at your DNS host, press Re-check now on the mailbox card, then resume the mailbox if Laureo paused it. Then press Resend on the campaign page: the resend a day later skips these refused emails.
  • 5.7.1: the receiving server blocked the message for policy reasons. Confirm authentication passes, then resume.
  • A block of your outgoing mail: the provider says it blocked the message as possible spam, often with a link to its own help page. Laureo records the email as blocked, not bounced, and the recipient is not suppressed. Blocks to more than one recipient in a short time pause the mailbox for a while; see Provider Block Pause.
  • Relay access denied, or no mail server for the domain: the recipient’s domain cannot take mail. This is not a mailbox problem. The lead is marked bounced and suppressed, and the other leads at that domain can be held back; see Domains That Cannot Receive Mail.
  • 5.1.8 / 5.7.708 / 5.7.750: your email tenant restricted the sending address or blocked the domain. Resolve it with your email admin before resuming.
  • 5.1.1 / 5.4.1: the recipient address does not exist or was rejected. This is a bad address, not a mailbox problem. The lead is suppressed automatically.
  • 4.2.2 / 5.2.2: the recipient’s mailbox is full. This is on the recipient’s side, so no mailbox action is needed.
Unknown codes fall back gracefully
If a rejection carries no recognized code, the mailbox still shows its plain pause reason, such as high bounce rate or sending limit reached. You never lose the reason, you just get a sharper one when the provider gives us a code to read.

A Sequence Is Not Sending

Common reasons a launched sequence sits quiet.

  • Daily limit reached: every mailbox hit its daily limit. The limit counts your workspace's calendar day, so sending resumes on the next day when the send window opens. Connect another mailbox to add room.
  • Outside the send window: leads are in time zones where it is currently outside business hours. Sends resume when their window opens.
  • Leads suppressed: the remaining leads are on your suppression list and were skipped. Import fresh leads.
  • No active mailbox: the sequence depends on a mailbox that is paused or disconnected. Resolve the mailbox or add another.
  • Campaign ramp: the lead rows read The campaign ramp reached its limit for this mailbox today. The campaign has sent its ramp allowance for today on that mailbox, and it sends more on the next sending day. Nothing needs fixing. See Campaign Ramp.
  • The campaign ramp is held: replies stayed low or too many emails bounced, so the campaign ramp keeps its level today instead of climbing. It climbs again once the numbers recover. See Campaign Ramp.
  • Outside sending or Recovering on a mailbox badge: mail the mailbox sent outside Laureo in the last 24 hours counts against its daily limit, or the mailbox is back from a pause at a lower cap. Campaigns send what is left.
  • A refused first email: the lead row reads Waiting on you: the first email to this lead was refused by your email provider. Resend it, or stop the lead. Its follow-ups wait until the first email is sent again. See Refused Emails and Step Holds.
  • A follow-up with nothing to reply to: the lead row reads Waiting on you: the earlier email this follow-up replies to could not be found in the sending mailbox. Check the mailbox, or stop the lead. The follow-up waits and looks for the earlier email again each time it is due, so reconnect the mailbox if it was disconnected.
  • An address not checked yet: when the campaign skips catch-all and unknown addresses, a first email to an address the check has not reached reads Waiting: the address has not been checked yet. It waits up to a day after the lead enrolls, sends once the check confirms the address, and stops if no answer comes.
  • The campaign is paused after bounces or mailbox pauses: see the next section.

A Campaign Was Paused After Bounces or Mailbox Pauses

The system paused a campaign whose bounces climbed or whose mailboxes stopped at once.

When a campaign's hard bounces climb, or several of your mailboxes are paused by the system at once, Laureo pauses the campaigns involved. The person who created the campaign and your admins get Campaign paused after bounces or mailbox pauses, and the alert names the cause. Clean the list for a bounce cause, or check the paused mailboxes for the other one. Then someone with access to every campaign resumes it and confirms the cause. Teammates with access to their own or their team's campaigns only cannot resume it. The rules are in Automatic Campaign Pause.

Warnings at Launch

Every warning is advice. None of them stops a launch.

Review and launch can list warnings beside its checks, such as Campaign ramp is off, Mailbox not used recently, Mailbox shared with another campaign, Formatted email where plain text is set, Unconfirmed addresses are skipped, Link in the first email, No opt-out sentence, and one row for each opt-out switch that is off. Each one is advice: the campaign launches either way, and nothing is changed for you. A launch also does not wait for address checking, and the list page shows the check as Verifying with the count done so far. When the campaign skips catch-all and unknown addresses, a first email to a lead not checked yet waits up to a day for the check; otherwise it is sent as before. See Content Checks and Compliance.

Fewer Leads Enrolled Than I Imported

Two different subtractions, each with its own panel.

A list can hold fewer leads than your file had rows, and a sequence can enroll fewer leads than the list holds. They are two different things. The import result on the list page names every row your file lost and why. The attach summary in the builder reads “Ready to enroll: 1 of 5” and lists one line for every reason underneath, so the four that are missing are named rather than counted. Neither of those is a send count: the tiles on Analytics follow the Sequence picker in the page header, which opens on the most recently updated campaign that has sent inside the range you are reading, falls back to All sequences when nothing has sent in that range, and names the scope in force in the caption underneath.

No lead is ever skipped for having been contacted recently. There is no such rule. A lead that stayed in an older list is a lead still active in another campaign, and the review panel says so: the line reads Active in another campaign, and it names that campaign and the step the lead is on underneath whenever it can resolve them. Whether those leads are held back at all is a setting on the campaign, so you can add them anyway on a campaign where that is what you want. Back on the list itself, a lead the last launch passed over carries the reason on its own row, in the Sequence column. What every other skip reason means is in Leads & Import. For a launched sequence, the address-by-address view of who was enrolled and who was passed over is the Recipients drawer in Analytics.

A campaign adds only leads whose status is Active, unless one of its switches says otherwise. A lead that is paused, has replied, has unsubscribed, has bounced, was suppressed earlier or was already promoted to the CRM is not added, and its status on the list is the reason. Before you launch, Review and launch counts these leads under the Leads line, one row for each status, and a row at 0 still shows: Paused leads, Unsubscribed or suppressed, Bounced or reported as spam, Already replied, Suppressed earlier and Promoted to a contact. Paused leads come back with Resume these leads on their row. Replied and promoted leads join only when the campaign setting Also contact leads who already replied or Also contact leads already added to the CRM is on. Each one is a switch on its row. If that row shows no switch, the panel cannot show or change that setting yet, and those leads join only if the assistant turned the setting on for this campaign. When the notice that an enrolment finished has an exact count, it names these leads too, for example: Not added: 2 had already replied. The rows and the switches are explained in Leads & Import.

Import Rejections

Why some rows did not import.

After an import, Laureo reports how many rows were imported and how many were skipped, with reasons: duplicate addresses, matches to existing customers, suppressed addresses, do-not-contact entries, or malformed rows. These skips are protections, not errors. Every skipped row is listed with its address under the reason that caught it, so you can act on the file rather than guess. Review the reasons, fix any genuinely bad rows in your file, and re-import. If the whole import was rejected, the most common cause is a missing list-source attestation.

The Cold-Send Meter Is Exhausted

What happens when you reach your monthly cold-send volume.

Cold sends are counted against an enforced monthly ceiling, and that ceiling is per user: on Ultra it is 7,500 cold emails per month per user, so the figure on your meter is your own allowance and every teammate has their own. This is a hard ceiling. Unlike the warn-only campaigns meter, the cold-send meter stops new cold sends once you reach it. When it is exhausted, in-flight sequences defer their remaining sends to the next monthly reset, you get a single notification, and a launch attempt is blocked on the meter gate.

Replies always send, even at the ceiling
Reaching the monthly cold-send ceiling never stops you from replying to prospects who already answered. Cold replies in your inbox are never counted against the meter, so the conversations that matter most keep moving.

Where Notifications Appear

How Laureo tells you something needs attention.

Cold Outreach posts to your normal notifications. A mailbox auto-pause, for bounces, for a provider block or for a sending limit, a notice from your email provider about a mailbox's sending limit or about mail it sent outside Laureo, a campaign step on hold, a campaign paused after bounces or mailbox pauses, an exhausted meter, or a sequence blocked at launch all surface in the notifications inbox (and to org admins for mailbox-health events). Your email provider's notices come at most once a day for each mailbox and each kind of notice. An alert about a pause stays unread after the pause ends, until you read it. Keep an eye on the bell so a paused mailbox does not quietly stall a sequence. See Notifications Inbox.