RocketsSend.com logoRocketsSend Docs
RocketsSend.com logoRocketsSend Docs
HomepageRocketsSend DocumentationGetting Started
RS Email Verifier OverviewFeaturesValidation MethodsInstallation, License, and PlansSingle VerificationBatch VerificationResults and Risk ScoresProxy PoolRulesReports and ExportSettings, Updates, and Troubleshooting
RS Email Verifier

Batch Verification

Import TXT or CSV lists, control long-running tasks, filter outcomes, and recover safely.

Batch verification processes a list incrementally while keeping progress, speed, status, and controls visible.

Batch verification task

Prepare the file

  • Use TXT when each line contains one email address.
  • Use CSV when addresses are part of a structured dataset.
  • Keep a header row in CSV and note the email column.
  • Save a source copy before cleaning or deduplicating the file.
  • Import only data you are permitted to process.

Create a task

  1. Open Batch Verification.
  2. Import a TXT or CSV file.
  3. For CSV, map the email column.
  4. Review the detected records and import summary.
  5. Choose Basic, DNS, or SMTP PRO.
  6. Review concurrency, timeout, and proxy settings.
  7. Start the task.

Start with a small sample when using a new environment, proxy pool, or SMTP PRO.

Control a running task

  • Pause stops scheduling new work while the application preserves current state.
  • Resume continues a paused task.
  • Stop ends the task; review completed records before deciding whether to create a replacement task.

Do not force-close the application during an active write if a normal pause or stop is available.

Review and filter

Use status, score, reason, domain, and other available filters to inspect the list. Common audience policies include:

  • exclude invalid records;
  • hold unknown records for retry after network recovery;
  • separately review risky categories;
  • keep an audit export before creating a narrower sending audience.

Batch-pattern signals

After each address completes the selected method, the batch engine can add clustering signals found across the list. A stronger batch signal can change the result to risky. These signals help surface generated or structurally unusual groups that are difficult to identify from one record alone.

Task history and recovery

Task history preserves the task’s state and completed results. After a restart, open history first and inspect whether the existing task can continue before importing the source again.

If a task has many unknown records, diagnose the shared cause—DNS, proxy, port access, or destination throttling—before retrying. Exporting an unknown subset avoids rechecking completed valid or invalid records.

Next: filter and export results.

Single Verification

Verify one address and interpret its status, reason, and network evidence.

Results and Risk Scores

Understand statuses, representative scores, risk details, and the separate list-quality formula.

Table of Contents

Prepare the fileCreate a taskControl a running taskReview and filterBatch-pattern signalsTask history and recovery