Why is my mail delayed, rejected or not arriving?
Check the emails-per-hour limit, the MX records, delivery tracking and DKIM to find out why a message is delayed or never arrives.
Start with delivery tracking: Email, Tracking shows what happened to a message (delivered, bounced, deferred), limited to your own domains.
Mail from a website is delayed or rejected
Your plan has an emails-per-hour limit that covers PHP mail() and authenticated sending on port 587. Over the limit you get a temporary rejection and the sender retries. Check Usage. A message that cannot be attributed to an account is also rejected with a temporary error.
Mail to a domain never arrives
- Check the domain's MX. Adding a mail domain makes this node treat it as local; if the MX points to another provider, delete the domain from the mail domains or move the MX here (why).
- Check SPF, DKIM and DMARC records exist; they are published automatically only if this node serves the zone.
- Look at the tracking entry for the exact reason given by the other server.
Mail lands in spam
A new IP address needs warm-up. Send in small volumes at first and increase over days. Mail from PHP mail() is not DKIM-signed; use authenticated SMTP when signing matters.
Admin view
Admins can list, requeue or delete queued messages under Email, Mail queue; every change is audited first.
Last updated: 2026-10-10