Mailfully logo

Troubleshooting

Find the right page from the symptom you can see or the error type you received, across domains, delivery, sending, and API keys.

This section routes a specific failure to the page that fixes it, covering domain verification, DNS records, refused sends, and delivery problems. If you have an error type in hand, match it in the table below; that is the fastest route to the right page.

By error type

StatustypePage
403unverified_domain_requiredLive sending is refused
401missing_api_key, invalid_api_key, invalid_session_tokenAuthentication
403insufficient_scopeScopes
403invalid_api_key on a revoked keyRotation
422validation_error, param: "from"Live sending is refused
403account_suspended, account_rejected, forbiddenLive sending is refused
409domain_parent_taken, conflictAdding a domain was refused
403domain_limit_reachedAdding a domain was refused
422marketing_single_recipient, marketing_missing_postal_address, recipient_unsubscribedUnsubscribe links
429account_under_reviewLive sending is refused
429rate_limit_exceeded, daily_quota_exceededRate limits and quotas
429monthly_quota_exceeded, marketing_quota_exceeded, spend_cap_exceededQuotas and plan limits

By symptom

Without an error string, match the symptom instead.

SymptomPage
A domain's status stays pending past its verification windowDomain will not verify
A required MX record looks like it would clash with corporate mailMX record conflicts
A live send was refused with a 403 or 422Live sending is refused
Mail is delivered but lands in spamWhy emails go to spam
A message shows as delivered and never arrivedDelivered but not received
A 202 came back and nothing sentDelivered but not received
A browser fetch failsCalling the API from a browser
A key was committed to a repositoryA leaked API key
Adding a domain was refusedAdding a domain was refused
A marketing send was refused over recipients, a postal address, or an opt-outUnsubscribe links
Sending stopped after hitting a monthly or daily allowanceQuotas and plan limits

Still stuck

Before contacting support, collect: the message id, the timestamp, the recipient domain, the error type if you have one, and the event timeline from GET /v1/emails/:id/events.