How sending becomes available
Domain checks confirm that you control the domain and have published the required DNS records. For eligible invited accounts, weneed then creates and renews sending permission automatically. Normal alpha setup does not require a separate manual test approval.
Create an API key or SMTP login for the exact address your application will send from. Each credential is bound to that one address. Your allowance, DNS checks and recipient suppression also apply to test emails.
If Control shows customer_grant_required, check the domain guidance and refresh the status. If it persists, contact support with your project ID. This is an exception to investigate, not a routine request for approval.
If sending is paused
Section titled “If sending is paused”weneed.email holds messages instead of sending them when, for example:
- a required DNS record disappears or its check goes stale,
- a credential is revoked (messages it submitted wait for review),
- a message’s
expires_athas passed, - too many messages bounce or a recipient complains.
Bounce and complaint limits
Section titled “Bounce and complaint limits”For each stream, weneed.email counts permanent bounces over the last 24 hours and the last 7 days:
| Permanent bounces in the period | Result |
|---|---|
| At least 5, and at least 2% of accepted messages | Sending is flagged for review. It continues. |
| At least 10, and at least 5% of accepted messages | Sending is paused. |
A complaint (a recipient marking your mail as spam) pauses sending as well.
A pause doesn’t lift itself, not even when a new day or month starts. A weneed person reviews it and resumes sending. Your project home shows the pause, and the message timeline shows held messages. Contact support with your project ID.