A consultant used a single mailbox on her hosting plan for several years and never deleted anything. Every proposal, every invoice, every forwarded newsletter and every PDF of a signed form stayed where it landed. Attachments accumulated until the mailbox reached its quota.
From then on, incoming mail bounced with a polite error message. A client who was preparing to sign a contract received the bounce and, after two attempts, assumed the consultant had stopped working. The contract went elsewhere.
She now archives mail yearly, and has alerts at eighty percent of quota. The story is a composite, but support teams meet versions of it every month, usually from someone who found out from a third party rather than from the system.
How a mailbox fills without anyone noticing
Nothing about a mailbox changes as it fills. It opens at the same speed, the unread count looks the same, and sending mail carries on working. A quota is a limit on what is stored on the server, not on what you send. So for years the consultant saw no symptom at all.
The growth was steady rather than dramatic. A consulting practice trades in documents: reports, slide decks, scanned contracts, photos of whiteboards. One attachment of four megabytes is nothing. Eight hundred of them is a problem. Email also inflates attachments, because binary files are encoded as text for transport, which adds roughly a third to their size. A 3 MB PDF becomes about 4 MB in the mailbox.
Her plan gave each mailbox a modest quota, a figure typical of entry-level hosting, and it was shared between the inbox, the sent folder, drafts, the archive folder she had made and the trash. The trash is the one people forget: deleted mail often sits in it, still counted, until it is emptied or expires.
What the sender sees when it bounces
When the mailbox is over quota, the receiving server refuses new messages. How it refuses depends on the software. Some servers answer with a temporary failure, a 4xx code such as 452 4.2.2 Mailbox full, and the sender's server keeps retrying for a day or more before giving up. Others answer with a permanent failure, a 5xx code such as 552 5.2.2 Quota exceeded, and the sender is told immediately.
In both cases the sender gets a message from their own mail system, usually from a name such as Mail Delivery Subsystem, with text like this:
Your message to [email protected] could not be delivered.
Reason: 552 5.2.2 Mailbox full / quota exceeded
No further attempts will be made.The person on the other end sees the bounce, not the consultant. If they are a technical person they will recognise it for what it is. If they are a busy client with a contract to sign they will see an error from a robot, and a robot saying the mailbox is full sounds a lot like "this person is no longer here". That is the psychological centre of this story. The consultant lost the contract because the failure was visible to everyone except her.
Two attempts and a silence
The client was ready to sign. They wrote with some final questions about the scope, and the message bounced. They tried again later that day, in case it was a glitch, and it bounced again. The client had no other address, no phone number to hand, and there was a deadline to set up the project. Rather than go hunting, they asked a second consultant who had been on the shortlist and who answered within the hour.
The consultant meanwhile was waiting for a reply that she did not know was being sent. Three days later she wrote to chase and got an answer that politely thanked her and said they had gone another way. Only then did she ask a colleague to send a test message, which bounced.
Two wrong turns followed. She first suspected a problem with the domain and spent an afternoon on DNS settings, which were fine. Then she suspected spam filtering, because a message from the client had never arrived, and she asked the host whether her address had been blacklisted. Support looked at the account and answered in one line: the mailbox is at 100 percent of its quota.
The fix, step by step
The repair is quick, though it is worth doing in the right order so nothing is lost.
- Log in to the hosting control panel and find the email accounts page. It lists each mailbox with used and total space. Confirm which one is full.
- Raise the quota temporarily if the plan allows it. This stops the bouncing straight away and gives room to work.
- Connect with a desktop or phone mail client over IMAP, and sort the folders by size. The sent folder and the trash are the usual culprits.
- Copy older mail to a local archive folder on your own computer, or to a separate archive mailbox, before deleting it from the server. Check the copy opens.
- Empty the trash and the junk folder, then compact the mailbox if your client offers it.
- Check the new figure in the control panel, then send yourself a test from another address.
Mail that bounced with a permanent error is not coming back. The consultant wrote to every client she could remember, apologised for the delay and asked them to resend anything from the previous three weeks. A few did.
The new routine
She now archives mail yearly. Everything older than twelve months moves out of the live mailbox into a local archive, which is backed up with her other files. Large attachments are saved into a document store, such as a shared drive, and the email keeps only a link or is deleted. Alerts are set at eighty percent of quota, so a warning arrives while there is still room to act.
She also changed one habit that had nothing to do with tools. Her email signature now carries her mobile number, so a client who sees a bounce has somewhere else to go. It cost nothing, and it would have saved the contract in this story. The quarterly review of her accounts, which used to cover invoices only, now includes a glance at the mailbox figure in the panel.
| Approach | Good for | Drawback |
|---|---|---|
| Yearly archive to local storage | Single user, modest mail | Needs a backup of the archive |
| Higher quota or bigger plan | Buying time | Delays the problem; the mailbox still fills |
| Attachments saved to a document store | Heavy attachment traffic | Needs a habit and a naming scheme |
| Separate archive mailbox | Searching old mail from anywhere | Counts against account storage |
Look at your own configuration
Look at the control panel's email page first. It shows the quota and usage for each mailbox, and on many hosts you can set a warning threshold there. If you have shell access to a VPS running Dovecot, you can ask it directly:
doveadm quota get -u [email protected]To test the bounce path without waiting for a client, send a message to the address from a separate account, such as a webmail address, and see whether it arrives. Do this monthly. The troubleshooting guide has a section on email delivery problems if the result is not what you expect.
Common questions
Does deleting mail free space straight away?
Not always. Deleted messages usually move to a trash folder that still counts, and some clients only flag mail as deleted until you purge it. Empty the trash and check the figure in the panel.
Will the sender be told to try again later?
Sometimes. A temporary failure makes the sender's server retry for days, so some mail arrives once you clear space. A permanent failure does not, and the message is gone.
Is a bigger quota the answer?
It buys time. Without a habit of archiving, the mailbox fills again, only later and with more mail to tidy.
Do forwarders and aliases count?
A forwarder stores nothing, so it adds no space. A forwarder pointing at a full mailbox will still bounce, however, which catches people out.
What would have caught it
- Check mailbox quotas and set alerts, at eighty percent or lower.
- Move old mail to an archive each year, and confirm the archive is backed up.
- Keep attachments out of the mailbox where possible, by saving them to a document store.
- Send a test message to every business address from an outside account once a month.
- Give clients a second way to reach you, such as a phone number in your signature.