As a hosting provider, I would like the ability to set a limit on the lifetime of email messages (deleting after a certain number of days that I specify) so that I don’t have to manually delete emails for customers who have exceeded their quota due to too much mail.
Clients who use e-mail accounts created via cPanel are often not very sure on how to setup up their e-mail clients correctly. This is made worse by the fact that there are so many different e-mail clients available, often with a client user more than one (due to different devices reading the same e-mail account).
Setting up accounts at all is often troublesome, but even for those that manage nearly all clients in my experience (over 10 years) fail to adjust their settings so that read e-mails are deleted from the server after a given period of time. Often a mobile e-mail client wont even have that option. Desktop clients rarely have that option for sent items, only the inbox is maintained.
The net result of this is I routinely have clients using up their mailbox quotas. This means e-mails bounce and things are disrupted for their business. I then have to increase their quota or try and teach them about mailbox management (which never works). I can't keep increasing quotas as clients are now getting large mailboxes that are filling up the entire server.
At the moment the only other alternative is to talk to the client and discuss what e-mails can be deleted, and then I have to go and do this for them on cPanel using the Dovecot rules.
When this problem is repeated across an entire client base I end up losing many hours myself as well the issue the client has with not receiving e-mails.
All I need is a single rule for all mailboxes that I can pass on to clients that is clear and understandable i.e messages over X months will be deleted. This would apply to sent and inbox folders. Ideally this would be a global setting on WHM, if that is not possible then it could be set via the cPanel.
The current arrangement is chaotic and unprofessional, it leads to uncertainty and impacts on the bottom line. I hope something like this can be implemented very soon.