quotawarn IMAP response status

[Scott Russell]

On Fri, 2003-04-18 at 23:07, Scott Russell wrote:
> Greets.
> 
> I noticed that Cyrus IMAPd v2.1.11 appears to set the wrong response
> status for mailboxes over the quotawarn value in imapd.conf

Hmm, silence :) Did I ask a stupid question or touch upon an old debate?
Or is this one of those things that could go either way and is open for
interpretation?

> Looking at rfc2060 section 7.1.1 it says that:
> 
>   The OK response indicates an information message from the server.
>   When tagged, it indicates successful completion of the associated
>   command.
> 
> The following section of a protocol trace shows Cyrus sending "* NO
> [ALERT]" for what appears to be a "successful completion of the
> associated command".
> 
>   <1050718642<B00006 LIST "" INBOX
>   >1050718642>* LIST (\Noinferiors) "." "INBOX"
>   B00006 OK Completed (0.000 secs 2 calls)
>   <1050718642<B00007 SELECT INBOX
>   >1050718642>* FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
>   * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)]  
>   * 16 EXISTS
>   * 0 RECENT
>   * OK [UNSEEN 2]  
>   * OK [UIDVALIDITY 1050717092]  
>   * OK [UIDNEXT 18]  
>   * NO [ALERT] Mailbox is at 96% of quota
>   B00007 OK [READ-WRITE] Completed
>   <1050718642<B00008 FETCH 16 UID
>   >1050718642>* 16 FETCH (UID 17)
>   B00008 OK Completed
> 
> Shouldn't the quotawarn, and even over quota ALERT response codes be
> using an OK status response unless the command actually fails?

-- 
Scott Russell <lnxgeek at us.ibm.com>
IBM Linux Technology Center