[ 
https://issues.apache.org/jira/browse/PROTOCOLS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit closed PROTOCOLS-109.
------------------------------------
    Resolution: Invalid

Command directly supported threw mailbox managers.

> Quota support for Append, copy and move IMAP commands
> -----------------------------------------------------
>
>                 Key: PROTOCOLS-109
>                 URL: https://issues.apache.org/jira/browse/PROTOCOLS-109
>             Project: James Protocols
>          Issue Type: New Feature
>            Reporter: Tellier Benoit
>            Assignee: Eric Charles
>
> I think it would be nice to have IMAP command that may increase the size of a 
> mailbox to check quotas.
> I listed those commands : 
>   - APPEND
>   - COPY
>   - MOVE
> I already implemented some stuff in the COPY processor :
>   - before copying anything, I check quotas
>   - I compute the total size of the moved messages
>   - I get the quota for the targetted mailbox
>   - Check the quota by adding the total size of moved messages to the target 
> mailbox quota and check it.
>   - If it is OK then messages are moved
>   - If not, I think no message should be moved ( RFC 3501 : if it fails, 
> nothing should have been done )
> Something similar can be achieved with the move commands.
> Problems appears with the Append command : we can not get the size of a 
> stream, and I do not believe ( or even trust ) that the clients sends the 
> size of the message with the command... So there is two solutions :
>   - Get the full message and calculates his size, and add it to the store if 
> quotas are OK
>   - Normally append the message end check quota afterwards. Delete the 
> messages if quotas are not OK. I think I would prefer this solution.
> What do you think ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to