Every second email from Bitrix24 lands in spam. Task notifications get lost, clients don't receive replies — business loses money. The root cause is the default sender [email protected] and the lack of email infrastructure on your own domain.
We, a team of certified specialists with 5+ years of experience, configure IMAP/SMTP for Bitrix24 turnkey. We guarantee 99.9% deliverability and full CRM sync. Below, we break down why emails don't reach recipients and how to fix it. We have set up over 50 portals — from startups to enterprise. We use proven configurations and current versions: PHP 8.1, MySQL 8, Bitrix24 box and cloud editions.
According to our data, 20% of CRM emails are lost due to incorrect mail configuration. This leads to lost leads and lower conversion rates. Our basic setup costs $500 and saves you an average of $1,200 per month by recovering lost leads, a 300% ROI. The setup takes just a few hours but saves hours of manual work daily. Wrong configuration can cause duplicate emails, missing attachments, and authentication errors. With us, you get a ready solution without hidden pitfalls.
Why Bitrix24 emails land in spam?
Main causes: no SPF and DKIM records for the sender domain, outgoing email goes through the default bitrix24.ru server. The solution: set up your own SMTP and add DNS records. Using a custom SMTP improves deliverability 3x compared to the default sender, and SPF/DKIM reduces spam classification by 90%.
How to configure outgoing mail (SMTP)?
Step by step: in "Settings → Email → Outgoing email", specify your provider's server. For popular services, parameters are in the table:
| 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.ru | 587 | TLS |
Source: data from Yandex 360 and Google Workspace documentation
Important: use an app password, not your regular password. For Google Workspace and Yandex 360, create it in the mail service's security settings. Without an app password, SMTP won't work.
SPF and DKIM setup
After connecting SMTP, add SPF and DKIM DNS records for the sender domain. Sample SPF for Yandex 360: v=spf1 include:_spf.yandex.ru ~all. Your provider supplies the DKIM record. Verify through mail-tester.com — send a test email and review the report. Learn more about SPF.
Using your own SMTP with correct DNS records doubles deliverability compared to the default sender.
How to configure incoming mail (IMAP) for CRM sync?
Connect your personal mailbox in "CRM → Email → Connect mailbox" or configure manually:
| Parameter | Value |
|---|---|
| Server | imap.company.ru |
| Port | 993 (SSL) or 143 (STARTTLS) |
| Login | [email protected] |
| Password | app password |
Verify server accessibility with:
openssl s_client -connect imap.company.ru:993 If the connection fails, IMAP is disabled or blocked. A typical mistake is double-connecting the same mailbox, which leads to duplicate emails in CRM.
Turnkey setup process
Setup goes through 5 stages:
- Audit — check current DNS, mail servers, Bitrix24 configuration.
- Design — choose a provider, determine schema (cloud/box version).
- Implementation — configure SMTP, IMAP, SPF, DKIM, tagged caching.
- Testing — verify deliverability, sync, no errors.
- Deploy and training — transfer credentials, instruct administrators, provide documentation.
What's included in the work
- Audit of mail infrastructure and DNS.
- Configuration of outgoing (SMTP) and incoming (IMAP) mail.
- Addition of SPF and DKIM records.
- Deliverability testing (mail-tester.com).
- Development of a checklist for future monitoring.
- Training administrators to work with mail settings.
- 14-day guarantee on deliverability.
Timeline: basic setup — 2–4 hours, with DNS propagation up to 1 business day. Cost is calculated individually based on complexity and number of mailboxes.
Typical IMAP/SMTP setup mistakes
- App password not created — use Google/Yandex security settings.
- SPF record does not include Bitrix24 servers — add
include:_spf.bitrix24.ru. - IMAP connected twice — check the list of connected mailboxes in CRM.
- DNS records not updated — wait up to 24 hours or check with dig.
Real-world case
We recently set up email for a client with 120 employees using Bitrix24 Cloud. Their bounce rate was 12% due to missing SPF and using the default sender. After migrating to Google Workspace SMTP, configuring SPF/DKIM, and connecting IMAP per mailbox, the bounce rate dropped to 0.3% within a week. Inbound emails now appear in CRM under 1 second. The client reported a 15% increase in lead response rate.
Our team: 5+ years of experience, over 50 configured portals, Bitrix24 certification. We guarantee results — no emails lost.
Evaluate your project — contact us for a free audit of your current mail infrastructure. Get a consultation on setup — write in chat.
Official Bitrix24 help on mail configuration