Readymag / Vigbo / uKit: Russian Builders Email Deliverability

Russian-language audiences read mail on Mail.ru and Yandex more than on Gmail. That changes the deliverability picture for site builders targeting RU: the bar for SPF/DKIM on Mail.ru and Yandex is stricter than on Gmail, shared-pool reputation matters more, and Cyrillic subject lines interact with filtering in non-obvious ways.

Readymag, Vigbo (formerly Gophotoweb) and uKit are the three domestic builders most commonly used for portfolio sites, photo studios and small-business landings. Each ships form-notification email from its own infrastructure, and each has its own quirks.

Headline

On Mail.ru and Yandex, shared-pool mail from Russian builders is more likely to hit "Promotions" ("Рассылки") or Spam than Gmail equivalents. Seed test across Mail.ru, Yandex, Rambler, Gmail and Outlook — not just Gmail.

Readymag

Form notifications sent from Readymag's mail infra (readymag.com subdomain).
No DKIM signing on your domain; shared reputation pool.
Paid plans unlock webhook and Zapier integration.
Reply-To can be set to a submitter field.

Readymag's audience skews design and photography. Forms are usually low-volume contact or booking requests. The shared pool holds up OK on Gmail and Yandex, but Mail.ru placement is inconsistent week to week.

Vigbo

Specialises in photography and wedding-studio sites with built-in booking and gallery handoff.
Form + booking notifications from Vigbo's SMTP.
Paid plan offers "custom sender domain" for marketing email — but not for form notifications.

Booking confirmations to clients tend to land in Yandex Inbox reliably because the recipient often initiated contact. Team notifications to the studio owner are more variable.

uKit

Positioned for SMB landings — restaurant, service, shop.
Form notification email from uKit infra.
No custom DKIM for notifications on any tier.
Paid tier adds telephony and CRM export, not sender control.

Mail.ru quirk: list-unsubscribe on transactional

Mail.ru increasingly flags transactional mail that lacks List-Unsubscribe headers when coming from shared pools — the assumption is "if you're on a shared marketing pool, you're marketing". This affects Russian builders' form notifications in ways not visible in the product UI.

The RU seed test

Critical: test against the providers your audience actually uses, not just Gmail.

Seed addresses on Mail.ru, Yandex.ru, Rambler.ru, VK Mail, Gmail, Google Workspace, Outlook.com, and ProtonMail.
Submit the form three times with Cyrillic and Latin content mix (some providers handle transliteration specially).
Record placement: Inbox, Promotions, Spam, missing.
Open one on Mail.ru and Yandex and check the headers for Authentication-Results — look for SPF and DKIM pass/fail.

Webhook escape: RU-friendly ESP

If placement on Mail.ru and Yandex is poor, route the form via webhook (or Zapier-RU) to an ESP with good RU reputation. For RU audiences the usual winners:

UniSender. Russian ESP with established Mail.ru and Yandex relationships; transactional API is fast.
Sendsay. Strong on the CIS side, offers dedicated IP options.
Mailopost / Sender. Domestic options with web panels in Russian.
SendPulse. Hybrid — works globally but has local RU mirrors and RU customer support.

Form builder (Readymag/Vigbo/uKit)
  --> webhook or Zapier
  --> UniSender / Sendsay API
        from:     zakaz@yourdomain.ru  (DKIM on yourdomain.ru)
        to:       sales@yourdomain.ru
        reply-to: {{ submitter_email }}
        subject:  &#1053;&#1086;&#1074;&#1072;&#1103; &#1079;&#1072;&#1103;&#1074;&#1082;&#1072; &#1089; {{ page }}
  --> Mail.ru / Yandex Inbox

DNS setup that Mail.ru and Yandex accept

Russian providers are strict about DNS. Minimum viable config:

SPF:
  v=spf1 include:_spf.unisender.ru ~all

DKIM (selector provided by ESP):
  unisender._domainkey.yourdomain.ru  TXT  "p=MIGf..."

DMARC (start permissive):
  _dmarc.yourdomain.ru  TXT
    "v=DMARC1; p=none; rua=mailto:postmaster@yourdomain.ru; pct=100"

PTR (optional but helps on Mail.ru):
  reverse DNS on sending IP should match HELO domain

Mail.ru's postmaster tool (postmaster.mail.ru) gives you direct visibility into your reputation, complaint rate and placement — register your sending domain there. It is free.

Decide: stay, webhook, or migrate

Small photo studio, personal portfolio: stay on the builder's native notification. Re-test quarterly.
Active SMB with daily leads: move to webhook + RU ESP. A day of setup, permanent improvement.
Enterprise or regulated sector: consider migrating off the hosted builder entirely — Bitrix, Tilda Business, or custom on 1C-Bitrix give you full control.

FAQ

Why does my Readymag notification hit Gmail Inbox but Mail.ru Spam?

Gmail and Mail.ru weight signals differently. Mail.ru is more sensitive to shared-pool reputation and missing PTR. Gmail leans more heavily on engagement and content patterns. The same mail can easily split across providers.

Does Roskomnadzor compliance affect deliverability?

Not directly — RKN compliance is about data handling, not email authentication. But if your DNS is hosted outside RU and your audience is RU, RU providers may apply a small penalty to first-time unfamiliar infrastructure.

Is UniSender genuinely better than SendGrid for RU audiences?

For Mail.ru and Yandex placement specifically, yes. UniSender has direct postmaster relationships that SendGrid doesn't. For a purely global audience, SendGrid is equal or better.

Can I send from a .com domain to a .ru audience?

You can, but Mail.ru and Yandex sometimes apply a small penalty to .com senders targeting Cyrillic recipients, on the assumption that domestic businesses use domestic TLDs. For a RU-first business, a .ru or .рф domain is slightly friendlier.

Russian builders Readymag, Vigbo, uKit: email deliverability