Deliverability alerts
How-to guides for every Lumail deliverability alert — what it means and what to change.
Every deliverability warning and error in Lumail links here. Open the matching guide, make the change, then recheck Domains or Settings → Deliverability.
This is not inbox placement. A delivered event means the receiving server accepted the message.
Domain authentication
| Alert | What to change | Guide |
|---|---|---|
example.com DMARC policy is monitoring only | _dmarc TXT: p=none → p=quarantine or p=reject (on the root domain if inherited) | How to strengthen DMARC |
example.com is missing DMARC / DMARC record is malformed | Publish a valid _dmarc TXT | How to add DMARC |
example.com DKIM is missing, failed, or weak | Add the DKIM CNAMEs from the domain page | How to fix DKIM |
example.com is not verified for sending | Add the verification + SPF records | How to verify a sending domain |
example.com custom MAIL FROM MX/SPF is incomplete | Add MX + SPF on ses.example.com | How to fix MAIL FROM |
example.com BIMI record is malformed | Fix or remove the default BIMI TXT | How to fix BIMI |
Sending health
| Alert | What to change | Guide |
|---|---|---|
| Sustained permanent bounce rate is above 2% / 5% | Remove invalid addresses before the next send | How to lower bounce rate |
| Sustained reported complaint rate is elevated / above 0.1% | Stop mailing people who mark you as spam | How to lower complaint rate |
| Sustained delivery delays are above 10% of sent mail | Check volume, reputation, and content | How to fix delivery delays |
| Bounce diagnostics mention blocked-list or spam concentration | Treat it as a reputation / list problem | How to fix blocklist bounces |
Infrastructure
These are Lumail sending-platform checks, not DNS you edit at your registrar.
| Alert | Guide |
|---|---|
| Bounce and complaint feedback is not connected | How to fix sending infrastructure |
| Email event tracking is disabled | How to fix sending infrastructure |
| Configuration set event destination is unhealthy | How to fix sending infrastructure |
| Email sending is paused | How to fix sending infrastructure |
| Dedicated IP pool is missing / not ready / warmup stalled | How to fix a dedicated IP |
Sends, billing, and verification
| Alert | What to change | Guide |
|---|---|---|
| Domain verification failed | Add the DNS rows on the domain page | How to verify a sending domain |
| Sender domain DNS is incomplete / MAIL FROM | MX + SPF on ses.example.com | How to fix MAIL FROM |
| Message rejected / send failed | Fix From, domain, or the named SES code | How to fix a failed send |
| Invalid email parameter | Fix from / to / subject / headers | How to fix an invalid email parameter |
| Sending rate exceeded / daily quota | Slow down or ask for a higher cap | How to fix sending rate or daily quota |
| Email used fallback domain | Fix the primary domain | How to fix a fallback-domain send |
| Approaching / hit monthly email limit | Upgrade or wait for reset | How to fix a monthly email limit |
| Sending blocked — payment past due | Pay the invoice | How to fix a past-due payment pause |
| Sending blocked — unverified org | Verify the domain / complete the form | How to unlock sending |
| Sending blocked — admin pause | Contact support | How to fix an admin sending pause |
| Additional verification / declined / more info | Complete Settings → Verification | How to complete additional verification |
| Campaign failed | Fix the underlying send/quota error, then retry remaining | How to fix a failed campaign |
| Campaign email failed to render / invalid HTML | Fix the template, then test | How to fix a campaign render error |