Search results

Dear Cleber, Thank you for your detailed analysis and for sharing comprehensive technical evidence. We truly appreciate the effort you’ve put into diagnosing the issue. We would like to inform you that this behavior has already been identified and addressed in our upcoming major update. The...

We use Global Headers heavily for multi-client setups. Instead of spinning multiple instances, we inject: Then our logging system categorizes performance automatically. Saves hours every week.

Recovery plan (based on real large Mumara accounts): Step 1: Reduce daily volume by 30–40% Step 2: Send ONLY to 30-day engaged users for 7–10 days Step 3: Monitor open + click rebound Step 4: Gradually reintroduce older segments Think of it as re-warming your domain reputation. Never panic on...

That’s good btw but go one level deeper. In Mumara Campaigns, do this: Separate lists per brand Separate segments per engagement level Never cross-send between brands Example mistake I’ve seen: Someone imported Brand A contacts into Brand B list “for testing”. Result: Low engagement Spam...

To add more clarfication on this. We actually use this for internal analytics. Example of what appears in the raw email header When someone reports a delivery issue, we can instantly trace: Which campaign Which segment Which contact Which sending pool Without digging manually through dashboards.

Hey Yamada, First of all, with 32 Cores + 64GB RAM + NVMe, Mumara is absolutely capable of preparing 500k+ campaigns in minutes. In almost all similar cases, the delay is caused by default database and PHP configurations, not by Mumara’s core engine. Below are the exact optimizations we...

This is a classic large-sender scenario and it happens more often than people realize. When you’re sending 1M/day, even a small shift in metrics can trigger mailbox algorithms. Let’s break it down based on real Mumara high-volume cases Engagement Decay (Most Common Reason) When volume grows...

Yes Ofcourse, Mumara can handle traffic spikes but only if you prepare properly. The platform itself is scalable, but mailbox providers (Gmail, Yahoo, Outlook) don’t like sudden unpredictable volume jumps. The real question isn’t “Can Mumara handle it?” However, If I rephrase this.... It’s...

Well this is a great question but this is very common once people scale beyond one project. Yes, you can manage multiple brands under one Mumara account but structure is everything. I can break it down based on real Mumara Campaigns and MumaraONE setups I’ve seen work successfully. Let me know...

Oh yes and honestly, not enough people use this feature. Global Headers in Mumara Campaigns are extremely useful if you want: Advanced tracking at SMTP level External log correlation (PowerMTA / Postfix / custom MTA) Webhook-based analytics Internal BI mapping They basically allow you to...

Hey Yamada, I will get back to you on this shortly with the required information you need to fix your issue. Thankyou

Yes, don’t just think IP. Think ecosystem: ✔ Dedicated IPs ✔ Proper DNS authentication ✔ Segments (engaged first) ✔ Bounce & complaint monitoring daily ✔ Gradual ramp-up Sending 1M/day is not about power It’s about discipline.

For anyone scaling with MumaraONE: Multiple domains are powerful but only when paired with proper segmentation and clean sending practices.

Yes, In proper setups: Unsubscribing stops promotional emails It does NOT stop critical transactional emails That’s actually why transactional emails shouldn’t include unsubscribe links because they are service-related and required. Example 3 -> Clean Transactional Confirmation Subject: Order...

Exactly, below are the summarized things MumaraONE supports multiple sending domains Domain reputation is separate IP reputation depends on configuration Structure + segmentation matter more than domain count Agencies successfully manage multiple brands from one dashboard just don’t mix risky...

Yes, but only in specific cases: ✔ Extremely clean opt-in database ✔ High engagement rate ✔ Controlled shared pool (quality-managed by provider) But even then, once you consistently hit 1M/day, serious senders move to dedicated. Mumara supports both models but scaling brands usually choose...

Yes, in these cases: Completely unrelated clients with different billing/ownership Very high-volume senders needing dedicated infrastructure Clients who require full isolation for compliance Otherwise, one account with properly separated domains works perfectly.

Exactly, mailbox providers and regulations care about intent and content, not just the fact that it was triggered. In Mumara: Transactional emails are typically sent via system/API flows Promotional emails are sent via campaigns Promotional emails must respect unsubscribe preferences

Immediate action plan: Stop sending to inactive contacts Suppress recent non-openers Segment only last 30–60 day engaged users Reduce volume temporarily Monitor next 2–3 campaigns closely Recovery usually starts within 1–2 weeks if you clean up fast.

True but think long-term ROI. If shared IP causes: 5% inbox drop 0.1% complaint spike Domain reputation damage That’s way more expensive than IP cost. At 1M/day, even a 3% inbox improvement means: -30,000 more emails landing in inbox daily -That’s serious revenue difference.