In short
- Quotes, invoices, emails and campaigns go through your own email service account.
- Your sending reputation is yours alone - nobody else's campaign can hurt it.
- You choose the service: Resend, Brevo, Postmark, SendGrid, Mailgun, Amazon SES, Zoho, Google Workspace or any email server.
- Every connection is checked with a real test email before it is saved.
The problem with a shared account
When a software company sends every customer's email through one account, mailbox providers see one sender. If one customer sends a careless campaign, the whole account's reputation suffers, and your invoices may start landing in spam for reasons you never see and cannot fix.
A shared account also decides things for you: which domain your email appears to come from, how many emails you may send, and what happens to the records of every message.
How Moirova sends instead
- An admin connects the workspace's own email service in Email settings, with a key made for Moirova.
- Moirova checks the key, then sends a real test email to the admin. Nothing is saved until that works.
- The key or password is kept in Google Secret Manager, never in the database.
- Campaigns go through your own sending service too. A mailbox service such as Zoho or Google Workspace is not used for bulk email, because those services do not allow it.
- Moirova's own email account sends only Moirova's own messages, such as password resets.
Why it is worth the few minutes
- Your reputation is built only by your own email.
- You can see every message in your own service's logs, and its limits and prices are the ones you chose.
- If you ever leave, your email account and its history stay with you.
The step-by-step guide is Connect your workspace's email service, and what to prepare at each service is in Set up your account at your email service.
Mailbox or sending service: which one you need
Two kinds of email service do two different jobs, and most businesses need one of each.
- A mailbox - Zoho Mail, Google Workspace, Microsoft 365 or the email that comes with your hosting - is where your team writes and receives everyday email. It is the right place for one-to-one email: a quote to one client, a reply to a question. Mailboxes limit how much you can send in a day and are not allowed to send bulk email.
- A sending service - Resend, Brevo, Postmark, SendGrid, Mailgun or Amazon SES - is built to send large numbers of emails reliably and to report on each one: delivered, bounced, opened, marked as spam. It is the right place for campaigns, and many businesses also use it for invoices and quotes.
Moirova works with both. Quotes, invoices and client emails can go from your mailbox or your sending service; campaigns and journeys go only through a sending service, because mailbox providers do not allow bulk email.
What a key made for Moirova means
A sending service gives you API keys: long secret codes that let a program send on your account. Make one key just for Moirova, with the permissions the setup step asks for, rather than reusing a key you already have elsewhere.
A key of its own means you can see in your service's logs exactly what Moirova sent, you can replace it whenever you like, and if you ever stop using Moirova you delete that one key and nothing else breaks. The key is kept in Google Secret Manager, not in the database, and is not shown again after you save it.
Your domain, checked step by step
Sending is only half the job; arriving is the other half. After the service is connected, step 2 of Email settings checks your domain's DNS records: SPF, the DKIM signature key and DMARC. Each one is shown as found or missing, with the exact record to add at your domain host and a Copy button.
The step works with any email server, not only the services it knows. When it cannot tell which signature key your server uses - common with your own email server or cPanel hosting - it looks for the keys in your DNS and offers the ones it finds, so you can pick yours with one click. The guide Set up your email domain covers every record.
Replies come back into the CRM
Email is a conversation. Step 4 of Email settings brings your clients' replies onto their page for the whole team: through your domain's receiving record and a webhook with Resend, or by reading the mailbox replies arrive in with any other service. Only emails from your contacts, and answers to emails the CRM sent, are brought in. Files your clients attach are kept with the reply when they are a safe kind. The guide Bring replies into the CRM shows both ways.
When a key or password stops working
Keys get rotated, passwords change, accounts are closed. When that happens, Moirova does not quietly switch to someone else's account to get the email out - that would hide the problem and put your email back on a shared reputation. The email is marked Not sent with the reason in plain words, and an admin sees what needs fixing in Email settings. Nothing is sent on your behalf through an account you did not choose.
What it costs you, and what it saves
Connecting your own account takes a little setup: an account at the service, a key, a few DNS records for your domain. Most of that is a one-time job of under an hour, and Moirova checks each step as you go, so you know it works before your first real email.
In return you get things a shared account cannot give you. Your deliverability is built by your own sending and nobody else's. When a client says an invoice never arrived, your service's logs show exactly what happened to it. Your limits are the ones on your plan with that service, and if you outgrow them you change plan there, without waiting for anyone. And if you ever move to other software, your account, your domain's reputation and your sending history move with you, because they were always yours.
Moving from a shared account to your own
- Create the account. Open an account at the sending service you chose and make one key for Moirova.
- Connect it. In Email settings, step 1, choose the service and paste the key. Moirova sends you a real test email before saving it.
- Prove your domain. Step 2 lists the DNS records to add. Add them at your domain host and let the step confirm each one.
- Bring replies in. Step 4 sets up how clients' replies reach their pages.
Emails you sent before the switch stay in each client's conversation, so the history does not start again. Campaign and journey settings, your contacts and your suppression list stay as they were; only the account the emails leave through changes, and from then on it is yours.

