I have raised log level and i was wrong. it seemd that MX record is actually used, but it can't verify cert: Jul 22 13:05:43 gater smtpd[1637]: 87e202d6092a9133 mta connecting address=smtp://223.255.246.167:25 host=mail.beml.co.in Jul 22 13:05:43 gater smtpd[1637]: 87e202d6092a9133 mta connected Jul 22 13:05:44 gater smtpd[1637]: 87e202d6092a9133 mta tls ciphers=TLSv1.3:TLS_AES_256_GCM_SHA384:256 Jul 22 13:05:44 gater smtpd[1637]: 87e202d6092a9133 mta cert-check result="unverified" fingerprint="SHA256:3ae402c1b3fdda5e4a9bf60e50f51549eb401fe917866e7557dd18302f41e1d8"
can it be the problem? ср, 22 июл. 2026 г. в 13:11, Damian McGuckin <[email protected]>: > > On Wed, 22 Jul 2026, kasak wrote: > > > Hello, misc! > > Tell me please, when we send mail, it should go to MX record, not A > > record, am I right? > > Please have a look. There is domain bemlltd.in that has MX records, > > but no A record, and I can't send mail to them: > > Jul 22 09:08:23 gater smtpd[96619]: smtp-out: No valid route for > > [connector:[]->[relay:bemlltd.in,smtp,heloname=tvema.ru],0x0] > > It is a more subtle that that. > > The A record exists but there is no route to it, e.g. you cannot ping > > mail.bemlltd.in > > which is the host in the MX record (which has an A record). > > Thanks - Damian
