Hi, Am 22.07.26 um 12:29 schrieb kasak:
I have raised log level and i was wrong. it seemd that MX record is actually used,
They are probably working on their system because that is now a very different message. They might had a missing A record or wrong IP (because of the "No vaild route" error). But at least now they have a reachable system.
> 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?
Unless you are using them in a relay action, an unverified cert has no effect (ignoring SPAM filter weights) on the deliverability of e-mail.
Even in this day and age of free certs and ACME smtp puts deliverability over security. Since there is no human to ask (like a browser could) it defaults to "not my problem".
You also cut your logs very tight. We don't even know what happened to the mail. Show the rest of 87e202d6092a9133.
