IMAP/SMTP Configuration for Bitrix24
Emails from Bitrix24 arrive from [email protected], automation notifications end up in spam, and client replies don't reach the CRM. All of this is solved by proper IMAP/SMTP configuration — the portal's basic mail infrastructure.
Outgoing Mail (SMTP)
By default Bitrix24 sends system emails (invitations, notifications, emails from CRM automations) through its own servers. The result — emails from the bitrix24.ru domain, low deliverability rating.
Configuring your own SMTP: Settings → Mail → Outgoing Mail → Configure Server.
Parameters for major providers:
| Provider | Server | Port | Encryption |
|---|---|---|---|
| Google Workspace | smtp.gmail.com | 587 | TLS |
| Yandex 360 | smtp.yandex.ru | 587 | TLS |
| Mail.ru for Business | smtp.mail.ru | 465 | SSL |
| Custom Postfix | mail.company.com | 587 | TLS |
For Google Workspace and Yandex 360 — an app password, not the regular account password. Created in the mail service's security settings.
Configuring DKIM and SPF
After connecting SMTP it is important to verify that SPF and DKIM are configured for the sending domain. Without them, emails will end up in spam regardless of SMTP quality.
SPF — a DNS TXT record that authorizes Bitrix24 servers (or your SMTP) to send emails on behalf of the domain. Example for Yandex 360:
v=spf1 include:_spf.yandex.ru ~all
DKIM — email signing with a private key. For Yandex 360 and Google Workspace — a DNS record with the public key provided by the provider is added. For custom Postfix — opendkim is configured.
Checking settings: mail-tester.com or mxtoolbox.com. Test email from Bitrix24 → header analysis.
Incoming Mail (IMAP)
Incoming mail is needed for two scenarios:
- CRM email tracker — syncing correspondence with clients
- Receiving replies to automated emails from automations
Configuring IMAP for a personal mailbox: CRM → Mail → Connect Mail → [Provider] → IMAP. For corporate servers — manual configuration:
| Parameter | Value |
|---|---|
| Server | imap.company.com |
| Port | 993 (SSL) or 143 (STARTTLS) |
| Login | [email protected] |
| Password | password or app password |
Check IMAP availability before configuring:
openssl s_client -connect imap.company.com:993
If the connection cannot be established — IMAP is disabled on the server or blocked by a firewall.
Shared Outgoing Mail for Notifications
Separately from personal mailbox SMTP, mail for system notifications is configured: password resets, invitations, task notifications. Path: Settings → General Settings → Notification Mail.
It is recommended to use a dedicated address such as [email protected] — to avoid mixing system emails with working correspondence.
Common Problems
Emails go to spam — SPF/DKIM not configured, or the domain is on a blacklist. Check via mxtoolbox.com → Blacklists.
IMAP not syncing — the provider requires confirmation of a "new application" via their webmail interface, or the app password has expired. Recreate the app password.
Emails duplicated in CRM — the mailbox is connected twice (e.g., both as personal via IMAP and synced via OAuth). Keep one connection method.
Authentication failed error — Google and Yandex require an app password, not the account password. Two-factor authentication must be enabled to generate an app password.
Setup Timeframes
| Task | Time |
|---|---|
| SMTP configuration and deliverability test | 1–2 h |
| SPF/DKIM configuration | 1–2 h (+ up to 24 h for DNS propagation) |
| IMAP configuration for the team | 2–4 h |
Full mail infrastructure setup — 1 working day accounting for deliverability checks and DNS propagation.