Re: [imap5] Standardized error messages

Timo Sirainen writes:
> On Oct 21, 2008, at 8:27 PM, Peter Mogensen wrote:
>>>  and draft-gulbrandsen-imap-response-codes, and see what you think.
>>
>>  Better... although I'm not sure it's a good idea to merge error-
>>  codes and status info (like UNSEEN,UIDNEXT...) into the same
>>  namespace.
>
> Hmm. Wonder if this causes problems.

It does, but that problem is one we have already and it hasn't been THAT 
painful:

        REFERRAL             RFC 2221
        ALERT                RFC 3501
        BADCHARSET           RFC 3501
        PARSE                RFC 3501
        PERMANENTFLAGS       RFC 3501
        READ-ONLY            RFC 3501
        READ-WRITE           RFC 3501
        TRYCREATE            RFC 3501
        UIDNEXT              RFC 3501
        UIDVALIDITY          RFC 3501
        UNSEEN               RFC 3501
        UNKNOWN-CTE          RFC 3516
        UIDNOTSTICKY         RFC 4315
        APPENDUID            RFC 4315
        COPYUID              RFC 4315
        URLMECH              RFC 4467
        TOOBIG               RFC 4469
        BADURL               RFC 4469
        HIGHESTMODSEQ        RFC 4551
        NOMODSEQ             RFC 4551
        MODIFIED             RFC 4551
        COMPRESSIONACTIVE    RFC 4978
        CLOSED               RFC 5162
        BADCOMPARATOR        RFC 5255
        ANNOTATE TOOBIG      RFC 5257
        ANNOTATE TOOMANY     RFC 5257
        ANNOTATIONS          RFC 5257

I've run into a case where I wanted to return two things (UIDNEXT and an 
error? can't remember).

> For example [EXPUNGEISSUED] can't be returned for a STORE 
> UNCHANGEDSINCE that returns [CHANGEDSINCE].
> Perhaps there are other similar issues. But maybe they don't matter.

I think they matter in principle, but generally you IMAP doesn't both 
return an error and do something at the same time.

Arnt
_______________________________________________
imap5 mailing list
imap5@ietf.org
https://www.ietf.org/mailman/listinfo/imap5