Search results

Clean data helps a lot, just in a different way. With opt-in subscribers: Opens happen naturally Clicks come in early Spam complaints stay low This sends positive engagement signals, which helps your warm-up complete faster and more smoothly. In Mumara, that usually means: Fewer throttles...

Start with delivery, not the email content. Check these in Mumara for the affected campaign: Are emails still marked as Delivered? Did sending take longer than usual? Any throttling visible in logs (especially Gmail)? When open rates drop that hard, emails are often landing in Spam or...

Daily sending helps, but how you send matters more than frequency. Mailbox providers look at: Consistent volume Low bounce and complaint rates Positive engagement (opens, clicks, replies) If those signals stay healthy, the reputation improves naturally.

Exactly. Mailbox providers (Gmail, Outlook, Yahoo, etc.) don’t know your list quality on day one. What they do see is: A new IP or domain Suddenly sending a large volume No prior sending history That’s where warming comes in. Mumara follows standard SMTP and ISP spam-compliant rules it won’t...

Great question and honestly, this comes up a lot. For your information. Yes, warming is still required, even if your data is perfectly clean. Clean opt-in data is huge, but warming isn’t really about the data it’s about sender reputation.

Good question and yes, this is completely normal. There’s no fixed time limit for an IP to move from Neutral to Good. It depends almost entirely on how you send, not how long the IP exists.

I get why this is confusing you, but don’t worry, this usually has a clear reason. First thing to know: Mumara doesn’t randomly drop open rates. A drop from 22% → 6% usually means delivery behavior changed, not tracking. Let’s go through the most common real causes I see.

Surely, it can, but let me reproduce the case on one of our test installations. I'll get back to you on this shortly.

Here are some best practices that work really well with Mumara Keep your email HTML lean Avoid overly complex layouts Reuse CSS classes instead of repeating inline styles Optimize images Compress images before uploading Don’t rely on dozens of small image blocks Avoid copy-paste from Word /...

Here are some simple rules: Use test emails only for preview & QA Check deliverability using real campaigns Send tests to multiple inboxes (Gmail, Outlook, Yahoo) Open or click test emails occasionally Ensure SPF, DKIM, and tracking domains are properly set If production emails are landing...

Mumara doesn’t force a specific name this part is always flexible. Common and safe options: mail.example.com m.example.com news.example.com notify.example.com What matters is: The subdomain is dedicated to email SPF, DKIM, DMARC and other authentications are set on that subdomain Once...

I guess thats what you were asking am happy your confusion has been cleared. Mumara sends clean, standards-compliant HTML, but Gmail decides how it renders it. In fact, Mumara does a few things right that help avoid clipping if used properly: It doesn’t inject unnecessary wrappers...

Test emails are only good for design, personalization, and to check the working not deliverability judgment. Test sends don’t fully reflect: Throttling behavior Volume ramp-up Natural sending patterns Mailbox providers trust consistent campaign traffic more than isolated tests.

Here’s the real risk, based on what I’ve seen usually. However, you can manage this in Mumara setups: Your domain reputation is shared across: Website Emails Anything tied to that domain If you send campaigns directly from example.com and later: You get spam complaints Engagement drops A bad...

Hey, Thats a very good question. However, this is NOT a Mumara issue It’s actually a Gmail behavior, and it happens across all email platforms. Let me break it down in simple terms. Gmail automatically clips emails when the HTML size exceeds ~102KB. Once that limit is crossed, Gmail hides part...

Yep this is actually very common, and in most cases it’s not a Mumara bug at all. Test emails don’t behave like real campaigns. When you send a test email, you’re usually sending it to: Your own inbox A brand-new or isolated address An address with no prior engagement history Mailbox...

Yes you need a subdomain and you’re right to ask this before sending anything. And you should use a subdomain for email sending. Technically, you can send from your main domain, but it’s risky long-term.

Exactly. SMTP is best for: Password resets OTP emails Order confirmations Account notifications These emails need to go instantly when an action happens. Your app decides when to send Mumara just delivers it. However, if you schedule a campaign for this purpose its not designed for instant...

That’s a very common question. Think of it this way: SMTP or its API is for real-time, one-to-one emails Campaigns are for bulk, one-to-many emails SMTP/API is usually triggered by your application (like login, signup, orders). Campaigns are manually or scheduled sends to a list. They’re...

My recommendation for you. Since you’re doing both: Separate domains now Don’t mix transactional + marketing on the same domain long-term Sending both from the same domain works. However, it’s not the safest setup If you’re planning to scale, separate subdomains now. It’s a small setup change...