> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moshi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Send shopper emails from your own domain

> Send Moshi's shopper emails from your own address. Verify your domain or connect your own SMTP server, then check that it works.

Moshi sends emails to your shoppers, such as discount codes, follow-ups, and broadcasts.
By default, these emails come from Moshi's address.
You can send them from your own address instead, like `deals@yourstore.com`.

Shoppers recognize your brand in their inbox.
Mail that is authenticated for your own domain also builds trust with inbox providers over time.

## Before you start

* **Access**: You must be an org admin in Moshi. Other members see "Only org admins can manage email sending."
* **Domain**: For the recommended option, you need access to your domain's DNS settings, or to the person who manages them.
* **SMTP account**: For the SMTP option, you need the server details and a password or API key from your email provider.

To open the settings, open Settings in Moshi, select Integrations, then select Email.

## Which emails change

The setting applies to these shopper emails:

* Discount code emails
* Email follow-ups
* Broadcasts

Your flows, messages, and schedules do not change. Only the sender address changes.

When a shopper replies, the reply goes to your organization's support email.
If you have not set a support email, replies go to Moshi.
Replies never go to the sending address, so that address does not need an inbox.

## Choose a sending method

Open the Sending method menu. Choose one of three options.

| Method | Shoppers see | Choose it when |
| - | - | - |
| Moshi default | Moshi's address | You want no setup. This is where every organization starts. |
| Verify your domain | Your address, like `deals@yourstore.com` | **Recommended for most stores.** You can add a few DNS records to your domain. |
| Your own SMTP server | Your address, sent through your email provider | You already send through a provider such as SendGrid, Postmark, or Mailgun, and you want Moshi's emails to go through it too. |

Only one method is active at a time. The active method shows an Active label.
Moshi keeps the saved details of the other methods, so you can switch back later.

## Verify your domain

Moshi gives you a few DNS records. You add them at your domain host. After the records are found, shopper emails go out from your address.

**1. Enter your sender details**

In Sending method, select Verify your domain. Fill in the three fields:

| Field | What to enter | Example |
| - | - | - |
| Your domain | The domain you send from. | `yourstore.com` or `mail.yourstore.com` |
| Email address | The part before the @. Use letters, numbers, and `. _ % + -` only. | `deals` |
| Sender name | The name shoppers see in their inbox, usually your brand name. | `Your Store` |

Moshi shows a preview, such as "Shoppers will see: Your Store \<[deals@yourstore.com](mailto:deals@yourstore.com)>".

**2. Select Set up domain**

Moshi creates your DNS records and shows them under DNS records.
The status changes to Waiting for DNS.

**3. Add the DNS records at your domain host**

