Read evidence by source
Diagnostics reports Healthy, Needs attention, Unavailable, Not configured, or Unknown rather than collapsing unrelated state into one boolean.
- service version, build, uptime, operating system, runtime, and hosting mode;
- SMTP listener state, actual binding, mode, enabled devices, and last local acceptance;
- queue counts, oldest message, next retry, and worker state;
- persisted and current-process Microsoft readiness;
- certificate presence, private-key accessibility, validity, and expiry;
- the last sanitized Microsoft setup stage, substage, category, and code;
- storage availability, schema, free space, and SQLite quick-check evidence; and
- management, LAN SMTP, tooling, certificate, and setup-scratch boundaries.
Choose the correct check
| Action | What it checks | What it does not do |
|---|---|---|
| Run connectivity checks | DNS, TCP 587, SMTP greeting, EHLO, STARTTLS, and certificate-validated TLS | Acquire a token, authenticate, mutate the tenant, or submit mail |
| Database quick check | SQLite PRAGMA quick_check | Edit, vacuum, or recreate the live database |
| Microsoft Verify connection | Active certificate, token acquisition, TLS, XOAUTH2, and QUIT | Provision the tenant, activate a candidate, or send a mail transaction |
| Repair connection | The controlled Microsoft identity and RBAC repair flow | Replace Windows Installer repair or justify broad permissions |
Generate and review a support bundle
RelayBridge creates the ZIP locally and does not upload it. Bundle schema v1 uses a fixed allowlist and a 1 MiB compressed-size cap.
The implemented exclusions cover raw configuration, database files, logs, spool files, message content, mailbox addresses, device credentials and verifiers, OAuth tokens, private keys, certificate references, and detailed raw setup output.
The bundle still includes operational metadata such as versions, timestamps, counts, listener and network information, storage capacity, and sanitized status summaries. Review it for your environment before attaching it to any report. Sanitization reduces risk; it is not a guarantee that sensitive information can never appear under every defect or environmental condition.
Report the problem safely
Use GitHub Issues for reproducible non-security defects. Do not publish tenant identifiers, mailbox or message data, credentials, tokens, certificates, private keys, raw configuration, databases, spool files, or an unreviewed support bundle.
Report suspected vulnerabilities through the repository's private security-reporting process described in SECURITY.md.