Skip to main content

Sending Nodes

Sending nodes are your email delivery channels—SMTP servers or email service provider (ESP) connections that relay your campaigns to recipients. Configure multiple nodes to distribute sending load, separate transactional from marketing emails, or use different providers for different purposes.

Overview​

A sending node connects Mumara Campaigns to an email delivery service:

+------------------+      +------------------+      +------------------+
|  MUMARA          | ---> |  SENDING NODE    | ---> |  RECIPIENT       |
|  CAMPAIGNS       |      |  (SMTP/ESP)      |      |  MAILBOX         |
+------------------+      +------------------+      +------------------+
                                 |
                                 v
                        +------------------+
                        |  - Authentication |
                        |  - Rate Limiting  |
                        |  - Tracking       |
                        +------------------+

Mumara ONE​

Featured Integration

Mumara ONE is Mumara's proprietary email sending solution—engineered for seamless, native integration with Mumara Campaigns.

Why Choose Mumara ONE​

BenefitDescription
Native IntegrationBuilt specifically for Mumara Campaigns with zero configuration friction
Simplified SetupJust enter your API token—no complex webhook or DNS configuration
Full Delivery ReportsAutomatic bounce, delivery, and complaint tracking out of the box
Optimized PerformanceInfrastructure tuned for high-volume email delivery
Priority SupportDirect support from the Mumara team

Quick Setup​

  1. Navigate to Setup → Sending Nodes
  2. Click Add New
  3. Select Mumara ONE as the gateway
  4. Enter your API Token (provided with your Mumara ONE subscription)
  5. Configure sender information
  6. Click Save

That's it—no webhook configuration, no SNS topics, no API permissions to manage.

Recommended for Best Results

For the smoothest experience with Mumara Campaigns, Mumara ONE provides the tightest integration, simplest configuration, and most reliable delivery reporting. If you're unsure which sending node to use, start with Mumara ONE.

Viewing Sending Nodes​

Navigate to Setup → Sending Nodes to view all configured nodes.

Page Features​

  • Add New button to create a node
  • Nodes tab shows all configured sending nodes
  • Servers tab for PowerMTA integration (separate add-on)
  • Our records / User records toggle to filter view
  • Filter by admin dropdown to filter by administrator
  • All dropdown to filter by gateway type (SMTPs, Sendgrid, Mailgun, etc.)
  • Show entries dropdown to control page size
  • Search box to find specific nodes
PowerMTA Add-on

The Servers tab is part of the PowerMTA add-on. PowerMTA configuration is covered in the Add-ons documentation.

Table Columns​

ColumnDescription
Node NameName of the sending node
GroupOrganizational group assignment
TypeGateway type icon and name
From NameSender name configured for this node
StatusActive/Inactive status
Created onDate and time the node was created
ActionsRow action menu

Tools Dropdown​

Select one or more nodes using checkboxes, then choose from:

ActionDescription
Test ConnectionVerify selected nodes can connect
Set as ActiveEnable selected nodes
Set as InactiveDisable selected nodes
Import sending nodesImport nodes from JSON file
Export sending nodesExport selected nodes to JSON
Make a CopyDuplicate selected nodes
DeleteRemove selected nodes

Row Actions​

Click the ... (three dots) menu on any row to access:

ActionDescription
Test ConnectionVerify this node can connect
Set as ActiveEnable this node
Set as InactiveDisable this node
Export to CSV FileDownload node configuration
Make a CopyDuplicate this node
EditModify node settings
DeleteRemove this node

Supported Gateway Types​

GatewayDescriptionBest For
Mumara ONEMumara's proprietary sending solutionFull integration with Mumara Campaigns

Direct SMTP Providers​

GatewayDescriptionBest For
SMTPGeneric SMTP serverSelf-hosted mail servers, custom setups
GmailGoogle's SMTP serviceSmall-volume sending
Gmail OAuth 2.0OAuth-authenticated Gmail APISecure Gmail integration
OutlookMicrosoft Hotmail/Outlook SMTPOffice 365 and Outlook users
YahooYahoo Mail SMTPYahoo account users
AOLAOL Mail SMTPAOL account users

Email Service Provider APIs​

