Peter Goerzen writes:
Sam Varshavchik wrote:There may not be apparent problems with quota-reporting itself, but filesystem-enforced quotas are generally problematic. When a mailbox goes over its quota and the IMAP server begins reporting errors from ordinary filesystem operations, many poorly-written IMAP clients will keel over, and, pretty much, lock the user out completely.Filesystem quotas are not recommended.Hi Sam,Thanks for the reply, but I'm a little confused. I find two places at courier-mta.org that recommend the use of filesystem quotas whenever possible:http://www.courier-mta.org/imap/README.maildirquota.html http://www.courier-mta.org/maildirquota.html Is this recommendation obsoleted?
Yes, thanks for bringing this to my attention. When maildirquotas were new, this might've been applicable, but now that the logic is fairly mature, this needs to change.
Intelligent filesystem quota implementation can mitigate client-side issues. Soft quotas give users the time they need to clean up before hitting the hard quota (my patch reports the soft quota). Once the hard quota is reached, the quota can be extended temporarily. The "locking out" you describe is not entirely undesirable in every situation, as it provides cause for administrative pressure to reduce disk usage ;-)
Fair enough.
pgpP4X3mWy9Ut.pgp
Description: PGP signature
------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
