If the sending domain cannot be successfully validated, the user now receives a clear error message.
An issue has been resolved whereby a valid sender domain was classified as invalid during the regular checking of DNS entries. This occurred due to timeouts when querying the DNS resolver.
An issue has been resolved whereby the Messages API returned a 500 status when message filters were used.
An issue has been resolved where newly created sender domains remained in the Creating status instead of the Validating status.
A DNS pre-check for the recipients domain at message injection phase has been added. If MailOut is not able to resolve the domain, the message will be rejected.
We have implemented stricter measures for processing messages containing malware. If a message is classified as malware, the sending domain will be blocked to prevent any further potential distribution of malware.
In case your sending domain has been blocked, you have to create a support ticket.
We updated the validation when creating a new sending domain to support RFC 1123 as well as RFC 2181. Sending domains that can’t receive mail, aren’t available to the public for registration, or are reserved for testing are rejected.
MailOut regularly checks the validity of the required DNS records for a sending domain to ensure that messages can be delivered successfully at all times.
If the DNS records for a sending domain cannot be successfully validated for 7 days, DNS validation is paused.
Users can restart the validation process by manually triggering DNS validation through the “Trigger DNS Validation” function in the portal or by using this API endpoint.