Why a send is refused | AgentsMail.io Documentation

Nothing left, and you want to know why. Every refusal is named — the product never fails silently on a send — and each name maps to exactly one thing to fix.

The reasons

Reason	What it means	What clears it
Sending is switched off	Marketing sending is paused across AgentsMail.	Nothing on your side. It is lifted by AgentsMail.
Organization not allowed	Your organization has not been cleared to send.	Contact support — this is a manual authorization.
Sending paused	The provider suspended sending for your organization, usually after a reputation incident.	Fix what caused it; the pause is lifted by the provider.
Domain not verified	Your sending domain has no valid DKIM yet.	Publish the DKIM records at your DNS provider, then verify.
Domain ownership unproven	DKIM passed, but this organization never proved it owns the domain.	Publish the TXT challenge shown in the domain settings.
No sender address	A domain is verified, and the address book is empty.	Add an address on one of your verified domains.
Sender not on a verified domain	The chosen sender address belongs to no verified domain of yours.	Pick another address, or verify that domain.
Not enough sending units	Your balance is short for this audience. The message says by how much.	Top up, or reduce the audience.
Daily quota exceeded	Sending now would go past the provider's 24-hour ceiling.	Wait for the window to roll, then send again.

Two of these are worth telling apart: domain not verified and ownership unproven look alike and are fixed differently — one is about DKIM records, the other about a TXT challenge. That is why they are two separate messages.

Immediate sends versus scheduled ones

A send you trigger yourself is refused on the screen, with the reason, and the draft is left exactly as it was. No email left, nothing to undo. A scheduled campaign is checked at its departure time, when nobody is watching. If it is refused, it is put back to draft, its schedule is cleared, and the owners and admins of the organization get a notification naming the reason — including how many units were missing.

A refusal never sends half a campaign. Every check happens before the first email leaves. A campaign is either fully underway or fully untouched.

Not a refusal, but often mistaken for one

Zero recipients. A valid campaign to nobody: the audience resolved empty. Check the tag or segment you targeted.
Fewer emails than the audience shown. The audience is an estimate; unsubscribes, suppressed addresses and topic refusals are applied at departure.
A contact ceiling hit. That refuses adding contacts, not sending. Existing contacts keep receiving.

Where to look

The sending settings screen shows the current state as a checklist, in plain words rather than codes — it is the fastest way to see what is missing before you write anything. Over HTTP, one call answers the same question, so an agent can set an account up from nothing and find out exactly what stands in its way: see Settings & domains.