Email setup
Forwarding (recommended)
Most teams already have a workspace inbox, another mail provider, or a sending service on their domain. Pointing that domain's MX at Troppus can conflict with those setups. Forwarding into a Troppus platform receive address keeps your existing mail where it is and still opens tickets in Troppus. A shorter walkthrough lives on the connect email page.
- Open Admin → Domains and copy your platform receive address (unique host).
- In your mail or DNS provider, forward support@yourdomain.com (or whichever alias you use for support) to that address.
- Leave your existing MX records as they are. Send a test message. It should open as a ticket in Troppus.
Any local-part on that receive host also routes (for example help@… on the same unique host).
Troppus always accepts mail on the platform receive address. You can optionally enable Receive on a custom domain for Direct MX. Forwarding is the recommended path when you already have mail elsewhere.
Custom domain for branded replies (Send)
Branded replies require a verified custom domain. To send as support@yourdomain.com, add that domain under Admin → Domains and publish the records shown on the domain page. Verification proves you own the domain and authorizes Troppus to send on your behalf.
Receive stays off by default. MX is not required when you use forwarding. Send turns on once the domain verifies.
Optional: Direct MX (Receive)
If you want Troppus to receive mail directly for a host (for example a dedicated subdomain like support.yourcompany.com), point that host's MX at inbound SES and turn Receive on. That is an advanced alternative to forwarding, not required when you already receive mail through another provider.
If you add a subdomain but manage DNS in the parent zone, enter the subdomain label as the record name, not @. The domain page shows both the provider name and the full hostname each record must resolve to.
DNS can take a few minutes to propagate. Use Verify on the domain page to re-check.