Emails not arriving in your mailbox (not receiving)
On this page
Every message this server receives or refuses is recorded. Start with Delivery reports: if the message is there, it tells you what happened; if it is not there, the message never reached this server.
Symptoms
- People say they sent you mail, but it is not in your inbox.
- The sender gets a bounce ("Mail delivery failed", "Undelivered Mail Returned to Sender").
- Mail from some senders arrives, from others not.
Causes
Most likely first:
- The domain's MX record does not point to this server, so mail goes elsewhere (often the old host).
- The message was put in the Junk folder by the spam filter.
- The mailbox is full (its quota is reached).
- The address does not exist — no mailbox or forwarder with exactly that name, and no catch-all.
- Email routing is set to Remote mail server for a domain whose mail should be received here.
- The spam filter refused the message (very high score), or greylisting delayed it for a few minutes.
Fix
Look it up in Delivery reports
- Open Email Accounts (section Email) and click Delivery reports.
- Search for the sender's or your address, choose Incoming under Direction and a Period.
- The Result shows
sent(delivered),deferred(will be retried),bounced,rejectedorexpired. Details gives the reason.
No entry at all means the message did not reach this server: check cause 1.
1. MX record
Open Email Accounts → Email routing. The Received column shows "on this server" or "on another mail server" for each domain, from the domain's MX record.
- If your DNS is hosted here (nameservers of this server), the MX record is already correct.
- If your DNS is elsewhere, set the MX record there to the mail server name of this server (look up the
MXrecord in Zone Editor, section Domains), and add the records listed under Email deliverability with their Copy buttons.
Until the change has spread, some mail still goes to the old server.
2. Junk folder
Open Webmail (Open Webmail on Email Accounts) and look in Junk. Mail scored as spam is moved there, never deleted. To stop it, click Autoresponder & filters next to the mailbox and add the sender or domain to Always allow (never Junk), then Save.
3. Mailbox full
The mailbox list on Email Accounts shows each mailbox's size next to its Quota, with a bar. If it is full, delete old mail in webmail (and empty Trash) or in your mail app. Senders get a bounce while it is full. The quota is chosen when the mailbox is created (Quota (MB, 0 = unlimited)).
4. The address does not exist
Check the spelling of the address in Email Accounts and Forwarders. Mail to unknown addresses is refused unless Mail to unknown addresses (catch-all) delivers it to a mailbox.
5. Email routing
In Email routing, choose Automatic (from the MX record) for the domain, or Local mail server if mail should always be received here, and save. With Remote mail server, this server does not keep mail for that domain.
6. Refused or delayed by the spam filter
A rejected result with a spam reason means the score was above the server's refusal level; the sender got an error. Ask your host to check the message. A message delayed by greylisting arrives by itself after the sender's server retries, usually within minutes.
Still not working?
- Mail to the accounts of a suspended hosting account is not delivered.
- Send a test from another provider (for example a free webmail account) and look it up in Delivery reports within a minute or two.
- Contact your host through Support with the sender address, your address and the time.
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
- Emails you send go to spam (Gmail, Outlook)
Your mail lands in spam or is rejected as unauthenticated. Set up SPF, DKIM and DMARC from the Email deliverability table and check the usual causes.
- Cannot send email: SMTP authentication failed
Your mail app or website cannot send: "SMTP authentication failed", refused or timed out. Check the username, ports 465/587, bans and the error.
- Website not working after changing nameservers (DNS)
You changed nameservers or DNS records and the site still shows the old server or nothing. Check where the domain points, how long DNS takes and what to fix.