BrandJet AI
    HomePricing
    Contact us
    Get Started
    Quickstart
    Email Outreach
    Email Infrastructure
    Connect Email Accounts
    Campaigns & Sequences
    Why test emails are not arrivingPersonalization variables pulled the wrong dataTimezones, schedules and sending windowsTemplates library: reusable sequences and message templatesSequence Assistant: AI-drafted multi-step sequences
    Deliverability & Analytics
    Social & Multichannel
    Connect Social Channels
    Multichannel Campaigns
    Leads
    Find & Enrich Leads
    Import & Manage Lists
    Recurring Lead Collection
    Billing & Workspace
    Plans, Trials & Limits
    AppSumo, BYOK & Upgrades
    Workspace, Team & Account
    Replies & Unibox
    Unibox & Snippets
    Workflows
    Workflow Builder
    Lifecycle Sequences
    Artemis (AI Assistant)
    Getting Started with Artemis
    Troubleshooting Artemis
    Integrations & Developers
    MCP Server
    REST API & Webhooks
    CRM Integrations
    Slack, Discord & Notifications
    Monitoring & Intelligence
    Mentions
    Competitor & Social Tracking
    Content Feed & Website Analytics
    AI / LLM Monitoring
    Press & PR Tools
    Press Outreach
    AI Agents
    Agent Types & Setup
    Help Center/Email Outreach/Campaigns & Sequences

    5 min read

    Why test emails are not arriving

    Test sends from a campaign use the exact same sending pipeline as live sends — same inbox, same warmup score, same throttling. That means most missing test email issues are real deliverability signals worth paying attention to.

    Step 1 — Check the obvious places first

    • Spam, Promotions, and Junk folders in the destination inbox.

    • Any aliases or forwarding rules on the destination domain.

    • The activity log inside the campaign — every test send shows there with status Sent, Failed, or Skipped.

    If the activity log says Sent, the inbox accepted the message and the issue is on the receiving side (spam filter, alias, or forwarding). If it says Failed, keep going.

    Step 2 — Look at the failure reason

    Click the failed test in the activity log to see the SMTP response. The most common failures are:

    • 5.7.x — message blocked: domain reputation is poor, or DKIM and DMARC fail. See the article on DNS records.

    • 5.4.1 — recipient address rejected: the destination does not exist or the catch-all is off. Try a different email.

    • OAuth revoked or token expired: the sending inbox needs to be reconnected.

    • Daily limit reached: warmup is still ramping. Test from another inbox or wait until the next sending window.

    Step 3 — Test from the right inbox

    By default, BrandJet picks one of the campaign sending inboxes for the test. If you have several inboxes and one is unhealthy, pick a specific inbox from the test dialog instead of letting the system rotate.

    Step 4 — Send to your own address (correctly)

    • Do not send tests from inbox X to inbox X — Gmail and Outlook often hide self-sent mail in Sent rather than Inbox.

    • Use a personal Gmail or Outlook account, not the same domain you are sending from.

    • Add a placeholder lead in your test list with your real address to verify variable rendering end to end.

    Step 5 — Check variables

    If the test send started but never completed, look for unresolved variables like {{firstName}} in the body. A missing required variable can cause the message to be skipped with status Missing personalization data. Set fallbacks in the sequence editor for any variable that might be empty.

    Still nothing?

    Open a support ticket with the campaign name, the inbox you tested from, and the timestamp of the test. We can pull the SMTP log line for that exact attempt.