Integrations & Code Verified for 2026 Expert Reviewed

Mumara Campaigns SMTP Server Configuration Guide

Direct Answer Quick Summary for Senders:

To configure Mumara Campaigns with an external SMTP server, navigate to Sending Nodes → Add New Node, choose SMTP as the transport agent, enter relay.171mails.com as the server host on port 587 with TLS encryption, input your credentials, configure your tracking domain with matching SSL, and set your hourly rate limit to match your 171mails tier.

Key Takeaways

Mumara's multi-node engine allows flexible distribution of campaigns across multiple SMTP relays.
Configure custom tracking domains with CNAME records to maintain 100% brand alignment.
Align Mumara node hourly limits with the 171mails 400-hour monthly pacing formula.
171mails provides 4 Dedicated IPs and automated suppression scrubbing for high-volume Mumara senders.

1. Adding a 171mails Sending Node in Mumara

In your Mumara administrative dashboard:

  1. Go to Sending Nodes → Add New Node.
  2. Set Node Type to Standard SMTP.
  3. Enter the server details:
    • SMTP Host: relay.171mails.com
    • SMTP Port: 587
    • Authentication: Yes
    • Encryption: TLS
    • Username / Password: Your 171mails credentials
  4. Under Rate Limiting, configure your hourly limit (e.g., 2,500/hr for 1M plan).
  5. Click Save & Test Connection.

2. Setting Up Tracking Domains & SSL

To preserve domain reputation in Mumara, set up a custom tracking domain (e.g. track.yourdomain.com) pointing via CNAME to relay.171mails.com. Ensure Let's Encrypt SSL is active so all click tracking links use HTTPS.

3. Leveraging 171mails 4-IP Rotation

Because 171mails handles IP rotation at the transport layer, a single Mumara node automatically distributes traffic across 4 Dedicated IPs (2 IPv4 + 2 IPv6), eliminating the need to configure multiple complex local nodes.

Frequently Asked Questions

Easily. Mumara is built for enterprise volume and pairs perfectly with 171mails' 2,500/hour paced delivery on 1M monthly packages.

Yes, Mumara has built-in webhook endpoints for bounces, unsubscribes, and spam complaints that integrate directly with 171mails.

Yes, Mumara's multi-tenant architecture allows you to assign specific sending nodes to distinct clients or sub-accounts.
Enterprise Bulk Email Relay

Scale Your Mumara Campaigns with Enterprise Multi-IP Relays

Maximize Mumara inbox placement with 4 Dedicated IPs, automated rate pacing, and 100M+ real-time suppression scrubbing.

  • Optimized for Mumara Campaigns, ONE, and ESP modules
  • 4 Dedicated IPs (2 IPv4 + 2 IPv6 dual-stack) up to 1M sends
  • 100M+ real-time suppression list scrubbing
  • Test your Mumara node with our $5 (₹399) sandbox
100K Email Plan
$29 /mo
4 Dedicated IPs Included

Related Questions & Guides

Platform, CRM & Stack Integrations
Best SMTP Relay for Mailwizz Self-Hosted (Setup Guide)

Connect Mailwizz EMA to the best high-volume SMTP relay. Learn delivery server settings, bounce handling we...

Platform, CRM & Stack Integrations
How to Connect Sendy to a Dedicated SMTP Server (Beyond SES)

Learn how to connect Sendy to a dedicated SMTP server instead of Amazon SES. Avoid strict SES account suspe...

Volume, Scaling & Rate Limits
How to Send 1 Million Emails a Month (Enterprise Roadmap)

Discover how to send 1,000,000 emails monthly without spam issues. Multi-IP architecture, 400-hour pacing, ...

Deliverability, Warmup & Reputation
What is SMTP IP Rotation and How Does It Work? (2026 Guide)

Understand SMTP IP rotation architecture. Learn round-robin vs volume-weighted routing, dual-stack IPv4/IPv...