Create Accountor Login
Docs

Email Delivery

Part of the MountDev Ops Workspace documentation. Updated November 18, 2026

MountDev Ops Workspace documentation | Updated November 18, 2026

Email Delivery decides how every email your workspace sends goes out: Helpdesk replies, receipts, and follow-ups, Forms auto-replies and notices, CRM emails and reminders, Chat transcripts, Proposals, Partners, Billing, and automation notices. You can use MountDev Ops' own sending, or connect your own SMTP server or email service, the same way you would in any email program. Owners and admins manage it on Settings, in the Email card (the Settings gear at the bottom of the menu, then Email). AI agents and API keys never see or change it. How your emails look, and each person's signature, is set in Brand, and the Email page has a link to it (Email Template and Signatures).

Choosing How Email Goes Out

The Email Delivery card (action core.email_delivery.get) shows the way chosen now, whether it is working, and when it was last tested, with Read the Docs at the top right of the card. Under Choose Your Email Service, each choice is a tile that says what you will need to enter. Save (action core.email_delivery.save) keeps a new choice. Sign In With Google is action core.email_delivery.google.start, and Google sends you back to a small page that finishes it (action core.email_delivery.google.finish):

  • MountDev Ops (Cloudflare Email Service): the start. Email goes out through MountDev Ops' own sending service. The From address (such as your Helpdesk address) must be on a domain set up for MountDev Ops sending; if it is not, sending fails with the reason, and you can connect your own delivery instead.
  • SMTP Server: any mail server or email service that offers SMTP, such as Google Workspace, Microsoft 365, Fastmail, or your web host. Enter the mail server's name (such as smtp.example.com), the port, the security, the user name, and the password.
    • STARTTLS (usually port 587): the connection starts plain and switches to encryption before anything is signed in or sent. If the server does not offer STARTTLS, nothing is sent, so your password never travels unencrypted.
    • TLS from the start (usually port 465).
    • Port 25 is not available for outgoing mail from the cloud.
    • The workspace signs in with AUTH PLAIN or AUTH LOGIN, whichever the server offers. Leave the user name empty only for a server that accepts mail without signing in.
    • Mail servers on private networks (such as 10.x, 192.168.x, or localhost) cannot be reached and are refused.
  • More email services with an API. Each is a tile under Choose Your Email Service, with its own fields, a one-line hint on where to find the key, and a Test It that sends one real email. The key is stored encrypted and never shown again. Where a service has regions, you choose yours from a short list.
    • Brevo: the API key (SMTP and API, API Keys). The sender must be validated in Brevo.
    • Mailjet: the API key and the secret key (Account Settings, API Key Management). Both are stored together, encrypted. The sender address or domain must be validated.
    • SparkPost: the API key with the Transmissions permission, and US or EU.
    • Mailchimp Transactional (Mandrill): the API key. It needs Mailchimp's paid Transactional add-on.
    • Elastic Email: the API key (Settings, Manage API Keys).
    • SMTP2GO: the API key, and US, EU, or Australia.
    • MailerSend: the API token with email access. A trial plan sends only to your own address.
    • Zoho ZeptoMail: the Send Mail Token (the words Zoho-enczapikey in front may be left on or off), and the data center your account is in.
    • Cloudflare Email Service: an API token that may send email and your Cloudflare account ID. The sending domain must be set up in that Cloudflare account.
    • Mailtrap: the API token for your verified sending domain. Its test sandbox is not offered, because a sandbox never delivers.
    • SocketLabs: your server ID and API key.
    • Netcore: the API key.
    • SendPulse: the API ID and API secret, stored together, encrypted. The SMTP service must be activated in SendPulse.
    • Mailpace: the server token for your domain.

