Hi, On Wed, 24 Mar 2004 15:50:27 -0500, Paul Jarc <[EMAIL PROTECTED]> wrote... > Mark Crispin <[EMAIL PROTECTED]> wrote: > > RFC 3501, section 6.4.5, page 54: > > Most data items, identified in the formal syntax under the > > msg-att-static rule, are static and MUST NOT change for any > > particular message. Other data items, identified in the formal > > syntax under the msg-att-dynamic rule, MAY change, either as a > > result of a STORE command or due to external events. > > So if the server at one time gives a value for a particular static > data item, and at a later time does not give a value at all, not even > NIL, then you call this a change of the data item? That isn't at all > clear to me from the text of the RFC. > > > This specifically outlaws the scenarios of: > > a1 FETCH 1 RFC822.TEXT > > * 1 FETCH RFC822.TEXT "foo" > > a1 OK done! > > a2 FETCH 1 RFC822.TEXT > > * 1 FETCH RFC822.TEXT NIL > > a2 OK done! > > I agree on this one.
Messages disappearing out from under your IMAP server is this kind of scenario. The server is in a situation where it can not respond because it has a request for a message with a pending expunge notification and the data is non-existant or someother reason why it is unable to return the requested data. Returning a response, different from a possible previous request or possible subsequent response is also not permitted. What are the options? NO or BYE. NO would be nice if clients took NO as "please do NOOP" and doing a NOOP would change the situation to one where the FETCH would succeed or the FETCH is no longer necessary; however, clients don't typically expect NO from a FETCH and most do not do NOOP. NO has also been reported to cause certain widely used clients to die horribly or behave obnoxiously so it is unfortunately not a reasonable (read as an interoperable) option unless you like getting lots of mail requesting that you fix your server. Not everyone agrees that sending a NOOP is the best client practice for NO responses to FETCH because the client can't know that NOOP will fix the cause for the NO response. That leaves BYE. The number you have dailed, 123-555-1111, has been disconnected or is no longer in service. Please hang up and try your call again. Some people will hang up and then press redial. Regards, Mark Keasling <[EMAIL PROTECTED]>
