Search results

Yes and that’s actually very common. A healthy structure would look like this: Ecommerce → shop.brand.com SaaS transactional → notify.brand.com Events → events.brand.com Each domain has its own Separate sending identity Separate DKIM/SPF records Separate segments Many agencies manage 5–10...

Yes ofcourse. Here is a recent case: A sender pushed a re-engagement campaign to old inactive contacts. Complaint rate jumped to 0.18%. Results within 10 days: Open rate dropped from 24% → 11% Gmail inbox placement decreased significantly Yahoo traffic slowed down It took 3–4 weeks of clean...

That’s where people get into trouble. The moment you add marketing intent, it’s no longer purely transactional. Example 2 ->Mixed Email (Now Needs Unsubscribe) Subject: Your invoice is ready That second paragraph turns it into promotional content. -In this case, it should be treated as a...

In real Mumara scaling scenarios, here’s a typical structure: - 1M/day → Minimum 4–6 dedicated IPs - Proper IP warm-up schedule (20–30 days) - Domain alignment (SPF, DKIM, DMARC configured correctly) - Segmented sending (not blasting entire list at once) Here is an example instead of: ❌...

Here’s a real MumaraONE scenario let’s just say: All domains are using the same shared IP pool One brand sends to inactive or risky data Spam complaints spike Even though domain reputation is separate, the IP reputation can temporarily affect everyone. That’s why agencies usually: Keep...

Several things can happen, including the following and if this eventually keeps on increasing their will be a risk of account suspension. Inbox placement drops gradually Gmail may start routing emails to Promotions or Spam Yahoo may throttle volume IP reputation may shift from “Good” to...

Well, that is quite thoughtful you have asked and this is where many users misunderstand scaling. On shared IP: Your reputation = influenced by others Their spam complaints = affect you Their bad data = affects inboxing Now imagine sending 1M/day and someone else in the pool suddenly blasts...

Because mailbox providers (Gmail, Yahoo, Outlook) measure user dissatisfaction, not percentages the way we do. For example: If you send 50,000 emails, 0.1% = 50 people clicking “This is spam.” From their perspective, that’s 50 negative trust signals in one campaign. That’s enough to trigger...

Thats will be a good heads up and this is where many people misunderstand things. In MumaraONE: Domain reputation is tied to each sending domain IP reputation depends on whether you're using shared or dedicated IPs Campaign behavior matters more than account count Example If you have...

In Mumara, transactional emails are: Triggered by a user action Necessary for account/service functionality Not marketing-driven Expected by the recipient For example: Example 1 -> Proper Transactional Email (No Unsubscribe Needed) Subject: Your password reset request ✔Triggered by user ✔No...

If you're seriously sending 1M/day, this isn’t even a debate. Dedicated IP is the correct setup. Shared IPs are fine for: Small senders New accounts Low volume (under 100k/day) Testing campaigns But once you cross 300k–500k daily volume, shared becomes risky.

Good question this is very common for agencies and multi-brand setups. MumaraONE allows multiple sending domains in one account. However, it depends on which account you have subscribed to. Have you checked the pricing page here please also click on the view limits button on the bottom right...

Yes, even though 0.1% may look small, but in email deliverability, it’s a major signal. To put it simply: 0.1% = 1 complaint per 1,000 emails Mailbox providers consider this the early warning line If complaints cross that consistently, the reputation starts weakening.

That's quite a great question and this confusion is very common. However, the answer to your query is, No, purely transactional emails do NOT require an unsubscribe link. But there’s an important condition: The email must be strictly transactional.

Yes honestly and clearly. I summarized my statement like below Purchased data = high risk “Opted in elsewhere” ≠ permission for you One bad list can hurt months of good sending If you care about: Account safety Inbox placement Long-term growth Stick to first-party opt-ins only.

That can be okay if: You have a direct relationship with them They expect to hear from you Emails are relevant to that relationship Best practice is Segment them separately Start with a low-volume re-introduction campaign Let inactive users naturally drop off Even then, still caution matters...

Frame it like this: Clients usually understand when you talk about long-term cost vs short-term gain.

Exactly, If you remember just one line: Once you switch to a segment-first workflow, mistakes drop massively and deliverability stays clean.

Best practice in MumaraONE are as follows: Keep transactional emails clean No banners No promotions No “Upgrade now” link Separate marketing from system emails Transactional → critical user actions Promotional → campaigns, announcements, upsells When in doubt, classify as promotional It’s...

You may think about it but that’s often the smartest move. Many MumaraONE users: Clearly document acceptable use Offer opt-in alternatives (lead magnets, forms) Decline cold lists politely but firmly Protecting long-term deliverability is more valuable than one campaign.