Outside CIS, Mail.ru is usually an afterthought in a sender's deliverability setup. Inside CIS, it's the default personal mailbox for roughly half the population. If any part of your target market is Russian, Belarusian or Kazakh consumer, Mail.ru is where you need to land in the Inbox — and the rules are meaningfully different from Gmail or Outlook. Here's the full picture.
Mail.ru hard-fails on SPF misalignment. DKIM selectors have strict format rules that most Western ESPs get wrong out of the box. postmaster.mail.ru is the best CIS-sender portal there is — set it up on day one. Cyrillic subject-line encoding breaks more campaigns than any other single issue.
How big Mail.ru actually is
When people say "Mail.ru," they usually mean four related mailbox domains on the same infrastructure:
- @mail.ru — the flagship domain. Largest slice of the user base.
- @list.ru — heritage domain, still tens of millions of active users.
- @inbox.ru — aliased to the same platform, same filter.
- @bk.ru — ditto.
All four share filtering, reputation, and the postmaster portal. Total active mailboxes across them: 50+ million as of 2026. Second place in CIS is Yandex; third is a long tail of corporate M365 and legacy Rambler.
The Mail.ru filter stack
Mail.ru's filter runs in roughly this order:
- SMTP-time checks — SPF, rDNS/PTR, banner, HELO match. Misalignment here results in 550 at SMTP, not quarantine.
- DKIM verification — strict selector parse; missing or malformed DKIM is a hard Junk signal.
- DMARC policy — honoured literally;
p=rejectmeans reject. - DNSBL lookups — Spamhaus, SORBS, plus Mail.ru's own internal blocklist.
- Content classifier — in-house ML with weights toward Cyrillic linguistic features, image/text ratio, link reputation.
- Engagement model — per-recipient history, opens and complaints over a rolling window.
The order matters. A content problem won't even get reached if SPF alignment fails. Start authentication-first.
postmaster.mail.ru: setup walkthrough
Registering your domain
- Go to
postmaster.mail.ruand sign in with any Mail.ru account (create one if you don't have one). - Add your sending domain and verify via DNS TXT record — Mail.ru gives you the exact string.
- Enable FBL (complaint feedback loop) from the Settings tab. You provide an email address; Mail.ru forwards ARF-format complaints there for every "Spam" click by a recipient.
- Enable daily digest for delivery errors and reputation changes.
Dashboards
The portal shows: delivery rate, error breakdown by SMTP code, Junk rate (measured server-side, distinct from user complaints), per-domain reputation trend over 30/90 days, and a per-IP breakdown if you use multiple. The UI is Russian-language only — a browser translator works fine.
SPF strictness: hard-fail on misalignment
Mail.ru's SPF check differs from Gmail's in two ways:
- Softfail is treated as hard-fail for alignment purposes. If your record ends with
~alland your actual sending IP isn't in the record, Mail.ru will Junk you even though technically the SPF evaluator returned softfail. - Return-Path domain must match From domain. If your ESP sets Return-Path to its own bounce subdomain, Mail.ru rejects DMARC alignment. This is the single most common misconfiguration we see on Western ESP setups.
Fix: publish SPF at the root of your From domain, include every sending service explicitly, end with -all, and set up custom Return-Path at your ESP so the bounce domain aligns.
DKIM selector rules
Mail.ru's DKIM parser is stricter than Gmail's. Observed failure modes:
- Selector names with underscores prefixed (
_default) or starting with a digit fail to parse on Mail.ru while passing on Gmail. - TXT records split across multiple quoted strings must concatenate to a valid DKIM record. Mail.ru handles this correctly only when quotes are well-formed; many CloudFlare defaults produce records that Gmail accepts and Mail.ru rejects.
- RSA keys below 1024 bits are silently rejected. 2048-bit is the Mail.ru recommendation.
DMARC handling
DMARC is honoured literally. p=reject gets rejected. p=quarantine goes to Spam folder. p=none falls through to the engagement-and-content filter. Aggregate reports (rua) are sent daily at 00:00 UTC — some of the most reliably formatted DMARC reports in the industry.
Why Gmail tests tell you nothing about Mail.ru
Passing a Gmail placement test does not predict Mail.ru placement. The content model is trained on Russian-language corpus; the DKIM parser is stricter; the SPF alignment rule is tighter; and engagement signals are measured against Russian-speaking recipients who complain at roughly twice the rate of Gmail users on cold mail. You need to seed Mail.ru directly.
GlockApps covers Mail.ru on the top tier ($79+/mo) but its CIS seed pool is small and screenshots are cropped. Other paid tools either skip the region entirely or bundle Mail.ru with "international providers" without a meaningful per-provider verdict. A free test with real Mail.ru / Yandex / Rambler seeds and real screenshots is the gap this space has had for years.
Common sender mistakes
Cyrillic subject encoding
Subject lines with Cyrillic must be MIME-encoded correctly, for example:
Subject: =?UTF-8?B?0J/RgNC40LLQtdGCLCDQvNC40YA=?=A plain UTF-8 subject without encoding often passes Gmail (which is permissive) and triggers Junk on Mail.ru (which is strict). Most ESPs handle this correctly; custom sending scripts frequently don't.
Image-only HTML
Mail.ru's content filter weights image-to-text ratio more than Gmail's. An email that is one big image with a two-line caption gets flagged immediately. Target 60/40 text-to-image or better.
No plain-text alternative
Send both parts of multipart/alternative. Mail.ru does actually parse the plain-text part and uses it in content classification.
Free Mail.ru placement test
The inbox-check tool seeds @mail.ru, @list.ru, @inbox.ru and @bk.ru in every test — no separate setup, no add-on, no paywall. You get per-address folder placement (Inbox / Spam / missing), authentication results, SpamAssassin and Rspamd scores, and real screenshots of the Mail.ru webmail UI so you can see what a Russian recipient actually sees.