But you’re pointing the MX record to kayanvoyages.tn, and the A for kayanvoyages.tn is Proxied (
), see the fifth (#5) record from the top, the one between ftp and webdisk.
Due to way your DNS records has been set up, it is the A record for kayanvoyages.tn that matters, and the Proxy status that actually matters, will be the one that has been set on this specific record.
-
Change the
MXrecord to point to “mail.kayanvoyages.tn”. -
Change “
mail” to become anArecord instead, that is pointing to the same IP address as “kayanvoyages.tn”, - BUT:
→ Make sure “mail” keep the Proxy status set to Unproxied (
) / DNS-only. -
You should also remove duplicating mechanisms from the latest DNS record, the
TXTwith “v=spf1 ...”, which can be done by making it become:
“v=spf1 ip4:196... -all”
That said, -
Even after these changes, I’m still concerned about your email deliveries (when you’re sending to others), as it seems like you’re running it all from a residential Internet connection (e.g. from home).
It seems like there are two (2) Reverse DNS (PTR) records attached to the IP address, - however, one of the host names does not point back to the original IP address, which means that some servers may randomly (round-robin like) hit the wrong PTR, and due to the mismatch, decide to reject your email
You should at the bare minimum work together with your ISP, to clean up the current mess, and make sure that the actual Reverse DNS (PTR) record that you keep (or otherwise switch to) matches one of the domain name(s) of your own organisation, and not any domain name(s) belonging to third parties.
Make sure you keep only one single Reverse DNS (PTR) record for the IP address.
My suggestion, based on and according to the DNS records you’ve demonstrated, would be to work with your ISP to clear all current PTR records for the IP address, and then set a new one, pointing to “mail.kayanvoyages.tn”.