GatewayAuthenticationFeatures
Amazon SESAccess Key + SecretHigh volume, low cost, SNS webhooks
SendGridAPI KeyDeliverability analytics, webhooks
MailgunAPI Key + DomainDeveloper-friendly, powerful APIs
SparkPostAPI KeyEnterprise features, analytics
MailjetPublic + Secret KeysTransactional + marketing
PostmarkAPI TokenTransactional email focus
SMTP2GOAPI KeyGlobal delivery network
Elastic EmailAPI KeyAffordable high-volume sending
SendInBlueAPI KeyMarketing automation features
ZeptoMailAPI KeyTransactional email service
MandrillAPI KeyMailchimp integration

Creating a Sending Node​

Navigate to Setup → Sending Nodes and click Add New.

Basic Settings​

Status​

Toggle to enable or disable the node.

  • Active: Active sending nodes are ready to relay emails and appear in campaign scheduling
  • Inactive: Inactive sending nodes do not appear in the scheduling process

Node Name​

Provide a friendly name for the sending node for identification purposes.

Examples:

  • "Production SMTP - Marketing"
  • "Amazon SES - Transactional"
  • "Mumara ONE - Main"

Group​

Select or create a group to organize your nodes.

Creating a new group:

  1. Click the + button next to the group dropdown
  2. Enter a group name
  3. Click Save

Groups help organize nodes by:

  • Purpose (Marketing, Transactional)
  • Environment (Production, Staging)
  • Team (Sales, Support)

Gateway​

Select the email service provider or SMTP type. The form fields change based on your selection.

SMTP Configuration​

For generic SMTP servers and email providers using SMTP protocol.

Connection Settings​

FieldDescriptionHelp Text
SMTP HostSMTP server addressThe hostname of the SMTP server to connect with
UsernameAuthentication usernameThe username required to authenticate with the SMTP server
PasswordAuthentication passwordThe password required to authenticate with the SMTP server
PortSMTP port numberThe port number to be used for connecting to the SMTP server
EncryptionSecurity protocolNone, TLS, or SSL encryption

Encryption Options​

Encryption ensures that the email content is protected from being accessed by anyone other than the intended recipients.

OptionDescription
NoneNo encryption is applied
TLSTLS is a cryptographic protocol that provides end-to-end security
SSLSSL adds an encryption layer over plaintext communication

Common SMTP Ports​

PortEncryptionUse Case
25NoneUnencrypted (not recommended)
465SSLImplicit SSL/TLS
587TLSSTARTTLS (recommended)
2525TLSAlternative port

SSL/TLS Options​

OptionDescription
Allow Self-Signed CertificatesAccept self-signed SSL certificates
Verify Peer CertificateValidate server SSL certificate
Verify Peer NameValidate certificate hostname matches
Security

Disabling certificate verification reduces security. Only disable for trusted internal servers.

Mail Encoding​

Choose the mail encoding method for emails sent from this node.

EncodingDescription
Quoted-PrintableDefault, ASCII-safe encoding
8-bitDirect 8-bit character transmission
Base64Binary-safe encoding
BinaryRaw binary transmission

Gmail Configuration​

There are two methods to use Gmail SMTP with Mumara Campaigns:

  1. Go to your Google Account → Security
  2. Enable 2-Step Verification if not already enabled
  3. Go to App Passwords
  4. Select "Mail" and your device
  5. Generate and copy the 16-character password
  6. Use this password in the SMTP Password field

Method 2: Using Less Secure Apps​

  1. Go to your Google Account → Security
  2. Enable "Less secure app access"
  3. Use your regular Gmail password
warning

Method 2 is less secure and may be deprecated by Google. App Passwords are recommended.

Gmail SMTP Settings​

SettingValue
Hostsmtp.gmail.com
Port587 (TLS) or 465 (SSL)
Username[email protected]
EncryptionTLS or SSL

Gmail OAuth 2.0 Configuration​

Use OAuth for secure authentication without storing your password.

Setup Steps​

  1. Select Gmail OAuth 2.0 as the gateway
  2. Click Connect Google Account
  3. Sign in to your Google account
  4. Grant permission for Mumara to send emails
  5. The authorization code is automatically captured
  6. Complete the remaining node configuration

Managing OAuth Connection​

  • Link Account: Connect a new Google account
  • Unlink Account: Remove the connected account

