#Support

cmail is a community-maintained, self-hosted project. The MIT license includes no hosted-service or guaranteed-response support.

For an organisation's operational support model — internal first-line triage plus an optional RME Solutions Technology escalation path — see the support process. That process does not change the community-maintainer scope described above.

#Before asking for help

1. Check the documentation, especially configuration and deployment verification.
2. Search existing issues for the same symptom.
3. Run pnpm validate and note the first failing command.
4. Reduce the problem to a staging or local environment with non-sensitive test data.

Use a bug report for a reproducible cmail defect and a feature request for a broadly useful product change. Include the affected commit, component, deployment shape, safe reproduction steps, expected result, and actual result.

Deployment-specific design, configuration, troubleshooting, and other work outside a reproducible product defect are not included with the project and may require separately scoped assistance.

#Keep reports safe

Never post OAuth credentials, session values, API keys, Cloudflare account or resource IDs, private message content, personal data, production URLs, raw database exports, or unredacted logs. Replace deployment-specific values with obvious examples such as example.com.

Report suspected vulnerabilities through the private process in SECURITY.md, not through a public support issue.

#Deployment-specific assistance

Cloudflare, Google, Microsoft, Postmark, DNS, privacy, and regulatory questions may require the relevant provider or a qualified local professional. Project maintainers cannot inspect or administer an operator's accounts and cannot certify a deployment for a particular legal or assurance framework.