On 2.8.2013, at 19.18, Richard Platel wrote:
>> I'm not exactly sure what you thought of, but my idea was simply that you'd
>> add your own dict proxy in the middle which hooks into the GET command, and
>> increases its value by reading the filestoresize. You can already do that by
>> pointing
On 2013-08-02, at 12:05 PM, Timo Sirainen wrote:
> On 2.8.2013, at 18.56, Richard Platel wrote:
>
>> On 2013-08-02, at 11:34 AM, Timo Sirainen wrote:
>>
>>> On 2.8.2013, at 18.15, Richard Platel wrote:
>>>
We pass custom quota rules for each user in our userdb, and use a custom
On 2.8.2013, at 18.56, Richard Platel wrote:
> On 2013-08-02, at 11:34 AM, Timo Sirainen wrote:
>
>> On 2.8.2013, at 18.15, Richard Platel wrote:
>>
>>> We pass custom quota rules for each user in our userdb, and use a custom
>>> dict proxy program, so that program could read the file and pa
On 2013-08-02, at 11:34 AM, Timo Sirainen wrote:
> On 2.8.2013, at 18.15, Richard Platel wrote:
>
>> We pass custom quota rules for each user in our userdb, and use a custom
>> dict proxy program, so that program could read the file and pass a setting
>> at log in time too (if, for example,
On 2.8.2013, at 18.15, Richard Platel wrote:
> We have a weird quota requirement, we have file storage that we manage
> through our own APIs but want that usage to come out of the user's mail quota.
I've been thinking something like that as well for various other things: IMAP
METADATA/ANNOTATE
