> Why do you think the gmail's behavior breaks standard compliance? For > me, it looks as in there was an system process concurrently attached to > the mailbox that sends periodically EXPUNGE commands. Can you please > point out to the part of the standard that is not obeyed?
Regardless of whether or not some other system process issued an EXPUNGE command, the EXPUNGE has not been announced in the session. Only inferior, poorly-designed servers fail to keep message data available to the session in that case. Even more important is the fact that Gmail does this automatic expunging when the \Deleted flag is set at all. This is in complete defiance of the entire point of the delete-expunge model, and breaks the user's option of undeleting. This is the same company that asserts that it has the legal and moral right to collect, copy, and archive any data that it can electronically access, without even the formality of a polite note to the owner of that data or the individuals referenced in that data. Yet, when it comes to personal email messages, they aggressively purge these from the user's IMAP INBOX. Yes, I know about the place where they hide the messages away. That doesn't matter. The whole point of standards is not to have every implementation doing its own idiosyncratic thing. _________________________________________________________________ You live life beyond your PC. So now Windows goes beyond your PC. http://clk.atdmt.com/MRT/go/115298556/direct/01/_______________________________________________ Imap-uw mailing list [email protected] http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
