MX records edited

It appears that you're experiencing issues with your MX records not syncing properly between your DNS provider (10web) and AWS. This can cause problems with email delivery, particularly receiving emails. Here are a few points to consider:

1. MX Record Configuration: The MX records you've entered (mx.zoho.eu, mx2.zoho.eu, mx3.zoho.eu) seem correct for Zoho Mail services in Europe. However, if they're still showing as .com instead of .eu on 10web, this indicates a synchronization issue.

2. DNS Propagation: Changes to DNS records, including MX records, can take up to 24-48 hours to propagate fully across the internet. If you've recently made these changes, you may need to wait for the propagation to complete.

3. AWS Route 53 and 10web: If you're using both AWS Route 53 and 10web for DNS management, there might be conflicts. Ensure that only one service is authoritative for your domain's DNS. If you're using Route 53, make sure your domain's nameservers are pointing to Route 53's nameservers.

4. Verification Failure: The MX verification failure you're experiencing could be due to the records not being properly propagated or conflicts between different DNS providers.

To resolve this:

1. Confirm which DNS provider (AWS Route 53 or 10web) should be authoritative for your domain.
2. Ensure all MX records are correctly entered in the authoritative DNS provider's console.
3. If using Route 53, verify that your domain's nameservers are correctly set to Route 53's nameservers.
4. After making any changes, wait for at least 24 hours for DNS propagation.
5. Use DNS lookup tools to verify that the correct MX records are visible publicly.

If the issue persists after these steps, you may need to contact your DNS provider's support for further assistance.

Sources
How to configure two different email servers (MX)? | AWS re:Post
Domain hosted in Route53 does not return IP-address or MX-records. How to fix? | AWS re:Post