Appearance
Set up your own mail service
Every community must provide its own sender domain and SMTP credentials. No OpenRP-hosted mail service, mailbox or relay is bundled. The application needs outbound transactional messages; hosting players’ personal mailboxes is not a requirement.
Option A: use your own SMTP provider
Use an account you control with an email/transactional delivery service. Add your domain, prove ownership using the requested DNS records, create a dedicated sender/SMTP credential and enter it in the web environment. Keep provider sandbox restrictions in mind when testing recipients.
Configure sender authentication using your provider’s exact records, then follow the application SMTP guide. This route works whether your game runs on Windows, Linux, EasyPanel or another panel. The provider handles mail delivery; you still own the credentials, DNS and sender policy.
Option B: self-host a Linux mail server
This is a separate service to administer. Before choosing it, confirm your host allows mail traffic and gives you a usable static public IP with reverse-DNS control. A server that can accept SMTP connections is not automatically a server that remote inboxes will trust.
The example route here uses Docker Mailserver. Use its basic installation guide for the matching release’s Compose template. Pin a release, keep its configuration persistent and run it separately from your game service.
1. Choose the mail identity
Use your own domain, for example example.com, and a mail hostname such as mail.example.com. Replace every example below with your values. Arrange a mailbox or forwarding destination for administrative/bounce messages.
Create the mail A record pointing to the mail host. Configure reverse DNS at the IP provider so the IP resolves back to the intended mail hostname. Publish AAAA only if IPv6 mail routing and reverse DNS work correctly too. Do not point mail traffic through an HTTP-only CDN proxy.
2. Prepare DNS authentication
| Record | Purpose | Example shape |
|---|---|---|
| A / optional AAAA | Resolve your mail hostname | mail.example.com → your mail host |
| MX | Route inbound domain mail | example.com → priority 10, mail.example.com |
| PTR | Give the sending IP a reverse hostname | Set through the IP provider |
| SPF TXT | Authorise senders for the envelope domain | Use your actual sending hosts/services |
| DKIM TXT | Publish the mail service’s signing public key | Generated selector under _domainkey |
| DMARC TXT | Define alignment/reporting policy | _dmarc.example.com |
Generate DKIM with the mail stack you chose. Publish only its public DNS record, never the private key. Keep one SPF record per domain and combine legitimate senders into it. Begin a new DMARC rollout with monitoring, inspect alignment results and move to an enforcement policy deliberately. The Docker Mailserver DNS guide explains its key generation and record formats.
3. Install the mail stack
On the Linux mail host, install Docker/Compose using their supported host instructions. In a dedicated mail-service directory, obtain the release-matched Compose and environment examples from Docker Mailserver. Configure the hostname, persistent mail/config/log storage and the ports needed by that release.
Set up a valid certificate for mail.example.com. For its Let's Encrypt integration, Docker Mailserver supports SSL_TYPE=letsencrypt with the certificate storage mounted as documented; the certificate must already be provisioned and renewal must remain operational. See its TLS configuration guide. An EasyPanel HTTPS domain on the web app does not automatically configure SMTP TLS.
4. Create the application sender
With a Compose service named mailserver, the administration command follows this form:
sh
docker compose up -d
docker compose exec mailserver setup email add noreply@example.com
docker compose exec mailserver setup config dkim
docker compose logs --tail=100 mailserverUse an interactive password prompt so the credential is not stored in shell history. Copy the generated public DKIM record to DNS. Service names and configuration details depend on the template version; consult the matching Docker Mailserver usage guide.
5. Configure application submission
Use authenticated submission, normally port 587 with STARTTLS or 465 with implicit TLS. The framework web service connects to this endpoint; the game and agent do not need the SMTP password.
dotenv
SMTP_HOST=mail.example.com
SMTP_PORT=587
SMTP_SECURE=false
SMTP_USER=noreply@example.com
SMTP_PASS=YOUR_NEW_MAILBOX_OR_SMTP_PASSWORD
SMTP_FROM="Your Community <noreply@example.com>"Mail transfer between servers normally needs TCP 25. Submission and optional inbox access have separate ports; open only the services you operate. Do not configure anonymous relay for public clients. If outbound port 25 is blocked, use an authenticated relay you control rather than trying to send directly.
6. Prove delivery
Run the SMTP verification command, then send real verification/reset emails to accounts you control on external domains. Inspect received message headers for SPF, DKIM and DMARC results. Check queues, bounce messages, reverse DNS, certificate expiry and spam placement.
Back up mail configuration, account credentials, DKIM private keys and any mail data you retain. Monitor failures and certificate renewal. Self-hosting instructions are a deployment guide, not a claim that your host/IP has been delivery-tested.
Standalone and panel-hosted mail
You may use an existing correctly administered Postfix/Exim service, a mail panel or another SMTP server instead. Give the web application a dedicated authenticated sender endpoint with the same SMTP environment settings. The framework does not depend on Docker Mailserver, EasyPanel or a particular provider.
Keep mail separate from game lifecycle operations: stopping or updating the game must not remove your account-recovery service.