Search results

That’s a very common mistake. If you use Evergreen incorrectly: Old subscribers may get the email late New subscribers may get an outdated promo Campaign keeps firing when you didn’t expect it I’ve seen people send a Black Friday email in January because of this. So Evergreen needs clear rules...

This is how most long-term Mumara users lock it down: Create a master “Send-Ready” segment Example conditions: Subscription status = Subscribed Not in suppression list Email status = Active Use only this segment for campaigns never raw lists. Avoid selecting lists directly in campaigns...

Ofcourse not, don’t send anything else to them. Once someone is unsubscribed, any follow-up email (even an apology) is considered a violation. Best practice in Mumara is: Leave it as a one-time mistake Fix your targeting rules Monitor complaint rate for the next 24–48 hours

Sure, here’s how it works in real usage. Scheduled Campaigns are best for: Weekly newsletters Product launches Flash sales Announcements with a deadline You pick the audience, the exact date & time. And the campaign sends once. Evergreen campaigns are for ongoing, automated sending. Typical...

That’s okay still not a big problem Here’s what matters now: Do NOT resend immediately Sending a correction email too fast often: Confuses recipients Increases spam complaints Wait a bit and evaluate engagement first because sending email to them again might trigger something bad which may...

Yes a few smart steps Stop future sends (if any) If the campaign is: Scheduled → Pause or cancel it immediately Ongoing → Stop the campaign so it doesn’t hit more contacts Mumara stops delivery instantly once you pause it.

Yes, that explains it. In Mumara, new lists don’t automatically exclude unsubscribed users unless you schedule your campaign to an old list on which you have already sent a campaign. Here’s what you should do next (step-by-step): Review campaign stats Go to Statistics → Broadcast Stats and...

Quick Yahoo-ready checklist for Mumara users: SPF + DKIM passing DMARC published Clean, opt-in lists only Gradual volume increases Consistent sending schedule Clear unsubscribe + footer info Monitor bounces and complaints Do this, and Yahoo usually behaves nicely and this will surely start...

Don’t panic this is a common slip, especially when sending to a raw list or a newly imported one. However, if you are sending to an old list on which you have already scheduled some campaign Mumara will automatically exclude unsubscribed users. Important thing first is If the campaign is still...

Good question this is something a lot of people get wrong at first. The easiest way to think about it is: Scheduled campaigns → send once at a specific time Evergreen campaigns → send automatically based on rules They’re built for very different goals, even though the emails may look similar...

Ofcourse its a huge deal. Even a small complaint rate can hurt: IP reputation Domain reputation Inbox placement That’s why list hygiene and suppression handling in Mumara are critical, and Mumara is providing you with a robust mechanism to handle suppression across domains and IPs.

Exactly. The quick takeaway from this is: Duplicate sends usually come from panic clicks Mumara does what it’s told Logs + patience prevent 90% of these mistakes Once you build a habit of checking status before resending, this almost never happens again. Its just a matter of thinking of what...

You’re not alone this happens to more people than you think. Its just a matter of the operation a user is doing in Mumara while sending a campaign. First thing to clear up. This isn’t a Mumara bug. Mumara sent exactly what it was instructed to send. The real question is how to limit the damage...

Sadly, once emails are sent they’re gone and will reach their destination until everything is working in a good state. What you can do: Pause the campaign immediately if it’s still sending Send a short follow-up apology if needed Learn from it and tighten your process Most users forgive one...

Yahoo dislikes surprises. You need to avoid: Sudden volume spikes Long sending gaps followed by blasts Sending cold or inactive contacts Best approach in Mumara: Warm up gradually Send consistently Start with engaged segments Predictability can eventually build trust on the major ISPs.

Great question and this is where people usually mess up. If you want to resend intentionally: Create a new campaign Target only: Non-openers Or a fresh segment Never resend blindly to the same full list. This way you will: You avoid duplicate emails You protect engagement Subscribers don’t...

Content still matters a lot. Yahoo looks for: Clear unsubscribe links No misleading subject lines Consistent sender identity No sudden template changes during warm-up Mumara handles unsubscribe compliance automatically but content discipline is on the sender. However, you can manage the...

Here are practical prevention steps that actually work: Always check Campaign Logs If status is Processing or Sending, don’t resend Large lists take time this is normal behavior also depends on your server resources Use “Exclude Previously Sent Contacts” Especially when cloning or retrying...

Strongly recommended. Yahoo expects: A valid DMARC policy At least p=none to start Gradual move to quarantine or reject once stable DMARC helps Yahoo trust that emails are really coming from you. So get your DMARC set before you start sending emails to yahoo.

Yes quite easily. Here’s what typically happens: Inactive users don’t open Engagement drops Inbox providers lose trust Emails start going to Spam or Promotions SPF/DKIM still pass, but reputation drops quietly in the background. That’s why everything looks correct technically, but results...