Some services cannot keep the threading headers of a reply (the card says so under the fields). Replies still join their ticket by its number.

  • Microsoft 365: sends through Microsoft Graph as one mailbox you choose, with no pop up. In your own Microsoft Entra, make an app registration, give it the Microsoft Graph application permission Mail.Send, and have a Microsoft 365 admin approve it once. Here, enter the Directory (tenant) ID, the Application (client) ID, the client secret (stored encrypted, never shown again), and the mailbox to send as. Without more, that permission lets the app send as anyone in your company, so ask the admin to limit it to the one mailbox with an application access policy. A client secret expires (up to 24 months): make a new one and save it before then. If a test says the app may not send as that mailbox, the permission is not approved or the access policy does not include it.
  • Google Workspace: sends through the Gmail API as one Google account, using your own Google Cloud OAuth client. In Google Cloud, make an OAuth client of type Web application in a project whose user type is Internal, and give it the redirect address shown on the card as its authorized redirect address. Here, enter its OAuth client ID, the mailbox (the Google account you sign in with), and the client secret, then Save, then choose Sign In With Google and approve in Google's own window. You do this once. Only a lasting sign-in token comes back, and it is stored encrypted with the secret; it is never shown. The sign-in must be as the mailbox you entered, or it is refused. Choose Sign In With Google Again if Google stops letting this workspace send. Changing the client ID or secret needs a new sign-in. Gmail allows about 2,000 emails a day for each Workspace mailbox (500 for a free Gmail account).
  • Postmark, SendGrid, Mailgun, or Amazon SES: email services with an API. Enter the API key (for Postmark, the server API token). For Postmark you can name the message stream (outbound at first). For Mailgun, enter your sending domain and choose US or EU. For Amazon SES, enter the region (such as us-east-1), the access key ID, and the secret access key of an IAM user allowed to send email.

A workspace that already sends through Resend keeps doing so, and its tile stays until it chooses another service. Resend is not offered to anyone else.

For any choice but the first:

  • Company Sender (Sender name and Sender address): one name and address for your whole company. Every app uses them whenever it sends an email with no sender of its own; an app with its own sender, such as a Helpdesk address, keeps that. The test email comes from them too. With your own email service, use an address your account there may send from.
  • Send everything from this address: turn it on when your service only lets you send from one address. Each email then goes out from this address, keeping the sender's name, and the address it would have come from (such as your Helpdesk address) becomes the Reply-To, so answers still reach the right place.

The password or key is stored encrypted with a key only your company's workspace can use. It is never shown again, to anyone, and never written in any log. Leave it empty when you save to keep the saved one. A password or key saved for one service is kept if you switch away, so switching back does not need it typed again. Changing the choice, the server, the key, or the From address marks the delivery Not tested yet.

A company that chose its own delivery never falls back to MountDev Ops' sending: if your service refuses an email, the email is marked as not sent, with your service's answer, so nothing goes out from an address you did not choose.

Email Before You Choose Your Own Service

Until you choose your own service, everything your apps send except marketing (sign-in codes, receipts, confirmations, invoices, and notices) goes out through the shared sending, from the same sender as your notices: your provider's verified support address if you have one, otherwise the platform's support address. Replies go to the address the email would otherwise have come from. Each one counts in your email usage and is listed in Recent Emails. Marketing email from Campaigns is never sent this way. Connect your own sending service first (Operations, then Integrations, then My Connections, then Add, and choose Connect a Service).

When No Email Service Is Set Up

Your workspace may be set to send email only through your own email service. Then the card shows Not Set Up until you choose one, and Send email through starts at No email service yet. Nothing is sent through anyone else's sending, and nothing is lost:

  • Every email your apps send while no service is chosen waits, kept safe in your own workspace. Recent Emails lists each one as Waiting, and the card says how many are waiting.
  • Every owner and admin is told once, in Needs You Today, what to set up, with a link to Settings, Email.
  • Once you save your own service, the waiting emails go out through it, a few at a time, in your business hours (Email and Business Hours). The ones that always go at once, such as a receipt, go at once. Each line in Recent Emails then says Sent, with your service's answer. An email your service refuses keeps waiting and is tried again later, with the reason on its line.
  • An email that cannot wait, such as Send Test Email or a code a client is waiting for on screen, is not sent, and you see why: choose your email service first.
  • Very large emails (over about 1.5 MB with their attachments) cannot be kept while waiting. The app that sends them sees the reason and tries again later, the way it does when an email service is busy.
  • Sign-in codes are the one exception: they always go out, so nobody is locked out.

