Your outbound queue can shrink because a cleanup job mistakes uncertainty for rejection. You get fewer prospects and a reassuring green checkmark. Lovely.

In deep verification, the Actor probes a made-up address alongside the prospect's mailbox. If the server accepts that address too, the domain is catch-all: the verdict becomes risky , and confidence drops.

A catch-all verdict means mailbox acceptance is inconclusive, not that the prospect's address is invalid. Your ingestion job should preserve that distinction before a campaign rule turns it into deletion.

Ask the mailbox question explicitly

Use deep verification for this workflow. The default standard setting doesn't perform mailbox-level SMTP verification or catch-all detection.

Example input and setup for the module:

import { randomUUID } from ' node:crypto ' ; import { ApifyClient } from ' apify-client ' ; import { z } from ' zod ' ; import pg from ' pg ' ;

const Input = z . object ({ emails : z . array ( z . string ()), verificationDepth : z .…