Outlook/Hotmail Configuration​

Connecting with Hotmail SMTP is straightforward.

Setup Steps​

  1. Enter your Hotmail email address in the Username field
  2. Enter your Hotmail password in the Password field

Outlook SMTP Settings​

SettingValue
Hostsmtp.office365.com
Port587
Username[email protected]
EncryptionTLS

Yahoo Configuration​

There are two methods to use Yahoo SMTP with Mumara Campaigns:

  1. Go to Yahoo Account Security
  2. Generate an App Password
  3. Use the generated password in the SMTP Password field

Method 2: Using Less Secure Apps​

  1. Enable "Allow apps that use less secure sign-in" in Yahoo settings
  2. Use your regular Yahoo password

Yahoo SMTP Settings​

SettingValue
Hostsmtp.mail.yahoo.com
Port587 (TLS) or 465 (SSL)
Username[email protected]
EncryptionTLS or SSL

AOL Configuration​

Similar to Yahoo, AOL supports two authentication methods:

  1. Go to AOL Account Security
  2. Generate an App Password
  3. Use the generated password in the SMTP Password field

Method 2: Using Less Secure Apps​

  1. Enable less secure app access in AOL settings
  2. Use your regular AOL password

AOL SMTP Settings​

SettingValue
Hostsmtp.aol.com
Port587 (TLS) or 465 (SSL)
Username[email protected]
EncryptionTLS or SSL

Amazon SES Configuration​

Connect your Amazon SES account for high-volume, cost-effective sending.

API Credentials​

FieldDescription
Access Key IDYour AWS access key ID
Secret Access KeyYour AWS secret access key
RegionAWS region for SES (e.g., us-east-1)

Getting AWS Credentials​

  1. Log in to AWS Console
  2. Navigate to IAM → Users
  3. Create a new user or select existing
  4. Attach the AmazonSESFullAccess policy
  5. Generate Access Keys
  6. Copy the Access Key ID and Secret Access Key

Available Regions​

  • US East (N. Virginia) - us-east-1
  • US East (Ohio) - us-east-2
  • US West (N. California) - us-west-1
  • US West (Oregon) - us-west-2
  • EU (Ireland) - eu-west-1
  • EU (London) - eu-west-2
  • EU (Frankfurt) - eu-central-1
  • Asia Pacific (Mumbai) - ap-south-1
  • Asia Pacific (Singapore) - ap-southeast-1
  • Asia Pacific (Sydney) - ap-southeast-2
  • Asia Pacific (Tokyo) - ap-northeast-1
  • Canada (Central) - ca-central-1
  • South America (São Paulo) - sa-east-1

SNS Webhook Configuration​

To process delivery reports, configure Amazon Simple Notification Service (SNS):

Step 1: Create SNS Topic

  1. Go to AWS SNS Console
  2. Create a new topic
  3. Note the Topic ARN

Step 2: Subscribe Mumara Webhook

  1. Create a new subscription
  2. Protocol: HTTPS
  3. Endpoint: Your Mumara webhook URL (shown in the node settings)
  4. Confirm the subscription

Step 3: Configure SES Notifications

  1. Go to SES Console → Verified Identities
  2. Select your domain
  3. Configure Notifications for Bounces, Complaints, and Deliveries
  4. Select your SNS topic

Step 4: Enable in Mumara

  1. Toggle Process Delivery Reports in the node settings
  2. Save the node

SendGrid Configuration​

Connect your SendGrid account for reliable email delivery.

API Key Setup​

  1. Log in to SendGrid
  2. Navigate to Settings → API Keys
  3. Click Create API Key
  4. Select Full Access or Restricted Access with Mail Send permissions
  5. Copy the API key (shown only once)
  6. Paste into Mumara's API Key field

Enable webhooks to receive delivery status notifications:

  1. Navigate to Settings → Mail Settings → Event Notification
  2. Enable Event Notification
  3. Enter your Mumara webhook URL
  4. Select events to track:
    • Delivered
    • Bounced
    • Spam Report
    • Unsubscribe
  5. Save settings
  6. Toggle Process Delivery Reports in Mumara

Mailgun Configuration​

Connect your Mailgun account for developer-friendly email delivery.

