Fix a message that won't send
When a message doesn’t leave, Aster saves your draft and shows the reason. Find the message you saw below.
You hit your daily sending limit
The error says you hit your daily sending limit and names when the next attempt works. Every plan has a daily send limit, and higher plans allow more. See Storage and sending limits.
The message has too many recipients
One message can reach a set number of addresses, and that number rises over your first week with the account. Split the recipient list, and send the message in smaller batches.
Too many addresses at one provider
The error names a domain and a wait time. Sending to many addresses at the same provider in one hour gets mail servers blocked, so Aster spreads them out. Wait for the time shown, and then send the rest.
The attachments are too large
The error names the size your plan allows for one message. Remove a file, compress it, or share it as a link. A message can carry at most 50 attachments.
Aster has no key for the recipient
With required encryption turned on, Aster refuses to send to anyone without a key on file. To fix it, ask the recipient to open Aster so their keys publish, or turn required encryption off in Settings > Security > Encryption.
To reach someone who doesn’t use Aster while keeping the message encrypted, see Send an encrypted message to anyone.
The recipient’s keys are out of date
The error says the recipient hasn’t published post-quantum keys, or is missing the keys needed to read the message. Ask them to open Aster on any device or update their app, and then send again.
The message was written offline
A message you write offline is queued and sent when the connection returns. If the queue fails, Aster tells you that an email written offline couldn’t be sent. Open Drafts, reopen the message, and send it again.
The send fails with no clear reason
- Check your connection, and reload the app.
- Confirm the recipient address is spelled correctly. A single wrong character produces a bounce rather than a delivery.
- Try again in a moment. A server error clears on its own, and your draft is saved.
The message sent but bounced back
The message left Aster and the receiving server rejected it. Open the bounce message to read the reason, which usually names a wrong address, a full mailbox, or a policy on the receiving side. Correct the address, and send again.
A scheduled message didn’t go out
Open Scheduled. A message that failed at its send time stays there with an error, and you can reschedule or send it now. See Schedule and snooze mail.
Related articles
Was this article helpful?