Hi, in the best tradion of what is to be in the core specs and what should be an extention, please consider this:
> > One addition would then be the part of an "extension": A command to supply a > > list of folders which it wants to receive untagged STATUS updates about. > > > > Wouldn't that be a really simple solution? Conforming? Rather easy to > > implement on both client and server? > > STATUS is not necessarily an inexpensive operation. So what? A server for which it is "expensive" to do this status update - don't advertise it in your CAPABILITY and you need not bother coding it. Right? Even if you advertise it and for a certain folder it is to expensive, give a NO response. You are fine with the specs. > If you want a widely deployed new-mail notification system, you need to > reduce it to what is really needed and can be globally implemented at low > cost, as opposed to what you may be able to do on some implementation. Needed: Notification of new mail arrival in unselected mailboxes Solution: a) See above (my idea) or b) A better idea (fine!) or c) Ignore it because it MIGHT be to costly or MIGHT not be possible on all systems. Please don't vote for c. If no one else needs it, fine, drop the idea. If the vast majority says "too difficult for me, don't make it a suggested behavior", fine, drop it. But it some say "hey, this could be a cool thing to have", let's talk about it, ok? > If you have the attitude that it must be the big thing or nothing at all, > then what you will get is nothing at all. Great attitude. I stick with another: "You never know until you really tried". Christof
