Bitrix24 Email Deliverability: Test Your CRM Emails (CIS Market)

Bitrix24 — the cloud SaaS sibling of the 1C-Bitrix CMS — is the de facto CRM and collaboration platform for a large share of small-to-mid businesses in Russia, Belarus, Kazakhstan, Ukraine, and adjacent markets. Its pricing and feature set have made it the obvious choice for sales teams of 5 to 500, and it is rapidly expanding into Western Europe and Latin America as well.

One area where Bitrix24 confuses new users is email. There is no single "send" button — outbound mail can flow through four different mechanisms depending on how you configure the product, and each one has its own deliverability profile. Running a sales motion on assumptions about which mechanism is active is the shortest path to a pipeline full of "the client never received our proposal" explanations.

The four ways Bitrix24 sends email

1. Built-in SMTP (bitrix24.ru / .com default)

When you type an email directly into a CRM deal or lead and hit send without configuring anything, Bitrix24 sends through its own shared SMTP infrastructure, with From addresses under @bitrix24.ru or@bitrix24.com. This works but is obviously unprofessional for anything but a brand-new trial, and has mediocre placement because it is a shared pool used by every Bitrix24 tenant.

2. Mail client integration (IMAP/SMTP to your real mailbox)

Bitrix24 can integrate with your existing corporate mailbox via IMAP and SMTP, sending mail as if you had sent it from Outlook or Thunderbird. In this mode, deliverability is whatever your existing mail infrastructure delivers — if your Microsoft 365 or Google Workspace is healthy, Bitrix24 inherits that health. This is the recommended mode for most B2B sales teams.

3. OAuth integration (Google, Office 365, Yandex 360)

Similar to mail client integration but uses OAuth instead of stored passwords. Better security, same deliverability characteristics — your provider sends the mail, Bitrix24 just orchestrates.

4. ESP connector (bulk campaigns)

For bulk marketing campaigns, Bitrix24 connects to Unisender, SendPulse, eSputnik, and similar ESPs. In this mode, the ESP handles authentication, IP warm-up, and bounce management; Bitrix24 is just the segmentation and trigger layer.

Why placement varies so much between modes

The core issue is that each mode uses a different sending infrastructure with a different reputation profile. A single Bitrix24 tenant can have:

Transactional notifications (task assignments, mentions) going out via Bitrix's shared SMTP — placement varies by mailbox provider and time of day.
Sales emails going via Google Workspace OAuth — placement driven by your Google domain reputation.
Marketing campaigns going via Unisender — placement driven by Unisender IP pool reputation and your ESP sub-account hygiene.

This is why "Bitrix24 deliverability" as a question has no single answer. You need to test each path separately and treat them as independent sending programs.

CIS mailbox provider landscape

For any Bitrix24 tenant whose customers are in the CIS, these are the receiving inboxes that matter. Rough share-of-inbox based on operator reports and our own seed-test data:

Mail.ru group (mail.ru, list.ru, bk.ru, inbox.ru) — ~35% of consumer inboxes, strict on DKIM alignment and DMARC.
Yandex (yandex.ru, ya.ru, yandex.com) — ~25%, engagement-weighted filtering, aggressive Promotions classification.
Gmail — ~20% of CIS consumer mail, engagement-driven, requires DMARC for bulk.
Corporate M365 and Google Workspace — dominant for B2B recipients, strict on authentication.
Regional and ISP mail (rambler.ru, ukr.net, tut.by, nm.ru) — small but non-trivial tail.

Seed-test workflow per connector

In Bitrix24, identify every sending path your tenant uses. Typical setup: OAuth mailbox for sales, built-in SMTP for system notifications, ESP connector for bulk. Some teams also have an SMS/email gateway integration.
For each path, trigger a representative message to a seed test pool covering Mail.ru group, Yandex, Gmail, and M365. A deal-notification email is the right seed for the OAuth path; a campaign is right for the ESP path.
Record placement for each path separately. Treat each as its own deliverability program with its own baseline.
Monitor the ratio of Inbox vs Promotions vs Spam over time. A sudden shift on one path but not the others points directly at the responsible infrastructure.

The inbox-check seed test covers the full CIS provider set, and is free with no account required, so you can run a pre-flight check before a campaign goes out and verify each Bitrix24 connector independently.

Bitrix integration in beta

A native Bitrix integration is in private beta — run placement tests in-platform and get alerts on drops.

→ Join the beta waitlist

DNS recommendations for Bitrix24 users

The DNS you need depends on the sending path. Here is the sensible default set for a CIS-focused Bitrix24 tenant on corporate domainexample.ru:

example.ru.   TXT   "v=spf1 include:_spf.google.com include:_spf.unisender.com ~all"
google._domainkey.example.ru.   TXT  "k=rsa; p=..."   ; Workspace DKIM
uni1._domainkey.example.ru.     TXT  "k=rsa; p=..."   ; Unisender DKIM
_dmarc.example.ru.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.ru; pct=100"

Note that you do not include bitrix24.ru SPF in your domain — when mail is sent from the built-in SMTP, the From address is a @bitrix24.ru address, which is under Bitrix's control, not yours. Do not mix that reputation with your own.

Common Bitrix24 pitfalls

Mass send via OAuth mailbox. Using your Google Workspace mailbox to send 500 proposals in a day will get you rate-limited and possibly locked out. Use the ESP connector for anything over a few dozen recipients.
CRM email templates with tracking pixels. The engagement-tracking pixel Bitrix24 inserts can trigger image-to-text-ratio filters on otherwise-innocent short emails.
Reply address mismatch. Bitrix24 sometimes sends with a Reply-To pointing at a @bitrix24 tracking address. Customers reply to the wrong place and the salesperson never sees it. Configure Reply-To explicitly on the mailbox integration.
Missing feedback loops. Enrol your sending domain in Mail.ru's and Yandex's postmaster programmes to receive complaint data and improve list hygiene.

FAQ

Should I use Bitrix24's built-in SMTP for production?

Only for system notifications inside your own company (task assignments, internal mentions). For anything going to a customer, use mailbox OAuth for 1-to-1 mail and an ESP connector for bulk. The built-in SMTP is fine for trials but undifferentiated in reputation for real business use.

Does Bitrix24 support DKIM signing for my own domain?

When you send via OAuth mailbox integration, DKIM is handled by Google/Microsoft/Yandex — their keys, your domain. When you send via ESP connector, DKIM is handled by the ESP. In both cases, you publish the DKIM public key in your DNS.

Can Bitrix24 handle bounces automatically?

Partially. Mailbox integrations forward bounces into the CRM activity stream. ESP connectors report bounces back via their APIs. The built-in SMTP path has the weakest bounce handling and is another reason to avoid it for external mail.

How do I know which connector a specific email went through?

Check the message headers. The Received and X-Mailer headers will identify the sending infrastructure (Bitrix SMTP, Google, Unisender, etc.). Bitrix24's activity log also records the channel used for each mail event.