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

Settings, Updates, and Troubleshooting

Configure verification safely, install updates, and diagnose common DNS, SMTP, proxy, and task issues.

Application settings

Settings

Review the available application preferences before a large task:

  • language and appearance;
  • default validation method;
  • batch concurrency and timeouts;
  • DNS and SMTP behavior;
  • proxy-pool selection;
  • local data and export locations;
  • license and update state.

Change one performance setting at a time and validate it with a sample. Higher concurrency can increase remote throttling, proxy failures, and local resource use.

Updates

Use the in-app update check or an installer supplied by RocketsSend. Before updating:

  1. Pause or finish active tasks.
  2. Export critical results.
  3. Record the current version.
  4. Preserve local rule or task data according to the available backup workflow.

After updating, run single checks in each method you depend on before resuming a large batch.

Common issues

Many DNS results are unknown

  • Check general DNS resolution.
  • Disable a failing proxy or verify its protocol support.
  • Increase timeout only after confirming normal latency.
  • Compare a direct check on a small authorized sample.

SMTP PRO is unreachable

  • Confirm the domain has MX records.
  • Check outbound TCP port 25 from the actual device and network.
  • Review local firewall, ISP, cloud-provider, and proxy restrictions.
  • Reduce concurrency if destinations are throttling.

An unreachable SMTP stage is unknown; it should not be converted to invalid.

Catch-all results are frequent

Some providers accept arbitrary recipients or hide mailbox existence. Treat catch-all as risky and apply a policy appropriate to the source and consent context.

A batch appears slow

  • Check the mix of methods; SMTP PRO naturally waits on remote servers.
  • Review proxy latency and failure rate.
  • Look for one destination domain dominating the queue.
  • Reduce concurrency if retries or throttling increase.
  • Pause normally before changing network configuration.

Results differ between runs

Remote DNS, mailbox state, server responses, rule packages, proxy paths, and application versions can change. Compare timestamps, methods, versions, and reasons—not only the final status.

Safe support information

Provide:

  • application version and operating system;
  • license plan and method;
  • sanitized task size and status distribution;
  • exact error text and stage;
  • safe diagnostics with addresses, tokens, and proxy credentials redacted.

Email gordon.hu@rocketssend.com.

Reports and Export

Analyze list quality and export the right result subset for review or downstream use.

RSender Overview

Understand RSender's role in permission-based email operations and the path from setup to reporting.

Table of Contents

SettingsUpdatesCommon issuesMany DNS results are unknownSMTP PRO is unreachableCatch-all results are frequentA batch appears slowResults differ between runsSafe support information