Email setup
This page explains how to configure email so Mambu can send manual and automated notifications, as well as system emails (such as password resets and user invitations).
- With a custom SMTP server, emails are sent from your own domain using the credentials you provide.
- If no custom SMTP is configured, system emails continue to be sent from a Mambu-managed sender. The Email channel for notifications may be disabled in the UI when no custom SMTP is selected.
Once you configure a custom email server, it will also be used for system messages such as password reset emails and user invitations. After changing settings, always verify that these flows still work as expected.
Prerequisites and permissions
- Navigation:
Administration > Email > Settings - To view settings: Users with administration visibility or template permissions can view the configuration (for example, View Administration Details, Create Templates, or Edit Templates).
- To change and save settings: Admin permission is required.
- After any change, verify end-to-end by sending a test email and checking a password reset or invitation flow.
Configure your email server in Mambu
To set up an email server in Mambu:
- On the main menu, go to Administration > Email > Settings. The Settings tab is only visible to users with the required permissions.
- Choose the email provider option:
- Custom SMTP – use your own SMTP server and credentials.
- Mambu-managed sender – leave Custom SMTP disabled.
- If you select Custom SMTP, fill in the fields described below and select Save Changes.
- Optionally, use Send Test Email to validate connectivity before saving. The test uses the values currently in the form and does not persist them.
We strongly recommend always testing after setup and making any changes by sending yourself a test email and validating key flows such as password reset.
Form fields to set up email server
| Field | Description |
|---|---|
| From Name | The display name reported as the sender's name in the email. Often your organization name, such as Mid City Bank. |
| From Email | The email address reported as the sender's email in the email, such as info@midcity.bank. Used as the From: address when sending via your SMTP. |
| Reply-to email | The reply address email. Often the same as the From Email. Replies from recipients are sent here. |
| SMTP Host | The DNS address of the email server. For example: smtp.example.com. |
| SMTP Port | The port used to communicate with the host. Common values are 465 or 587, depending on the provider and encryption method. |
| Transport Encryption Method | The encryption method used to secure the SMTP connection. Supported: SSL/TLS (implicit TLS, usually port 465) and STARTTLS (explicit TLS, usually port 587). |
| Username | The username part of the credentials to use the SMTP host. Often the full email address. |
| Password | The password part of the credentials to use the SMTP host. Stored encrypted in Mambu. |
Notes:
- When Custom SMTP is selected, Mambu attempts to send via your SMTP first and may fall back to a Mambu-managed no-reply sender if the primary attempt fails.
- If Custom SMTP is not selected, system emails continue to be sent from a Mambu-managed sender. The Email channel for notifications may be disabled if no valid configuration is present.
After configuring SMTP, send yourself a test email and also trigger a password reset or user invitation to validate both notification and system emails.
Send Test Email
Use Send Test Email to try sending a message with the current form values without saving the configuration.
What the test checks
- Resolves the SMTP host and attempts to connect using the selected encryption method.
- Tries to authenticate with the provided username and password.
- Attempts to submit a test email for delivery.
What the test does not guarantee
- Final delivery to the recipient’s inbox. Spam filtering, DMARC/DKIM alignment, and downstream provider issues are outside the scope of this test.
Common causes of test failures
- Invalid hostname, wrong port, or encryption mismatch (SSL/TLS vs STARTTLS).
- Wrong credentials or missing app-specific passwords.
- Firewall or allowlisting rules blocking Mambu egress IPs from reaching your SMTP on the selected port.
Examples for common email service providers
If you already use a trusted email service provider such as Google Workspace/Gmail or Amazon SES, you can connect it via SMTP. For more advanced email workflows (marketing journeys, complex templates, etc.), consider using Webhooks to trigger sending email templates through your existing service.
Google Workspace / Gmail SMTP
The Google Workspace platform or Gmail can be used as an email service provider. Example configuration:
| Field | Description |
|---|---|
| From Name | Any string. Google may override this value with the default value from the account. |
| From Email | Gmail or Google Workspace address. Google may override this value with the default value from the account. |
| Reply-to email | Gmail or Google Workspace address. Often the same as From Email. |
| SMTP Host | smtp.gmail.com |
| SMTP Port | 465 (SSL/TLS) or 587 (STARTTLS) |
| Transport Encryption Method | SSL/TLS or STARTTLS, depending on the chosen port. |
| Username | Full Gmail or Google Workspace user, such as mambu@gmail.com or hello@mambu.com. |
| Password | Application-specific password or SMTP relay credentials, depending on your Google security settings. |
Check Google’s documentation for the latest requirements on app passwords, 2-step verification, and SMTP relay.
Amazon Simple Email Service (SES)
Amazon SES can be used as an email service provider. You must have an AWS account and SES configured for your domain.
| Field | Description |
|---|---|
| From Name | Any string, usually the name of your organization. |
| From Email | Full email address to display in the From: field. Must be verified in SES depending on your configuration. |
| Reply-to email | Full email address used when replying to the email. This can be the same as From Email. |
| SMTP Host | Regional SES SMTP endpoint, for example email-smtp.eu-west-1.amazonaws.com. Use the endpoint for your SES region. |
| SMTP Port | Typically 465 (SSL/TLS) or 587 (STARTTLS). |
| Transport Encryption Method | SSL/TLS or STARTTLS, matching the chosen port. |
| Username | The username from your SES SMTP credentials. |
| Password | The password from your SES SMTP credentials. |
Ensure your DNS and domain authentication (SPF, DKIM, DMARC) are correctly configured with your provider to improve deliverability and reduce the risk of messages being flagged as spam.
IP address ranges
Emails being sent through your SMTP server from Mambu will originate from a fixed set of IP addresses per Mambu region. If your SMTP server or firewall requires allowlisting, you may need to allow these IP addresses.
- Any updates to infrastructure will be announced on our Status Page.
- If you need to know the current sender IP addresses for your dedicated environment or region, please contact Mambu Support.
Troubleshooting
- The Send Email options don’t appear in the UI:
- Ensure the Email channel is enabled in Administration > Email > Settings.
- Verify your user role has the necessary permissions to send notifications.
- Test email fails to send:
- Double-check SMTP host, port, and encryption method.
- Verify username/password or app password requirements with your provider.
- Confirm your firewall allows Mambu IPs to reach your SMTP on the selected port.
- System emails not received after changes:
- Trigger a password reset or user invitation to test.
- Check spam/junk folders and domain authentication settings (SPF/DKIM/DMARC).
- If issues persist, review your SMTP logs and contact your email provider or Mambu Support.
If none of the above helps, see this page