How to manage the mail queue (retry or delete stuck email)
On this page
The mail queue holds messages the server could not deliver yet. Most leave on their own after a retry. A long queue usually means one receiving server refuses your mail, or an account is sending spam.
Before you start
You need the administrator panel (https://<server>:2087). Resellers do not see this page.
Open the queue
- Open Mail Queue & Spam in the menu (section Email). The Mail queue tab opens.
- The heading shows the last 24 hours: messages sent, deferred, bounced and rejected.
- The list shows each waiting message: Queued (time, with a deferred badge for retried messages), From, To / reason and Size. Above it you see how many message(s) waiting. When the queue is long, only the first messages are listed.
Click Headers in a row to read the message's headers, for example to see which account or script sent it.
Actions
- Retry selected — tick messages and try to deliver them now.
- Delete selected — tick messages and delete them (you are asked to confirm).
- Retry all — try to deliver every queued message now.
- Delete all deferred — delete every message that is waiting for a retry (you are asked to confirm Delete ALL deferred mail?).
Deleted messages are gone; the sender is not told.
Delivery reports for every domain
The Delivery reports tab shows every delivery attempt of the last 30 days, for all domains, read from the mail server log every two minutes. Search by Address or message ID, Result (Sent, Deferred, Bounced, Rejected, Expired), Direction and Period. Customers see the same report for their own domains only.
Reading the reasons
The text under each recipient in To / reason comes from the receiving server. Typical cases:
- Connection timed out or refused — the receiving server is down or unreachable; retries continue.
- Rate limited or "try again later" — the receiver slows down mail from your server; it usually clears.
- Blocked or listed — the receiver distrusts your server's IP address. See server setup for email delivery.
- Many messages from one sender to random addresses — likely spam from a hacked mailbox or website.
Common questions
The queue is full of spam from one account. What do I do?
Delete the messages, then have the customer change the mailbox password or clean the website. The hourly sending limit keeps the damage small meanwhile; the Sending limits tab shows which accounts reached it.
Does Retry all help with blocked mail?
Only after the cause is fixed. Retrying mail that the receiver refuses gives the same answer.
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
- 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.
- How to configure the server spam filter and greylisting
Turn spam filtering on or off for the whole server, set the scores for moving mail to Junk and refusing it, and use greylisting against spam bots.
- 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.