API Key Setup​

  1. Log in to Mailgun
  2. Click Settings → Security & Users → API Security
  3. Copy your Private API Key
  4. Paste into Mumara's API Key field
  5. Enter your Mailgun Domain

Webhook Configuration​

  1. Navigate to Sending → Webhooks
  2. Click Add Webhook
  3. Enter your Mumara webhook URL
  4. Select event types:
    • Delivered
    • Permanent Failure (bounces)
    • Temporary Failure
    • Complained (spam)
  5. Save the webhook
  6. Toggle Process Delivery Reports in Mumara

SparkPost Configuration​

Connect your SparkPost account for enterprise email delivery.

API Key Setup​

  1. Log in to SparkPost
  2. Navigate to Configuration → API Keys
  3. Create a new API key with appropriate permissions
  4. Copy the API key
  5. Paste into Mumara's API Key field
  6. Select your Region (US, EU, or Enterprise)

Webhook Configuration​

  1. Navigate to Configuration → Webhooks
  2. Create a new webhook
  3. Enter your Mumara webhook URL
  4. Select events to track
  5. Save the webhook
  6. Toggle Process Delivery Reports in Mumara

Elastic Email Configuration​

Connect your Elastic Email account for affordable high-volume sending.

API Key Setup​

  1. Log in to Elastic Email
  2. Navigate to Settings → API
  3. Click Create API Key
  4. Select Full Permissions
  5. Copy the API key
  6. Paste into Mumara's API Key field

Webhook Configuration​

  1. Navigate to Settings → Webhooks
  2. Create a new webhook
  3. Configure the webhook URL
  4. Select notification types
  5. Save the webhook
  6. Toggle Process Delivery Reports in Mumara

Mailjet Configuration​

Connect your Mailjet account for transactional and marketing email.

API Keys Setup​

  1. Log in to Mailjet
  2. Navigate to Account Settings → REST API → API Key Management
  3. Copy your API Public Key and API Secret Key
  4. Paste into Mumara's corresponding fields

Webhook Configuration​

  1. Navigate to Account Settings → Event Notifications (Webhooks)
  2. Add your Mumara webhook URL
  3. Select events to track
  4. Save the configuration
  5. Toggle Process Delivery Reports in Mumara

SMTP2GO Configuration​

Connect your SMTP2GO account for global email delivery.

API Key Setup​

  1. Log in to SMTP2GO
  2. Navigate to Settings → API Keys
  3. Click Add API Key
  4. Select appropriate permissions
  5. Copy the API key
  6. Paste into Mumara's API Key field

Webhook Configuration​

  1. Navigate to Settings → Webhooks
  2. Click Add Webhook
  3. Enter your Mumara webhook URL
  4. Configure event types and headers
  5. Save the webhook
  6. Toggle Process Delivery Reports in Mumara

Postmark Configuration​

Connect your Postmark account for transactional email delivery.

API Token Setup​

  1. Log in to Postmark
  2. Navigate to Servers → Select Your Server → API Tokens
  3. Copy the Server API Token
  4. Paste into Mumara's API Token field

Webhook Configuration​

  1. Navigate to Servers → Select Your Server → Webhooks
  2. Click Add Webhook
  3. Enter your Mumara webhook URL
  4. Select event types:
    • Delivery
    • Bounce
    • Spam Complaint
  5. Save the webhook
  6. Toggle Process Delivery Reports in Mumara

Sender Information​

Configure how the "From" address appears to recipients.

Sender Name​

The name that will appear as the sender in the recipient's mailbox.

Examples:

  • "John from Acme Corp"
  • "Acme Support Team"
  • "Newsletter Updates"

Sender Email​

The email address that will appear as the sender in the recipient's mailbox.

Configuration:

  • Enter the username portion
  • Select the domain from configured sending domains

Example: newsletter + @example.com = [email protected]

Reply-To Settings​

Configure where replies are delivered.

Enable Reply-To​

Toggle Different Reply-To Email to set a different reply address than the sender.

Reply-To Email​

The email address that receives replies.

Use cases:

  • Send from noreply@ but receive replies at support@
  • Direct replies to a specific team or person
  • Use a different domain for replies

Bounce Processing​

Configure how bounced emails are handled.

Enable Return Path​

Toggle Add Return-Path to set a bounce email address.

Return Path Email​

