Why is Communigate mail not coming?

Question

Domain Name System

Good afternoon, comrades I have
installed CG on debian without any connection with spamassassin yet.
I set it up according to the read manuals, while without prohibitions (by lan, wan, spam, etc.)
The IP address is valid white.
I set up MX records in the domain, and also set up routing within the network.
What I have: mail is sent validly even to Africa. Letters do not come at all, even from Africa.
Pieces of logs:
If you look in Observation - Mail - Queue we see a queue of letters, looking inside we see the state "ready".
If you look in Observation - Mail - SMTP, we see "to whom" our domain is in the opening connection state. If you connect inside:
Module Status Last Problem
SMTP Processing domain.ru: no response
Well, turn.
Log for 1 letter
11:46:05.959 5 SMTPI-000007([37.140.190.182]:35837) out: 220 mail.MYDOMAIN.ru ESMTP CommuniGate Pro 6.2.12\r\n
11:46:05.968 5 SMTPI-000007( [37.140.190.182]:35837) inp: EHLO forward102o.mail.yandex.net
11:46:05.968 5 SMTPI-000007(forward102o.mail.yandex.net) out: 250-mail.MYDOMAIN.ru is pleased to meet you \r\n250-DSN\r\n250-SIZE\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-SMTPUTF8\r\n250 EHLO\r\n
11:46:05.977 5 SMTPI-000007(forward102o.mail.yandex.net) inp: STARTTLS
11:46:05.977 5 SMTPI-000007(forward102o.mail.yandex.net) out: 220 please start a TLS connection\r\n
11:46:06.009 2 TLS-000002 created(TLSv1.2,ECDHE_AESGCM256_SHA384) for SMTPI-
000007 mail.MYDOMAIN.ru)
11:46:06.268 5 SMTPI-000007(forward102o.mail.yandex.net) s-inp: EHLO forward102o.mail.yandex.net
11:46:06.269 5 SMTPI-000007(forward102o.mail. yandex.net) s-out: 250-mail.MYDOMAIN.ru is pleased to meet you\r\n250-DSN\r\n250-SIZE\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-SMTPUTF8\ r\n250 EHLO\r\n
11:46:06.277 5 SMTPI-000007(forward102o.mail.yandex.net) s-inp: MAIL FROM: SIZE=1338
11:46:06.277 4 SMTPI-000007(forward102o.mail.yandex.net) SPF(yandex.ru) checking
11:46:13.084 4 SMTPI-000007(forward102o.mail.yandex.net) SPF(yandex.ru) result =pass
11:46:13.084 4 SMTPI-000007(forward102o.mail.yandex.net) checking MX-record for yandex.ru
11:46:13.094 4 SMTPI-000007(forward102o.mail.yandex.net) checking relay mx. yandex.ru
11:46:13.094 5 SMTPI-000007(forward102o.mail.yandex.net) reverse-connecting
11:46:13.094 4 SMTPIC-000007 connecting [0.0.0.0]:0 -> [213.180.193.89]:25
11:46:13.146 5 SMTPIC-000007 inp: 220 mxfront4q.mail.yandex.net (Want to use Yandex.Mail for your domain? Visit http://pdd.yandex.ru)
11:46:13.146 4 SMTPI-000007(forward102o.mail.yandex.net) [192.168.2.55]:39898 -> [213.180.193.89]:25 reverse-connected
11:46:13.146 5 SMTPIC-000007 out: HELO mail .MYDOMAIN.ru\r\n
11:46:13.154 5 SMTPIC-000007 inp: 250 mxfront4q.mail.yandex.net
11:46:13.154 5 SMTPIC-000007 out: MAIL FROM:<>\r\n
11:46 :13.165 5 SMTPIC-000007 inp: 250 2.1.0 <> ok
11:46:13.165 5 SMTPIC-000007 out: RCPT TO:\r\n
11:46:13.171 5 SMTPIC-000007 inp: 250 2.1.5 recipient ok
11:46:13.171 5 SMTPIC-000007 out: QUIT\r\n
11:46:13.175 5 SMTPIC-000007 inp: 221 2.0.0 Closing connection.
11:46:13.175 4 SMTPIC-000007 closing connection
11:46:13.175 5 SMTPI-000007(forward102o.mail.yandex.net) s-out: 250 [email protected] sender accepted\r\n
11:46:13.175 5 SMTPI-000007(forward102o.mail.yandex. net) s-inp: RCPT TO: ORCPT=rfc822;[email protected]
11:46:13.175 4 SMTPI-000007(forward102o.mail.yandex.net) checking MX-record for MYDOMAIN.ru
11:46:13.176 5 SMTPI-000007(forward102o.mail.yandex.net) s-out: 250 [email protected] will relay to a backed-up host\r\n
11:46:13.176 5 SMTPI-000007(forward102o.mail.yandex. net) s-inp: DATA
11:46:13.176 5 SMTPI-000007(forward102o.mail.yandex.net) s-out: 354 Enter mail, end with "." on a line by itself\r\n
11:46:13.233 2 SMTPI-000007(forward102o.mail.yandex.net) [280005] received encrypted, 1862 bytes
11:46:13.233 5 SMTPI-000007(forward102o.mail.yandex.net) s-out: 250 280005 message accepted for delivery\r\n
11:46:13.233 5 SMTPI-000007(forward102o.mail.yandex.net) s-inp: QUIT
11:46:13.233 5 SMTPI-000007(forward102o.mail.yandex.net) s-out: 221 mail.MYDOMAIN.ru CommuniGate Pro SMTP closing connection\r\n
11:46:13.233 4 SMTPI- 000007(forward102o.mail.yandex.net) TLS connection is closing 11 :46 :
13.233 46:13.233 4 SMTPI-000007(forward102o.mail.yandex.net) releasing stream 11:46:13.233 4 SMTP(MYDOMAIN.ru) [280005] enqueueing (active) 11:46:13.233 5 SMTP waiting: active: MYDOMAIN. en
11:46:13.233 4 SMTP queue is empty Message delivery to '[email protected]' delayed
SMTP module(domain mydomain.ru reports: mail.mydomain.ru: no response)

Answer 1

There is a suspicion that the machine with kommunigeyt looks at some tricky internal dns where mail.mydomain.ru - resolves into something else.
I'm not particularly familiar with CGP - maybe it's his corporate style to log like this, but what worries me is these lines:
11:46:13.175 4 SMTPI-000007(forward102o.mail.yandex.net) checking MX-record for MYDOMAIN. ru - which one it checks for the MX records of the local domain for which it is responsible - it's not clear to me
and
11:46:13.233 5 SMTP waiting: active: MYDOMAIN.ru - well, it feels like he tried to send mail for this domain somewhere - maybe I'm wrong.
And another mystery - if you get NDR on Yandex - then it's not entirely clear where it is in the log?
(I can assume this response comes from the logs from the "SMTPIC-000007" module, where for some reason it does another mysterious action: "reverse-connecting" - perhaps this is some kind of tricky anti-spam check - known only to pumped communicators, and after all, there is a full-fledged session. And the line:
11:46:13.154 5 SMTPIC-000007 out: MAIL FROM:<>\r\n
hints to us that this is NDR, but how did it happen that NDR was sent even before the completion of the unsuccessful delivery of the current letter ...
In general, I have to your log has more questions than you -)