What did Yandex do with mail? How to fix?

Question

Mail server

Yandex did something with its mail,
now all letters from them come from everything from another forward*.mail.yandex.net domain,
which is not indicated in the DNS or anywhere else,
by itself such mail is rejected

or is this normal?

17:18:49.445 4 SMTPI-025457([77.88.28.105]:45756) [9.101.70.162]:25 <- [77.88.28.105]:45756 incoming connection(mycompany.org.ru)
17:18:54.544 4 SMTPI-025457([77.88.28.105]:45756) rsp: 220 mycompany.org.ru ESMTP CommuniGate Pro 6.1.20. It is you again :-(
17:18:54.560 4 SMTPI-025457([77.88.28.105]:45756) cmd: EHLO forward400p.mail.yandex.net
17:18:54.625 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 250-mycompany.org.ru is pleased to meet you\r\n250-DSN\r\n250-SIZE 53248000\r\n250-STARTTLS\r\n250-AUTH LOGIN PLAIN CRAM-MD5 DIGEST-MD5 GSSAPI MSN NTLM\r\n250-ETRN\r\n250-TURN\r\n250-ATRN\r\n250-NO-SOLICITING\r\n250-8BITMIME\r\n250-HELP\r\n250-PIPELINING\r\n250 EHLO
17:18:54.643 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: STARTTLS
17:18:54.643 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 220 please start a TLS connection
17:18:55.065 4 SMTPI-025457(forward400p.mail.yandex.net) TLS-169600(ECDHE_AES256_SHA) connection accepted for DOMAIN(mycompany.org.ru)
17:18:55.134 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: EHLO forward400p.mail.yandex.net
17:18:55.136 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 250-mycompany.org.ru is pleased to meet you\r\n250-DSN\r\n250-SIZE 53248000\r\n250-AUTH LOGIN PLAIN CRAM-MD5 DIGEST-MD5 GSSAPI MSN NTLM\r\n250-ETRN\r\n250-TURN\r\n250-ATRN\r\n250-NO-SOLICITING\r\n250-8BITMIME\r\n250-HELP\r\n250-PIPELINING\r\n250 EHLO
17:18:55.151 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: MAIL FROM:<[email protected]> SIZE=1357
17:18:55.151 4 SMTPI-025457(forward400p.mail.yandex.net) SPF(yandex.ru) checking
17:18:55.160 4 SMTPI-025457(forward400p.mail.yandex.net) SPF(yandex.ru) result=pass
17:18:55.160 4 SMTPI-025457(forward400p.mail.yandex.net) checking MX-record for yandex.ru
17:18:55.161 4 SMTPI-025457(forward400p.mail.yandex.net) checking relay mx.yandex.ru
17:18:55.274 4 SMTPI-025457(forward400p.mail.yandex.net) [9.101.70.162]:41163 -> [77.88.21.249]:25 reverse-connected
17:18:55.390 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 250 [email protected] sender accepted
17:18:55.390 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: RCPT TO:<[email protected]> ORCPT=rfc822;[email protected]
17:18:55.390 1 SMTPI-025457(forward400p.mail.yandex.net) Recipient [email protected] rejected: your host [77.88.28.105] is blacklisted. Send your questions to [email protected]
17:18:57.425 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 591 [email protected] your host [77.88.28.105] is blacklisted. Send your questions to [email protected]
17:18:57.425 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: DATA
17:18:59.525 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 554 no valid RCPT address specified
17:18:59.540 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: RSET
17:18:59.540 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 250 SMTP state reset
17:18:59.540 4 SMTPI-025457(forward400p.mail.yandex.net) cmd: QUIT
17:18:59.540 4 SMTPI-025457(forward400p.mail.yandex.net) rsp: 221 mycompany.org.ru CommuniGate Pro SMTP closing connection
17:18:59.540 4 SMTPI-025457(forward400p.mail.yandex.net) TLS connection is closing
17:18:59.540 2 TLS-169600 closed by SMTPI-025457
17:18:59.540 4 SMTPI-025457(forward400p.mail.yandex.net) closing connection
17:18:59.541 4 SMTPI-025457(forward400p.mail.yandex.net) releasing stream

Answer 1

Everything is in DNS and the FCrDNS check passes:
% host 77.88.28.105
105.28.88.77.in-addr.arpa domain name pointer forward400p.mail.yandex.net.
% host forward400p.mail.yandex.net
forward400p.mail.yandex.net has address 77.88.28.105
forward400p.mail.yandex.net has IPv6 address 2a02:6b8:0:1472:2741:0:8b7:105
In SPF this ip also hits
https://mxtoolbox.com/SuperTool.aspx?action=spf%3a...
Why is your Yandex host in the blacklists except you hardly anyone will answer.

Answer 2

right, blocking by dns names began to work

*-*-*-*
*.*.*.*.*