Select a configured bounce address to receive and process bounces.

tip

Configure bounce addresses in Setup → Bounce Addresses before enabling return path.

Tracking Settings​

Tracking Domain​

Select a tracking domain for rewriting links and embedding tracking pixels.

The tracking domain will appear in all hyperlinks, image URLs, and tracking pixels for outgoing emails.

How it works:

  1. Links in emails are rewritten to pass through the tracking domain
  2. When clicked, the click is recorded and the user is redirected
  3. Open tracking uses a transparent pixel hosted on the tracking domain

Delivery Settings​

Process Delivery Reports​

Enable to receive and process delivery status notifications.

When enabled, Mumara processes delivery reports for all recipients sent through this node, updating contact statuses based on bounces, deliveries, and complaints.

Additional Headers​

Add custom email headers which will be embedded to the email when this sending node is used.

Format:

  • Header names support only hyphens (-), no spaces or special characters
  • One header per line

Common custom headers:

  • X-Campaign-ID - Track campaign in logs
  • X-Customer-ID - Customer identification
  • X-Priority - Email priority level

Testing Nodes​

Validate Connection​

Before saving, click the Validate button to test the node connection:

  1. System attempts to authenticate with the server/API
  2. Success or error message is displayed
  3. Fix any issues before saving

Send Test Email​

After saving, send a test email through the node:

  1. Expand the Send a Test Email section
  2. Enter recipient email address
  3. Click Send Test
  4. Check recipient inbox for the test email
Test Before Production

Always send test emails before using a node for campaigns.

Managing Nodes​

Editing a Node​

  1. Click the Edit icon on a node
  2. Modify settings as needed
  3. Click Validate to test changes
  4. Click Save

Copying a Node​

Duplicate an existing node configuration:

  1. Click ... menu → Make a Copy
  2. A new node is created with "(Copy)" suffix
  3. Edit the copy with new settings
  4. Save the new node

Deleting a Node​

  1. Click ... menu → Delete
  2. If node is in use, select a replacement node for affected campaigns
  3. Confirm deletion
warning

Deleting a node used by active campaigns requires selecting a replacement.

Import/Export​

Export nodes:

  1. Select nodes using checkboxes
  2. Click Tools → Export sending nodes
  3. Download JSON configuration file

Import nodes:

  1. Click Tools → Import sending nodes
  2. Upload JSON configuration file
  3. Review and confirm import

Best Practices​

Security​

  • Use TLS/SSL encryption - Always use encrypted connections
  • Store credentials securely - Passwords are encrypted in the database
  • Limit API key permissions - Use minimal required permissions
  • Rotate credentials regularly - Update passwords and API keys periodically

Deliverability​

  • Warm up new nodes - Gradually increase sending volume
  • Monitor bounce rates - High bounces indicate problems
  • Use verified domains - Configure SPF, DKIM, DMARC
  • Set appropriate rate limits - Respect ESP sending limits

Organization​

  • Use descriptive names - Make nodes easy to identify
  • Group logically - Organize by purpose or environment
  • Document configurations - Note special settings or purposes
  • Test regularly - Verify nodes are functioning

Troubleshooting​

Connection Failed​

Possible causes:

  • Incorrect host or port
  • Wrong username/password
  • Firewall blocking connection
  • SSL/TLS misconfiguration

Solutions:

  • Verify server details with your provider
  • Check credentials are correct
  • Ensure firewall allows SMTP ports
  • Try different encryption settings

Authentication Error​

Possible causes:

  • Invalid credentials
  • Account suspended
  • Two-factor authentication blocking
  • API key revoked

Solutions:

  • Verify credentials in provider dashboard
  • Check account status
  • Generate app-specific password if using 2FA
  • Create new API key

Emails Not Sending​

Possible causes:

  • Node is inactive
  • Hourly limit reached
  • ESP rate limiting
  • Sender domain not verified

Solutions:

  • Check node status is active
  • Wait for hourly limit to reset or increase it
  • Contact ESP support
  • Verify sending domain configuration

Slow Sending​

Possible causes:

  • Low hourly limit
  • ESP throttling
  • Server performance issues
  • Network latency

Solutions:

  • Increase hourly limit
  • Add additional nodes
  • Check server resources
  • Consider different ESP

Next Steps​

Last updated on