If your list is in Russia, Kazakhstan, Belarus or Ukraine, odds are you send through UniSender or SendPulse. Both are solid platforms with deep CIS integrations — but both have the same blind spot as every other ESP: their dashboards report acceptance, not inbox placement. For CIS senders that gap is even worse, because the Western placement-testing tools (GlockApps, Litmus, Mailgun) do not cover Mail.ru and Yandex in any meaningful way. Our free tool does.
Test Mail.ru, Yandex, Rambler, Outlook and Gmail before every send. UniSender and SendPulse report "доставлено", which means the MTA accepted the mail — not that it landed in the Inbox (Входящие). Real placement on shared CIS pools is often 25–40 points below the dashboard number.
Why CIS senders need a CIS-aware test
Mail.ru and Yandex together hold 60%+ of consumer email share in Russia, with Rambler still relevant for older demographics. Each uses its own spam filter, its own reputation system, and its own postmaster tooling. Crucially:
- Postmaster.mail.ru tracks domain reputation but exposes it with a 48–72 hour lag, not real-time.
- Postoffice.yandex.ru shows bulk-sender statistics but requires verified ownership and only goes granular for senders above ~10k daily volume.
- Western tools either skip CIS providers entirely or simulate them with a single seed mailbox, which provides almost no signal.
If you send to a CIS list and only test via GlockApps' Western seed pool, you are measuring the wrong thing. Inbox at Gmail tells you nothing about placement at Mail.ru.
UniSender shared pool dynamics
UniSender runs shared IP pools segmented by account tier and sending history. Observed behaviour:
- Mail.ru placement is generally strong — UniSender has long-established reputation with Mail.ru. Expect 70–85% Inbox for clean lists.
- Yandex placement is more variable. Yandex's spam filter weighs content and subject-line signals heavily, and shared-pool contamination hits Yandex placement first.
- Gmail placement for UniSender is mixed. Non-CIS Gmail users often see Promotions; Russian-language Gmail users receive more variable placement due to language-model signals.
- Outlook is the weakest — UniSender IPs are flagged as high-volume commercial in Microsoft's reputation system, and Junk placement is common.
UniSender offers a dedicated-IP option on enterprise plans and a white-label SMTP service for developers. Both help if you're at scale.
SendPulse shared pool dynamics
SendPulse operates multi-region infrastructure (CIS, EU, US) and routes traffic based on sender geography. For CIS senders:
- Mail.ru placement is solid, comparable to UniSender. Expect similar 70–85% Inbox ranges on clean lists.
- Yandex placement tends to be slightly weaker than UniSender based on our observations, especially on new accounts.
- Gmail placement at SendPulse benefits from their EU infrastructure — often better than UniSender for mixed-language lists.
- Outlook is the same weak point as every shared-pool ESP.
SendPulse additionally offers SMS, web push and transactional pipelines. As with Brevo, the shared IPs are segmented logically but share the same reputation substrate.
How postmaster.mail.ru and postoffice.yandex.ru compare
postmaster.mail.ru
Shows domain reputation, authentication pass rates, complaint rates and placement breakdown by folder. Strong on authentication diagnostics (SPF, DKIM, DMARC per-send reporting). Weak on real-time feedback — placement data lags 2–3 days.
postoffice.yandex.ru
Similar metrics, plus a useful "mass-mailer score" that summarises sender health. Requires domain verification and minimum daily volume thresholds for full detail. Yandex's FBL (feedback loop) is essential here — register it or you lose visibility into complaints.
Both are worth registering, but neither gives you the per-provider, per-send feedback a seed-list placement test provides. They complement each other; they don't replace each other.
Running a free test across CIS providers
Pre-send routine for UniSender and SendPulse:
- Open the free placement-test tool and copy the seed-mailbox addresses — it includes Mail.ru, Yandex, Rambler, Gmail, Outlook, Yahoo, GMX, ProtonMail, Fastmail and more.
- Add the seed addresses as a separate segment or contact group in UniSender / SendPulse.
- Send the exact campaign content — same HTML, same subject, same From address — to that segment only.
- Wait 2–3 minutes and read the per-provider breakdown.
- Check Mail.ru and Yandex first: Inbox vs "Рассылки" (Promotions-style) vs "Спам". If Спам > 10% on either, stop and fix before the real send.
Typical causes of Mail.ru spam placement
- Missing or misaligned DMARC — Mail.ru enforces DMARC strictly. A passing
p=noneis not enough for bulk senders;p=quarantinewith domain alignment is expected. - Cyrillic sender-name alignment failure — From names in Cyrillic must be properly encoded (MIME-Q or MIME-B). UniSender and SendPulse handle this, but custom SMTP integrations often break alignment.
- Subject-line keywords — Mail.ru's filter is Bayesian-heavy and reacts to shouty language and money-oriented keywords more aggressively than Gmail.
- Tracking-domain reputation — the shared UniSender / SendPulse tracking domains are sometimes on SURBL. A custom tracking domain is a high-ROI fix.
- List quality — Mail.ru has abundant spam traps (recycled abandoned accounts). A single spam-trap hit hurts for weeks.
DMARC alignment under Cyrillic sender names
The From header in a Cyrillic-language campaign typically looks like:
From: =?utf-8?B?0JDQvdC90LAg0LjQtyDQkdGA0LXQvdC00LA=?= <anna@brand.ru>
For DMARC alignment, what matters is the brand.ru part — the encoded display name is irrelevant. Check:
- The
d=in your DKIM signature matchesbrand.ru(relaxed alignment) or subdomains of it (strict). - The
return-pathSPF domain also aligns withbrand.ru. UniSender and SendPulse use their own return-path by default, so SPF alignment often fails. Set up a custom return-path if their plan allows it. - DMARC policy at
_dmarc.brand.ruis at leastp=quarantine.
A custom sending domain with proper DMARC alignment reaches good Mail.ru reputation in 2–3 weeks of modest-volume sending — notably faster than Gmail, where 4–6 weeks is typical. The ROI on domain setup is higher for CIS-targeting senders.
GlockApps coverage gap
GlockApps covers Gmail, Outlook, Yahoo, AOL, iCloud, Fastmail, ProtonMail and a handful of regional providers. Mail.ru and Yandex are either absent or represented by one seed mailbox that gives no statistical signal. For a CIS sender, that is a near-total blind spot.
Our free tool was built specifically to cover this gap. Multiple Mail.ru seed inboxes across different account ages, multiple Yandex seeds, plus Rambler — alongside the full Western set. Unlimited tests, no signup, all 20+ providers on every run.