Sending email from your own domain
Send OpsDash's emails from your own address and domain, through your own mail server or a verified domain, and check SPF, DKIM and DMARC.
OpsDash sends emails for you: invoices, quotes, reminders, ticket replies, portal invites, campaigns and more. Out of the box they go through OpsDash's own email service with your from name and reply-to address. For the best deliverability and a professional look, send from your own domain.
There are two ways, both in Settings › Email sending:
- Your own mail server (SMTP): emails go out through your email provider (Google Workspace, Microsoft 365, your host).
- A verified sending domain: emails go through OpsDash's email service but come from
@yourdomain.co.uk, once you've added DNS records.
Use your own mail server (SMTP)
What you need: your provider's SMTP host, port, username and password (often an app password). Owners and admins only.
- In Settings › Email sending, under Mail server (SMTP), enter the SMTP host, port, user and password.
- Save. They're stored encrypted.
- Under Send a test email, send yourself one to confirm it works.
Verify a sending domain
- Under Domain verification, enter your domain (for example
youragency.co.uk). - OpsDash shows the DNS records to add (type, name and value). Copy each into your domain's DNS (at your registrar or host).
- Come back and check verification. Each record shows its status until it's verified.
Custom sending domains need the right plan on OpsDash's email service; the card says if it isn't available. Remove domain clears it.
Check SPF, DKIM and DMARC
Settings › Sending setup checks the domain your emails come from:
- SPF: which servers may send as your domain.
- DKIM: a signature proving the email wasn't changed. Enter your provider's DKIM selector (for example
googleorselector1) if it isn't found at the usual ones. - DMARC: what receivers do with mail that fails.
Each shows Passes, Could be better, Missing or Problem, with what to fix. Send me a test email sends a branded email to your own address exactly the way campaigns and sequences are sent.
How emails look
Your logo, colours, email header and footer come from Settings › Branding › Email branding.
Troubleshooting
- The test email doesn't arrive: check spam, then the SMTP details. Port 587 usually uses STARTTLS; 465 uses SSL.
- Google or Microsoft refuse the password: use an app password, and make sure SMTP sending is allowed for the mailbox.
- Emails go to spam: fix anything Sending setup marks as Missing or Problem, especially SPF and DKIM for whichever service sends your email.
- Replies go to the wrong place: ticket replies use your support mailbox as the reply-to.
Settings in OpsDash
These open in OpsDash. You’ll be asked to sign in first if you aren’t already.
Related articles
- Campaigns, sequences and templatesSend email campaigns to groups, run automatic sequences such as client onboarding, use branded templates, and respect consent and unsubscribes.
- The support mailboxConnect your support email inbox so new mail becomes tickets, matched to the client who sent it, with replies threaded back on.
- Email settingsEmail sending (your own SMTP server, domain verification, test email) and sending setup (SPF, DKIM and DMARC checks).