Sender Health
How Lumail measures sending health, receiving-server delivery, and domain authentication
Sender health is the organization trust score already used to keep sending unlocked. It lives on Settings → Deliverability and Settings → Verification. Lumail does not introduce a fourth score formula here.
This page is not inbox placement. A delivered event means Amazon SES accepted the message at the receiving server.
Where to look
- Settings → Deliverability — sender health, 24h/7d/30d outcome metrics, recommendations, authentication, SES infrastructure
- Settings → Verification — the same sender score plus domain unlock checklist
- Dashboard campaign delivery score — a separate campaign-window formula, documented in Campaign Delivery Score
- Editor content checks — pre-send content hygiene, documented in Content Deliverability Checker
Metric definitions
Every metric shows its count, denominator, date window, and sample confidence. Below 50 events the sample is insufficient; below 200 it is limited. Low-volume segments stay neutral, not high-risk.
| Label | Definition | Denominator |
|---|---|---|
| Sent | SES-accepted send attempts stored as Lumail emails | sent |
| Delivered to receiving server | SES delivery event received | sent |
| Delayed | SES delivery-delay events | sent |
| Permanent bounce | Normalized permanent bounces | sent |
| Transient bounce | Normalized transient bounces | sent |
| Reported complaint rate | Feedback-loop complaints received | delivered |
| Unique open | Unique non-bot opens | delivered |
| Unique click | Unique clicks | delivered |
| Sender health | Existing getOrganizationTrustScore() 30-day result | last 30 days of sending |
Tests and Amazon SES mailbox-simulator traffic are excluded from customer health.
What “delivered” does not mean
Delivered is not inbox placement. The message can still land in spam. Lumail cannot reproduce Amazon SES Virtual Deliverability Manager’s optimized shared delivery, private ISP insights, or seed-panel evidence.
Recipient-provider breakdowns (Gmail, Yahoo, Microsoft, Apple, Proton, Other) are a recipient-domain mapping. They are not AWS VDM ISP intelligence.
Reported complaints and opens
Reported complaint rate only includes ISPs that send feedback-loop complaints. Missing ISP coverage is not treated as a clean list.
Open rate is directional. Apple Mail Privacy Protection and image proxies inflate or hide opens. Known bots are excluded where Lumail can detect them.
Authentication and recommendations
Each custom sending domain gets a last-checked posture for SES identity, DKIM, custom MAIL FROM MX/SPF, DMARC, and optional BIMI. BIMI is informational and never required for a healthy sender.
Recommendations are persistent OPEN/RESOLVED rows with a stable rule key, evidence, and a remediation link. WARNING/ERROR openings notify the organization once (deduped, with the existing email cooldown). A finding does not resolve just because a DNS lookup failed; resolution needs a confirming healthy scan.
Members can view Deliverability. Owners and admins can refresh infrastructure snapshots.
Related
- Deliverability alerts — how-to for every warning and error
- Campaign Delivery Score
- Content Deliverability Checker
- Account Verification
- Email Domains