Change how your community's emails reach members: the sender name and address, where replies go, the welcome email new members get, and the email alerts your team receives. You can also send your community's email through your own mail server.
Who can do this: Community owners and admins. · Where: Web (admin console). · Plan: The welcome email, renewal receipts, admin notifications, and new member notifications are available on every platform plan. Saving a custom sender (Sender Identity) and Custom SMTP each depend on your platform plan.
Open the email and notification settings
Go to Admin → Settings → Email & Notifications. The page has three sections saved together: Sender Identity, System Notifications, and Admin Notifications. After making changes, click Save Changes at the bottom of the page. Custom SMTP and New member notifications, below them, save on their own.
A section your plan doesn't include shows Upgrade to unlock, and its fields can't be edited. If you move to a plan without a custom sender or Custom SMTP, your emails go back to Mateflow's default sender and sending service. Your settings are kept and apply again when you upgrade.
Change the email sender name, From address, and Reply-To address
In Sender Identity, a line shows the address your emails to members currently go out as, and where replies go. Every field here is optional:
- From Name: the name shown in members' inboxes. When it's empty, your community's name is used.
- From Email Address: the address your emails come from, on your own domain. It's used only after you verify the domain (see the next section).
- Reply-To Address (optional): where members' replies go, such as your support inbox. If it's empty or your plan doesn't include a custom sender, replies go to the Support email in Admin → Settings → General. With neither set, replies go to Mateflow's inbox and never reach you. The broadcast editor and the Community Digest page show the sender and reply address actually used.
When your sender settings take effect:
| Before the domain is verified | After the domain is verified | |
|---|---|---|
| Broadcasts | Your From Name, sent from Mateflow's default sender address | Your From Name and From Email Address |
| Transactional emails, such as the welcome email, notifications, invitations, and verification codes | Your community's name, sent from Mateflow's default sender | Your From Name and From Email Address |
If you use Custom SMTP, your own server sends those emails, so they use your From Email Address without a verified domain. Broadcasts always go through Mateflow, so they still need one.
Verify your own sending domain
To use your own From address, save From Email Address, then open Set up domain under Sending domain verification.
- Click Get DNS records if no records are shown.
- Add every DNS record at your domain provider, copying its type, name, and value. In Cloudflare, CNAME records must use DNS only (grey cloud).
- Return to the dialog and click Verify. Verification can take up to 48 hours while DNS propagates.
Until verification succeeds, email uses Mateflow's default sender. Save unsaved From-address changes before verifying. If the domain belongs to another account, use a different domain or contact support. Mateflow rechecks verified domains daily; if a check fails, it falls back to the default sender and notifies owners and admins. Fix the records and verify again.
Edit the welcome email for new members
The welcome email is sent automatically when someone registers. In System Notifications:
- Turn on Send Welcome Email.
- Enter a Welcome Email Subject and write the Welcome Email Body. Both are required while the welcome email is on.
- Before you save, click Send test to myself to get a test at your own address, or Preview to see the email as members get it, with the variables filled in from your own account. Testing doesn't save anything.
- Click Save Changes.
Write the body as plain text or HTML. Plain text keeps its line breaks, and web addresses become links. Either way, your community's name is added at the top and a footer at the bottom, with the footer in each member's language. A full HTML document (with an <html> tag) is sent as written, without the name and footer.
The subject and body can include these variables:
{username}: the member's display name{site_name}: your community's name{app_download_url}: a link to download the Mateflow app. It's left empty if your platform plan removes Mateflow branding.
To stop sending it, turn off Send Welcome Email. The welcome email is separate from the welcome message members see inside the community. See Set up new-member onboarding.
Turn renewal receipts for paying members on or off
After each successful automatic renewal of a member's subscription, your community emails the member a receipt with the amount and an invoice link. This is on by default. To stop these emails, turn off Send renewal receipts to members in System Notifications and click Save Changes.
The switch covers renewals only. The confirmation email for a member's first subscription and reminders about failed payments always go out. See Connect Stripe and get paid.
Get an email when a new member joins
In Admin Notifications, turn on Notify on New Members ("Email administrators when a new member joins") and click Save Changes.
The email goes to the community owner and every admin with an email address. Moderators and custom roles don't get it. It's sent when someone becomes a full member: they sign up with email, social login, or single sign-on (SSO), complete a paid sign-up, or have their join request approved. Each recipient gets their own email.
Set default notifications for new members
New member notifications decides what members who join from now on start with. Existing members aren't affected, and anyone can change their own settings later. Until you change it, new members start with email off and everything else on.
- Email: New followers, New comments, New reactions, and Mentions. New members will really get these emails, which counts toward your email usage.
- In the community: New followers, New comments, and New reactions.
- Push notifications: on or off.
Each change saves right away.
Send community email through your own SMTP server
Custom SMTP sends most of the email your community sends to members, including the community digest, through your own mail server instead of Mateflow's sending service. Broadcasts are the exception: "Broadcast emails are always sent through Mateflow, so opens and clicks can be tracked."
- Click Set up, or Edit if a server is already saved. Enter the SMTP Host, Port, Username, and Password from your email provider.
- Keep Require encryption (previously called Use TLS/SSL) on. Port 465 uses TLS; other ports use STARTTLS. On, sending fails if the server can't encrypt. Off, it still encrypts when the server can.
- Click Test connection to try the details in the form. To check delivery as well, enter an address under Send a test email to and click Send test email. A failed test says where it failed: reaching the server, encryption, the username or password, or sending. If you change SMTP Host, enter the password again.
- Click Save. If these details haven't passed a test, you're asked to confirm first.
Custom SMTP has no fallback. If your server fails, Mateflow retries the email but doesn't send it through its own service instead, so wrong details mean signup verification codes, invitations, and notification emails aren't delivered. Password reset emails always go through Mateflow. If an email still can't be sent after the retries, owners and admins get an email about it, at most one a day, and Custom SMTP shows when it last failed and at which step. To go back to Mateflow's default sending, click Remove, which also deletes the username and password. After saving, the password isn't shown again; leave the field blank to keep it. Community digest emails sent through your own server have no open or click tracking.
What members control about their notification emails
Members decide which notification emails they get, and you can't change their settings for them. In Settings → Notifications, each member picks channels and categories, sets how often they get a Notification summary email (previously called Email Digest Frequency), and can turn off Marketing Emails, which covers broadcast emails and the community digest. See Choose your notifications.
Broadcast emails and the community digest include an unsubscribe link. Opening it changes nothing by itself: the page asks the member to click Unsubscribe, and they can undo it within 30 minutes with That was a mistake — resubscribe. The link in a broadcast email stops both broadcast emails and the digest; the link in the digest stops only the digest.
Other automatic emails, such as verification codes, have fixed content. To write your own emails to members, send a broadcast or set up the community digest.
Related articles
Was this guide helpful?