Add every record in the table, exactly as shown. Use the copy buttons next to each Name and Value.
Select Copy all records to send the full list to the person who manages your DNS.
See [Add the records at your DNS host](#add-the-records-at-your-dns-host) for host-specific help.

**4. Select Verify**

Moshi asks its email provider, Resend, to check your records.
The check usually takes a few minutes. The page updates on its own.
Moshi also keeps checking on its own while the status is Waiting for DNS.

**5. Confirm the Verified status**

When the status shows Verified, the panel shows "Sending as" with your sender name and address.
New shopper emails now go out from your address.

> [!NOTE]
>
> Until your domain is verified, shopper emails keep going out from Moshi's address. No email is lost while you wait.

### The DNS records

You see three kinds of records. Your table shows the exact names and values for your domain.

| Type | Name | Purpose |
| - | - | - |
| TXT | `resend._domainkey` | Signs your emails (DKIM), so inboxes can confirm they really came from you. |
| MX | `send` | Handles bounce messages for the sending subdomain. |
| TXT | `send` | Lists the servers allowed to send for that subdomain (SPF). |
| CNAME | Shown in your table | Lets Moshi count when shoppers open an email. |

These records sit on `send` and `resend._domainkey` under your domain.
They do not change your normal email. Your existing inbox, MX records, and SPF record keep working.

### Status labels

| Status | Meaning |
| - | - |
| Not set up | You have not entered a domain yet. |
| Waiting for DNS | Moshi has not found all the records yet. Emails go out from Moshi's address. |
| Verified | Your records are found. Emails go out from your address. |
| Failed | The records were not found in time. See [Troubleshooting](#the-status-shows-failed). |

### Root domain or subdomain

You can use your main domain, like `yourstore.com`, or a subdomain, like `mail.yourstore.com`.
Shoppers see the address on the domain you enter, so `deals@mail.yourstore.com` for a subdomain.

Most stores use the main domain, because the address looks the most familiar.
The records go on the `send` and `resend._domainkey` subdomains either way, so your inbox is not affected.
Use a subdomain if your IT team asks you to keep marketing mail separate.

A domain can be connected to only one Moshi organization.
Moshi's own domain, `moshi.ai`, cannot be used.

## Add the records at your DNS host

Add the records where your domain's DNS is managed. This is often the company where you bought the domain.
If your domain points to another DNS service, such as Cloudflare, add the records there instead.

> [!WARNING]
>
> Most DNS hosts add your domain to the end of the Name for you.
> Enter only the part Moshi shows, like `send` or `resend._domainkey`.
> If you enter `send.yourstore.com`, the record can become `send.yourstore.com.yourstore.com`, and verification fails.

General rules for every host:

* **Name**: Paste the Name from Moshi without your domain.
* **Value**: Paste the full Value. Do not add or remove characters.
* **MX priority**: Use the Priority from Moshi. If the host asks for a priority you already use, try `20` or `30` instead.
* **Existing records**: Do not delete your current records. Add the new ones next to them.

| DNS host | Where to add records | Notes |
| - | - | - |
| Shopify (domain bought through Shopify) | In Shopify admin, go to Settings, then Domains. Select the domain, then select Manage in DNS settings. Select Add custom record. | Choose the record type, then fill in the Name and Value from Moshi. |
| GoDaddy | Sign in, open DNS, and select your domain. | Enter only `send` or `resend._domainkey` as the Name. |
| Cloudflare | Open your domain, then DNS, then Records. Select Add record. | Set the CNAME record's Proxy status to DNS only (grey cloud). TXT and MX records are always DNS only. |
| Namecheap | Open Domain List, select Manage, then open Advanced DNS. | Add TXT and CNAME records under Host records. Add the MX record under Mail Settings with Custom MX. The priority goes in the unlabeled column after Value. |
| Squarespace (including former Google Domains) | Open your domain in the Squarespace domains dashboard. Go to Custom records and select Add record. | The MX value goes in Mail Server. The TXT value goes in Text. |
| Amazon Route 53 | Open Hosted zones, select your domain, then select Create record. | There is no Priority field. Put the priority, then a space, then the Value from Moshi, like `10 <value>`. |

> [!WARNING]
>
> On Namecheap, switching Mail Settings to Custom MX replaces the mail setting you had before, such as Gmail.
> If you use Gmail, add Gmail's MX records under Custom MX too. Otherwise your normal inbox stops receiving mail.

Domains that moved from Google Domains to Squarespace can no longer edit records in Google Domains DNS.
Manage the records in Squarespace, or at the DNS provider your domain now uses.

Resend publishes step-by-step guides for many hosts in its [DNS provider guides](https://resend.com/docs/knowledge-base/introduction).

## Use your own SMTP server

Moshi connects to your email provider and sends shopper emails through it.
Before Moshi saves the settings, it sends a test email to your own Moshi login address.

**1. Get your SMTP details**

Find the SMTP host, port, username, and password in your email provider. See [SMTP settings for common providers](#smtp-settings-for-common-providers).
In most providers, you must also verify your sending domain or address there first.

**2. Fill in the form**

In Sending method, select Your own SMTP server. Fill in the fields:

| Field | What to enter |
| - | - |
| SMTP host | The server name, like `smtp.yourprovider.com`. |
| Port | 587 or 465 for most providers. Moshi accepts 25, 465, 587, and 2525. |
| Security | Moshi picks TLS for port 465 and STARTTLS for other ports. Change it only if your provider says so. |
| Username | The SMTP username from your provider. |
| Password | The SMTP password, API key, or app password from your provider. |
| From email | The address shoppers see, like `deals@yourstore.com`. |
| From name | The name shoppers see, usually your brand name. |

**3. Select Send test and save**

Moshi sends an email with the subject "Test email from Moshi" to your address.
If your server accepts it, Moshi saves the settings and shows "Test email sent. Your SMTP server is active."
If the test fails, Moshi shows the reason and saves nothing.

**4. Check your inbox**

Open the test email. Confirm the sender name and address look right.

> [!NOTE]
>
> Port 25 is blocked from Moshi's servers. Use port 587 or 465.

How Moshi handles your password:

* Moshi stores the password securely and never shows it again. The form shows "•••• saved".
* To change the password, select Replace and enter a new one.
* If you change the host, port, security, or username, enter the password again. Moshi never sends a saved password to a different server.
* Security set to None sends your password without encryption. Use TLS or STARTTLS unless your provider requires otherwise.

You can run up to 10 tests per hour. After that, Moshi shows "Too many test emails — try again in an hour."

### What SMTP does not give Moshi

Bounces and spam complaints go to your email provider, not Moshi.
Moshi cannot stop emailing addresses that your provider has flagged. Check your provider's dashboard for bounces and suppressions.

Moshi sends each email over its own connection.
A large broadcast can reach your provider's per-minute or per-day limit.
If your provider refuses emails, the rest go out from Moshi's address, and the Email page shows a warning.

### SMTP settings for common providers

These settings come from each provider's own documentation. Check your provider's dashboard for the exact values for your account.

| Provider | SMTP host | Port and security | Username | Password |
| - | - | - | - | - |
| SendGrid | `smtp.sendgrid.net` | 587 STARTTLS, or 465 TLS | `apikey` (type this word exactly) | An API key with Mail Send access |
| Postmark | `smtp.postmarkapp.com` | 587 STARTTLS | Your Server API token, or an SMTP token Access Key | The same Server API token, or the SMTP token Secret Key |
| Mailgun | `smtp.mailgun.org` (US) or `smtp.eu.mailgun.org` (EU) | 587 STARTTLS, or 465 TLS | The SMTP login for your domain | The SMTP password for that login |
| Resend | `smtp.resend.com` | 587 STARTTLS, or 465 TLS | `resend` | Your Resend API key |
| Amazon SES | `email-smtp.<region>.amazonaws.com`, like `email-smtp.us-east-1.amazonaws.com` | 587 STARTTLS, or 465 TLS | Your SES SMTP username | Your SES SMTP password |
| Google Workspace or Gmail | `smtp.gmail.com` | 587 STARTTLS, or 465 TLS | Your full Google email address | An app password |
| Microsoft 365 | `smtp.office365.com` | 587 STARTTLS | The mailbox's full email address | The mailbox password |

Provider notes:

* **SendGrid**: The username is the literal word `apikey`, not your API key. Authenticate your domain in SendGrid first.
* **Postmark**: Postmark sends one-to-one email and bulk email through separate message streams. The default stream is for one-to-one email. Moshi sends discount codes, follow-ups, and broadcasts through one server, so ask Postmark which stream fits your mix.
* **Mailgun**: SMTP logins belong to one sending domain. Find them in Mailgun under Sending, then Domain settings, then SMTP credentials. Use the host for your account's region.
* **Amazon SES**: SMTP credentials are not your AWS access keys. Create them in the SES console under SMTP settings. They work in one region only. New SES accounts start in a sandbox that sends only to verified addresses, so request production access before you go live.
* **Google Workspace or Gmail**: App passwords need 2-Step Verification. Create one on your Google Account's app passwords page. Google Workspace limits this method to 2,000 messages per day. Some work accounts cannot create app passwords; ask your Workspace admin.
* **Microsoft 365**: Your admin must turn on SMTP AUTH for the mailbox. Microsoft limits this method to 30 messages per minute and 10,000 recipients per day. Microsoft plans to turn off password sign-in for SMTP by default at the end of December 2026. Prefer a dedicated sending service for broadcasts.

Sources: [SendGrid](https://www.twilio.com/docs/sendgrid/for-developers/sending-email/integrating-with-the-smtp-api), [Postmark](https://postmarkapp.com/developer/user-guide/send-email-with-smtp), [Mailgun](https://documentation.mailgun.com/docs/mailgun/user-manual/sending-messages/send-smtp), [Resend](https://resend.com/docs/send-with-smtp), [Amazon SES](https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html), [Google Workspace](https://knowledge.workspace.google.com/admin/gmail/send-email-from-a-printer-scanner-or-app), [Google app passwords](https://support.google.com/accounts/answer/185833), [Microsoft 365](https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365).

## Check that it works

1. Open the Email page. Confirm the method you set up shows Active.
2. For a domain, confirm the status shows Verified. For SMTP, confirm the test email arrived.
3. Confirm that no warning shows at the top of the page.
4. Send yourself a real shopper email. For example, claim a discount code in your own flow with your email address.
5. In the email, check the sender name and address. Reply to it and confirm the reply reaches your support inbox.

> [!TIP]
>
> If the email shows your sender name and address, and the Email page shows no warning, your setup works.

## Switch back to Moshi's address

In Sending method, select Moshi default, then select Use Moshi default.
Shopper emails go out from Moshi's address again right away.
Moshi keeps your domain or SMTP details. To use them again, select the method and select Use this domain or Send test and save.

To change your domain or address later, select Change domain. You must add the DNS records again for a new domain.

## If your setup stops working

Moshi never drops a shopper email because of a sending problem.
If your domain or SMTP server cannot send, the email goes out from Moshi's address.
The Email page then shows a warning that explains why.

| Warning | What to do |
| - | - |
| Your domain isn't verified yet, so shopper emails go out from Moshi's address. | Add the DNS records, then select Verify. |
| Your domain's DNS records aren't verified, so shopper emails go out from Moshi's address. | Compare each record at your DNS host with the table in Moshi. Fix any difference, then select Verify. |
| Your domain's DNS records are no longer verified, so shopper emails go out from Moshi's address. | A record was changed or removed. Add it again exactly as shown, then select Verify. |
| Your domain is no longer set up for sending, so shopper emails go out from Moshi's address. Enter your domain again to set it up. | Enter your domain again and select Use this domain. Then add the new DNS records Moshi shows. |
| Your SMTP settings are incomplete. Open them and save again. | Open Your own SMTP server, fill in every field, and select Send test and save. |
| We couldn't read your saved SMTP password. Enter it again. | Select Replace, enter the password, and select Send test and save. |
| We couldn't use your SMTP settings right now — contact support. | Contact the Moshi team. Your emails still go out from Moshi's address. |
| Your email sending method can't be used right now, so shopper emails go out from Moshi's address. | Check your domain status or SMTP settings. Contact the Moshi team if the warning stays. |

For SMTP, the warning can also show the last error from your server. See [SMTP errors](#smtp-errors).
After a fix, the warning clears when your domain is verified again or the next email sends successfully.

## Troubleshooting

### The status stays on Waiting for DNS

* **Wait a little**: DNS changes can take from a few minutes to a few hours to appear. Select Verify again later.
* **Check the Name**: Look for a doubled domain, like `send.yourstore.com.yourstore.com`. Enter only the part Moshi shows.
* **Check the Value**: Copy it again with the copy button. A missing character breaks the record.
* **Check the right place**: Add records where your DNS is actually managed. If your domain uses Cloudflare, records at your registrar do nothing.
* **Check the Cloudflare proxy**: Set the CNAME record to DNS only.
* **Check for duplicates**: Remove an older record with the same Name and type if it has a different value.

### The status shows Failed

The records were not found within about 72 hours.
Fix the records using the checks above. If Verify still shows, select it.
If the DNS records table is empty, enter your domain again and select Use this domain. Then add the records Moshi shows.

### Domain setup messages

| Message | What to do |
| - | - |
| Enter a domain you own, like mail.yourstore.com, and a from address without spaces | Enter only the domain, without `https://` or `www.`. Check the Email address field for spaces. |
| Use only letters, numbers and . \_ % + - (no spaces or @), like deals | Enter only the part before the @ in Email address. |
| This domain is already in use — contact support | The domain is connected to another Moshi organization. Contact the Moshi team. |
| We couldn't set up your domain right now — contact support | Try again later. Contact the Moshi team if the message stays. |

### SMTP errors

In these messages, Moshi shows your server's name, like `smtp.yourprovider.com`.

| Message | What to do |
| - | - |
| We couldn't sign in to your server. Check the username and password. | Copy the username and password again. For SendGrid, the username is `apikey`. For Gmail, use an app password. For Microsoft 365, ask your admin to turn on SMTP AUTH. |
| Your server on port 25 didn't respond in time. Many networks block port 25; try port 587 or 465 instead. | Change Port to 587 or 465. |
| Your server didn't respond in time. | Check the host and port. Try 587 with STARTTLS, or 465 with TLS. |
| We couldn't connect to your server. | Check the host spelling and port. The server refused the connection or is not reachable. |
| We couldn't make a secure connection. Check the security setting and the server's certificate. | Use TLS with port 465, or STARTTLS with port 587. |
| We couldn't find that host. Check the spelling. | Fix the SMTP host. |
| That host points to a private network address, which Moshi can't connect to. | Use your provider's public SMTP host. |
| Use port 25, 465, 587 or 2525. | Choose one of these ports. |
| Your server refused the sender address. | Verify the From email or its domain in your email provider. |
| Your server refused the message. | Read the server reply that Moshi shows. It often names a sending limit or an unverified sender. |
| Use a from address on your own domain, not Moshi's. | Change From email to an address on your domain. |
| Enter your SMTP password. | Enter the password. It is required after you change the host, port, security, or username. |
| Too many test emails — try again in an hour. | Wait an hour, then try again. |

## FAQ

### Does this change my existing flows?

No. Your flows, offers, and schedules stay the same. Only the sender address on shopper emails changes.

### Do I need a real inbox for the sending address?

No. Replies go to your organization's support email, not to the sending address.

### What happens if someone deletes the DNS records later?

Moshi checks your domain regularly.
If a record disappears, emails go out from Moshi's address, and the Email page shows a warning.
Add the record again and select Verify.

### Can I switch back to Moshi's address?

Yes. Select Moshi default, then Use Moshi default. Your other settings stay saved.

### Will this affect my regular business email?

Verifying your domain adds records only on the `send` and `resend._domainkey` subdomains.
Your inbox and existing email records keep working.
The SMTP option does not change your DNS.

### Should I use my main domain or a subdomain?

Most stores use their main domain. See [Root domain or subdomain](#root-domain-or-subdomain).

### Can I use the same domain in two Moshi organizations?

No. A domain can be connected to only one Moshi organization. Use a different subdomain for the second organization, like `mail.yourstore.com`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.