This revised proposal for a Feature Request is the result of my desire to implement quotas, but not have the attendant headaches that inevitably accompany its implementation.
<snip>
Ok, seems there is no interest in doing this - and I do understand the objections... but how about a more consistent method for handling over quota conditions?
This could be as simple as:
*** 1. Make dovecot aware of and use a special 'Quota Status' message that it uses to inform a user that they are over quota. This message should be able to be customized, with variables (like, for example, it should list the messages that are bounced - including, optionally, the Subject, the sender, date/time, etc - as well as provide general quota information (ie, how close to or over quota they are, and how much they'd need to delete or move to Local Folders to get back below a certain level (again, configurable)), and lastly, any custom information the System Admin wanted to provide - like, maybe, specific instructions for how to move messages to Local Folders, how to request additional storage allowance, etc.
*** 2. When user goes over quota, update the Quota Status message and move it to the Inbox.
*** 3. While the user is over quota, every time a message to them is bounced, update the Quota Status message with the new information (append the details of the message just bounced, so they will have a complete list of messages that were bounced while they were over quota).
Hmmm... I think I like this idea much better anyway...
--
Best regards,
Charles