I had created a mailbox for a customer.
Some time later I was asked to add a forward to a second personal address which was available on a phone. It wasn’t possible to always collect from the established mailbox.
The user found that he predominately used the secondary account and with little or no use of a computer to connect to mailbox. The original domain mailbox was all-but forgotten!
Some time later it was reported that incoming emails were bouncing, unable to be received. On investigation the mailbox was found to be full.
The emails stop being received because the master mailbox was full and were therefore being rejected
The customer had stopped logging into the mailbox to handle the emails, managing those required, deleting the unnecessary ones, and saving to local folders those to be preserved.
For incoming emails the action order was:
- Deliver to mailbox
- send forwarded email
The consequence of this was that once the mailbox had filled up it was returning a mailbox full/ unable to receive email error. The forwarding of the email was not actioned as the error had been encountered first.
Delivery of emails to the mailbox were being actioned first. With a full mailbox this caused the process flow to abort with the error response being attended to.
It was recommended to periodically connect to the mailbox from a computer to manage emails: deleting and saving in local folders. Thus keeping the emails in the mailbox to a minimum.
