InboxIssue

Spam Tests

Create and manage email deliverability tests

Spam Tests

Spam tests are the core feature of InboxIssue. They allow you to test email deliverability across multiple providers.

Test Types

InboxIssue supports several ways to create tests:

TypeDescriptionBest For
ManualCreated from the dashboardAd-hoc testing
APICreated via REST APIAutomated workflows
SlackCreated via /inboxissue commandTeam collaboration

Creating a Manual Test

  1. Navigate to Spam Tests in the dashboard
  2. Click New Spam Test
  3. Configure test options:
    • Name - Descriptive name for the test
    • Provider Types - Consumer, Business, Protected
  4. Click Create

Test Lifecycle

graph LR
    A[Created] --> B[Pending]
    B --> C[In Progress]
    C --> D[Complete]
    C --> E[Expired]
StatusDescription
CreatedTest created, awaiting email send
PendingWaiting for first result
In ProgressSome results received
CompleteAll results received
ExpiredTimeout reached (60 minutes)

Provider Selection

Consumer Providers

Free email services used by individuals:

  • Gmail
  • Yahoo Mail
  • AOL
  • Outlook.com (Hotmail)
  • iCloud Mail

Business Providers

Enterprise email services:

  • Microsoft 365
  • Google Workspace
  • Exchange Server

Protected Providers

Mailboxes behind commercial spam filter gateways:

  • Mimecast
  • Proofpoint
  • Barracuda
  • Cisco IronPort

Tracking Key

Each test has a unique tracking key that must be included in your email:

inboxissue-12345-2024-01-15 10:30:00 UTC-inboxissue

Where to Include It

  • Subject line: "Newsletter Test - inboxissue-12345..."
  • Email body: Visible or hidden text
  • X-Header: Custom header (advanced)

Without the tracking key, InboxIssue cannot match the email to your test.

Test Results

Each test result includes:

Delivery Information

  • Folder - Inbox, Spam, or Missing
  • Delivery Time - How long until received

Authentication

  • SPF, DKIM, DMARC status
  • Composite authentication (CompAuth)

Spam Scores

  • Microsoft SCL/BCL (for Microsoft mailboxes)
  • Gmail spam indicators

Headers

  • Full email headers for debugging
  • Parsed authentication results

Bulk Testing

For testing multiple emails or templates:

  1. Create separate tests for each variation
  2. Use the API for automation
  3. Use metadata to track variations
{
  "name": "Template A/B Test",
  "metadata": {
    "template": "welcome_v2",
    "variant": "a"
  }
}

Test Limits

Test limits depend on your subscription plan:

PlanTests per Month
Free3
Starter100
Pro1,000
EnterpriseUnlimited

See Subscription Plans for details.

On this page