MX record priority not respected?

[fipoac]

I tried to send an email to a domain, which is used in Azure but not enabled for Exchange. I guess because of some sort of domain validation there is an additional MX record aside of the true mail server.
In this case ms14369303.msv1.invalid. but with priority 32767, the other record has priority 10.
If I try to send a mail to this domain, stalwart seems to use the wrong MX record, which leads to the mailer-deamon sending me a Failed to deliver message with connection to 'ms14369303.msv1.invalid' failed: record not found for MX
The main mail server in the mx record is reachable and other mail services seem to send just fine.
Is this a known issue? Is there a workaround?

[fipoac]

Well sorry all, my bad.
I looked a the logs and found this error: TLS error: invalid peer certificate: Other(OtherError(UnsupportedCertVersion)) when stalwart tried to connect to the correct server. So seems this mail server uses an old encryption.