Emails you send go to spam or don't arrive (how to fix)
On this page
Symptoms
- Recipients find your mail in their spam or junk folder.
- Recipients say nothing arrived at all.
- You get a bounce message saying your mail was rejected.
Causes
Most likely first:
- SPF, DKIM or DMARC is missing or wrong for your domain.
- The message was delivered, but the receiver's filter put it in spam because of its content or because people often mark your mail as spam.
- The domain's email is hosted elsewhere and the SPF record does not allow this server.
- Your account reached its hourly sending limit, so messages are waiting.
- A hacked mailbox or website sent spam, and receivers now distrust the server.
- The server's own setup (reverse DNS of its IP address, its name, a blocklist entry).
Fix
1. Check SPF, DKIM and DMARC
Open Email Accounts (section Email) in the control panel (https://<server>:2083) and scroll to Email deliverability. Every row should show Valid. For each Missing row, add the shown record at your DNS host. See SPF, DKIM and DMARC.
2. Find out what happened to the message
Click Delivery reports on the same page and search for the recipient's address. See delivery reports.
- Sent means the receiver accepted it; it is in their spam folder or filtered by their rules.
- Bounced or Deferred: read Details. It usually names the reason, for example an authentication failure or a blocklist.
3. Improve the message itself
- Send from a real mailbox on your domain, not from a free address with your domain as reply address.
- Avoid messages that are only an image, link shorteners, and lots of capital letters or exclamation marks.
- Send newsletters only to people who agreed, through a mailing list, which adds an unsubscribe link.
- Ask regular contacts to add your address to their contacts.
4. Email hosted elsewhere
If your domain's mailboxes are at another service but your website sends mail from this server, add this server to the domain's SPF record (one SPF record only). The Email deliverability table shows a suggested value.
5. Waiting messages (sending limit)
The top of Email Accounts shows sent in the last hour and your limit. Over the limit, messages wait and go out later. See hourly sending limit.
6. Hacked mailbox or website
If you did not send many of the messages yourself, change the mailbox passwords and have the website checked for malware. Tell your hosting provider.
Still not working?
Contact your hosting provider with the recipient address, the time you sent the message and the Details text from the delivery report. Server-wide causes, such as reverse DNS or a blocklisted IP address, can only be fixed by the server administrator; see server setup for email delivery.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- SPF, DKIM and DMARC records for your domain explained
What SPF, DKIM and DMARC are, which records the control panel creates automatically, how to check them, and how to add them when your DNS is elsewhere.
- How to check if an email was delivered (delivery reports)
Find out what happened to a message sent from or to your domain in the last 30 days: delivered, delayed, bounced or rejected, and why.
- Hourly email sending limit explained (emails per hour)
Each hosting account may send a set number of emails per hour. See your limit and usage, what happens over it, and how administrators change it.
- Server checklist for reliable email delivery (hostname, PTR)
Set up the server so other mail providers trust it: hostname and its certificate, reverse DNS (PTR), IPv4 sending, open mail ports and blocklist checks.