Timo Sirainen wrote: > On Thu, 2008-09-25 at 09:40 -0700, Seth Mattinen wrote: >> Has anyone (is anyone) working on adding quota support to dovecot's >> managesieve server? I was thinking about giving it a shot myself and I'd >> hate to duplicate work. It would be something very basic like a max >> bytes setting and the total sieve storage per user isn't allowed to >> exceed it. > > I think it would be nice to be able to use the standard quota plugin > with managesieve so that all the same backends and configuration could > be used. The main problem I see is: > > Does anyone want (or need) to have the mail and sieve quota shared, > instead of specifying separate limits for them? > > With shared quota the code will probably have to have some kind of sieve > hardcoding or write some kind of state files so it knows where to look > when recalculating quota. So preferrably no-one needs this. :) > > So without shared quota they could be configured as "sievestorage" and > "sievefiles" which would also be visible using IMAP quota commands. > Configuration could go like: > > quota = dict:::proxy::quota > quota_rule = *:storage=100M:sievestorage=1M:sievefiles=10
No need for sharing from me. (In fact, I don't use mail quotas at all.) My only goal is to have some kind of sieve quota to prevent someone from filling the filesystem with garbage either intentionally or through a baldy written client. ~Seth