Send Test Email

Under Test It, type the address to send the test to (your own address is filled in) and press Send Test Email (action core.email_delivery.test). It sends one email to that address, the way you saved, and shows your service's exact answer: for example "250 2.0.0 OK queued as 4XyZ" from an SMTP server, "Accepted, id re_123" from an email API, or the refusal word for word, such as "Signing in (AUTH PLAIN) was refused: 535 5.7.8 Username and Password not accepted". The card then shows Working or Failing with the reason. When a test fails, a plain sentence says what went wrong and what to do, with your service's exact answer under it. For example: "Cannot reach smtp.example.com on port 587. Check the server name and port, and that the server allows connections from the internet.", "The server said no to the user name or password. Check them in your email account and try again.", "The server refused the sender address. Use an address your account may send from.", or "The service did not accept the key." Save your changes before testing; the test uses what is saved. The test email says it was sent from Settings, Email, and nothing else about your account.

Recent Emails

Recent Emails (action core.email_delivery.log) lists every email the workspace sent or tried to send, newest first, and updates on its own as emails go out: when, which app sent it (such as Helpdesk), to whom, the subject, Sent or Not Sent, the service it went through, and the service's answer or the reason it failed. Only Not Sent shows just the failures. It never holds the email itself.

It shows 10 emails at a time. Below them, a line such as 11 to 20 of 134 says which ones you are looking at, and Previous and Next move a page back or forward. All, Only Not Sent, and Automated Emails each keep their own page, so moving between them brings you back to where you were.

This is where to look when a client says they did not get a reply or a receipt: if the email is listed as Sent, your service accepted it, and the client's own mail system decides where it lands; if it is Not Sent, the reason is beside it.

Automated Emails

Automated Emails, beside Only Not Sent (action core.email_delivery.automated), lists every email your apps sent to clients on their own: Helpdesk's automatic follow-ups, closing notices, and daily follow-ups, and proposal reminders. Each shows what it was (such as Follow-up 2 of 3 or Proposal reminder 1), the ticket or proposal it was about, with a link to open it, who it went to, when, and Sent or Not Sent. Show Email shows the email exactly as it went out (action core.email_delivery.automated.get). The same email is also on its ticket's conversation or its proposal's Links and Activity. It shows 10 at a time, newest first, with Previous and Next, like the rest of Recent Emails. Owners and admins see this list; nothing in it can be changed.

Headers a Service Does Not Take

Some services refuse an email that carries a header they do not know. Cloudflare Email Service, for example, says "custom header is not allowed" for anything outside its list and the headers that start with X-. So no app can stop its own email from sending this way, every email is checked just before it goes to your service, and a header that service does not take is left off (the email goes out without it). Only the header's name is written in the workspace's logs, never its value or any part of the email. An SMTP server, Amazon SES, Mailgun, Microsoft 365, and Google Workspace are given the whole message and take every header. The other services get the headers that mail apps use to keep a conversation and a mailing together (In-Reply-To, References, Auto-Submitted, Precedence, Importance, Priority, and the List- headers) and every X- header. The invitation in a meeting email is the calendar part of the message, which mail apps read, so it needs no header of its own.

A meeting email that was not sent can be sent again from Meetings (When an Email Is Not Sent).

Threading

Helpdesk replies carry the In-Reply-To and References headers of the conversation, so they stay in the same thread in your client's email program. With an SMTP server, Resend, Postmark, SendGrid, and Mailgun, each email goes out with a Message-ID the workspace keeps, so the client's answer joins the right ticket. Amazon SES and MountDev Ops' own sending give each email their own Message-ID, which the workspace keeps from their answer. Either way, an answer also joins its ticket by the ticket number in its subject or text.

Ask Us Anything

We’d love to hear from you!