Who sends what
Emails to your customers come from you, through your own email server. Emails to you and your team come from MINT.
| Sent by | |
|---|---|
| A welcome to each customer who signs up on your sites | You — through the project’s default email account, from your address |
| Order receipts, automation emails | You — the same way |
| Your welcome to MINT, invitations to your organization | MINT |
| Password resets, sign-in and verification codes | MINT |
Until a project has an email account (or your organization has a server), its customers get no emails from you — signing up on your sites still works. MINT doesn’t send anything to your customers in its own name.
A project’s email accounts
Inside a project: Project → Email. Connect the accounts the project sends from — Sales, Support, as many as you like.
Each row shows the account’s name, the sender name and address, the server, and whether it works: Working (green) after a check or an email that went out, Not working (red) with the reason after one that didn’t. The ⋯ menu on a row has Make default, Edit, Send a test email and Remove.
Connecting an account
Connect an account opens a window. Fill it in, press Test connection, then Connect.
| Field | What to put |
|---|---|
| Account name | For your team, to tell accounts apart — e.g. Sales. Empty: the address. |
| Sender name | The name people see the email is from — e.g. your shop’s name. |
| Email provider | Optional: pick yours to fill in the server and port. |
| SMTP server | Your host’s outgoing server, e.g. smtp.gmail.com. |
| Port | 587 (secured after connecting) or 465 (secured from the start). The security follows the port. |
| The address emails come from. It’s also the sign-in. | |
| Password | The account’s password — or an app password for Gmail and Outlook. |
Test connection signs in to the server without sending anything. Green means it connected and the password was accepted; red says what went wrong in plain words. Changing any field clears the answer, so test again. Saving checks once more and shows the result on the row; an account that fails is still saved, so you can fix it later with Edit.
The default account
Send from, at the top of the list, picks the default. Every email the project sends goes through it.
- The first account you connect becomes the default.
- Removing the default makes the oldest account left the default; removing the last one sends the project’s emails back to your organization’s server, or stops them if it has none.
- Send a test email (in a row’s ⋯ menu) goes through that account, whether it’s the default or not — to you, or any address.
How your emails look
Project → Email → How your emails look. Design the frame every email from the project goes out in — receipts, welcomes, automation emails and tests.
New design opens a window: the settings on the left, a sample email on the right that changes as you do — at desktop or phone width. What you see is exactly what your customers get. A project can have several designs (Receipts, Newsletter…); the Default one is used unless an automation picks another. The ⋯ menu on a row has Make default, Send a test email and Remove.
Plain or designed
Two looks to start from.
| Look | What your customer sees |
|---|---|
| Plain | Just your words, a link and your signature — like an email you wrote yourself. Good for a personal tone, and it rarely lands in spam. |
| Designed | Your logo or name in a coloured header, the message on a card, a button, and a small footer with your details. |
Font offers the fonts every email app has (Helvetica, Georgia, Trebuchet…), so it looks the same in Gmail, Outlook and on phones. Start from colours sets the header, buttons and background in one click — change any of them after.
The header
Designed only. Turn it off for no band at the top.
- Logo — upload one or pick it from the media library. Use PNG or JPG: Gmail and Outlook don’t show SVG in emails. It starts as your business logo.
- Title — text beside the logo, or on its own.
{{business.name}}fills in your business name; leave it empty for the logo alone. - Logo height, line up (left or centre), background and title colour.
Colours and shape
Click a swatch to pick a colour, or type it like #1f2937.
| Setting | What it colours |
|---|---|
| Text | The message. |
| Buttons (Links on a plain email) | The button — “View your order” — or the link on a plain email. |
| Heading, Button text | The large line at the top of the card, and the words on the button. |
| Card, Around the card | The white box the message is in, and the background around it. |
| Corners | Square, soft, round or rounder — the card and its button. |
| Width | 560 px is usual; 480 is narrower, 640 wider. Phones always show it full width. |
A design for one automation
In an automation’s Send an email, Design picks how that email looks.
The default follows whichever design is the project’s default. Pick another — a plain one for a personal follow-up, say — and only that email uses it. If that design is removed, the email goes out in the default.
Your organization’s email server
Organization → Email. One server for the whole organization — used by every project that hasn’t connected its own account.
Your email host gives you these details (often under “SMTP”, “outgoing mail” or “email clients”):
| Setting | What to put |
|---|---|
| Server | The outgoing (SMTP) server, e.g. smtp.gmail.com. Pick your provider to fill it in. |
| Port and SSL | Usually 587 with SSL off (the connection is secured after it starts), or 465 with SSL on. |
| Username and password | Usually your full email address and its password — or an app password, see below. |
| From name | What customers see as the sender. Empty: your organization’s name. |
| From address | The address emails come from. Most servers only send as the account you sign in with. |
| Replies go to | Where customers’ replies land, if not the from address — e.g. a shared inbox. |
| Welcome customers | On: a short welcome to everyone who creates an account on your sites. |
Common providers
| Provider | Server · port · SSL |
|---|---|
| Gmail / Google Workspace | smtp.gmail.com · 587 · off. Turn on 2-step verification, then make an app password (Google Account → Security → App passwords) and use that. |
| Outlook / Microsoft 365 | smtp.office365.com · 587 · off. Your Microsoft 365 admin may have to allow “Authenticated SMTP” for the mailbox. |
| Zoho Mail | smtp.zoho.com · 465 · on (smtp.zoho.eu or smtp.zoho.in for accounts in Europe or India). |
| Namecheap Private Email | mail.privateemail.com · 465 · on |
| Hostinger | smtp.hostinger.com · 465 · on |
Sending a lot? Gmail and Outlook limit how many emails a mailbox sends a day (a few hundred to two thousand). For newsletters, a sending service with SMTP (Brevo, Mailgun, Postmark, SendGrid, Amazon SES) works the same way: put in its SMTP server and the username and password it gives you.
Testing it
After saving, send a test — to yourself, or to any address.
The test goes out exactly like your customers’ emails. If it works, the page says Working; if not, it says why in plain words — a wrong password, a wrong port, a server that can’t be reached — and the same reason is kept until the next email goes out.
What was sent
Each Email page lists the last 50 emails: when, what kind, to whom, the subject, and whether it went.
A project’s page shows that project’s emails and which account each went through; the organization’s page shows them all. For most emails only the subject is kept. Automation emails keep their message too: the eye shows one as it went out, and a failed one has Resend — see Automations → seeing and resending emails. Entries go after 180 days.
Troubleshooting
| It says | What to do |
|---|---|
| refused the username or password | Check both. Gmail and Outlook usually need an app password, not your normal password. |
| didn’t answer on port … | Try 587 with SSL off, or 465 with SSL on. |
| The secure connection failed | Switch SSL: on for 465, off for 587. |
| wouldn’t take this address | The address may not exist, or the server won’t send to it. Check the spelling. |
| The test arrived in spam | Your domain needs SPF and DKIM records for the server you use — your email host’s help pages show what to add. |
- Changing the server, port, SSL, username or password marks it as not tested — send a test again.
- Removing the server stops your emails at once; the log stays.