Bitrix24 - why do emails end up in spam?

Question

Fight against spam

Hello everyone, we bought an annual subscription on our own head, set up integrations, and when we got to the main part of the CRM system, we realized that it was a complete failure, the support responds exactly once a day (but at first they ignored the week, in general, their TP is a separate story, pulls on article for habr).
Therefore, a question for the community:
- Yandex mail is connected (pdd)
- We form a response to the lead by e-mail through CRM, the letter quietly falls into spam with a delay of 20-30 minutes
- Among other things, the lead is indicated by the addressee 2 times (To:)
Full headers letters:

Received: from mxfront12g.mail.yandex.net ([127.0.0.1])
  by mxfront12g.mail.yandex.net with LMTP id cRQxLe5A
  for <[email protected]>; Tue, 19 Sep 2017 14:12:02 +0300
Received: from mail-001.bitrix24.com (mail-001.bitrix24.com [46.235.53.71])
  by mxfront12g.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id pR94AZBLb6-Bu78jWwh;
  Tue, 19 Sep 2017 14:11:56 +0300
  (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
  (Client certificate not present)
Return-Path: [email protected]
X-Yandex-Front: mxfront12g.mail.yandex.net
X-Yandex-TimeMark: 1505819516
Authentication-Results: mxfront12g.mail.yandex.net; spf=pass (mxfront12g.mail.yandex.net: domain of aparser.bitrix24.ru designates 46.235.53.71 as permitted sender, rule=[ip4:46.235.53.71]) [email protected]
X-Yandex-Spam: 4
Received: from mon-ru.bitrix24.ru (mon-ru.bx24.net [10.10.10.2])
  (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
  (No client certificate requested)
  by mail-001.bitrix24.com (Postfix) with ESMTPS id 83A6C4400C
  for <[email protected]>; Tue, 19 Sep 2017 14:11:56 +0300 (MSK)
Received: from cp.bitrix24.com (unknown [10.10.10.36])
  by mon-ru.bitrix24.ru (Postfix) with ESMTP id 45C19206BA
  for <[email protected]>; Tue, 19 Sep 2017 14:11:56 +0300 (MSK)
Received: from cp-linx-015 (localhost [127.0.0.1])
  by cp.bitrix24.com (Postfix) with SMTP id 3C5742015A;
  Tue, 19 Sep 2017 14:11:56 +0300 (MSK)
To: [email protected]
Subject: =?UTF-8?B?dGVzdCBsaWRh?=
From: =?UTF-8?B?0JzQuNGF0LDQuNC7INCu0YDRjNC10LLQuNGH?= <[email protected]>
Reply-To: =?UTF-8?B?0JzQuNGF0LDQuNC7INCu0YDRjNC10LLQuNGH?= <[email protected]>
To: [email protected]
Subject: test lida
Message-Id: <[email protected]>
X-Priority: 3 (Normal)
Date: Tue, 19 Sep 2017 14:11:56 +0300
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Yandex-Forward: fc21fd3b66f459c28acb802b1618a148

test 2<img src="http://aparser.bitrix24.ru/bitrix/tools/track_mail_read.php?tag=crm.eyJ1cm4iOiI0OC0wVlZBSzEifQ%3D%3D" border="0" height="1" width="1" alt="Read" />

Bitrix support sent me to understand Yandex :) despite the fact that the mail leaves their server.
The question is where to look, who is to blame, what to do, how to live with it?

Answer 1

They kick
you right You need to set up SPIF and DKIM on Yandex.
And tell Bitrix the parameters for DKIM.