>>> 2) This is an actual IMAP thing, but rarely used: The ability to publish or >>> subscribe to folders, and the ability to unsubscribe to folders in your own >>> store you don't care about. >> >> Account-local un/subscriptions have been considered and I don't think they'd >> be much trouble to support. Although if the source list is customizable, why >> do you care what you're subscribed to or not? > > Because there's a difference between not seeing a folder and not talking to > it at all. > >> >> I guess there's some IMAP extension that lets you get notifications for all >> your subscriptions at once, instead of a single mailbox? That would justify >> giving it attention. >> >> As for publishing, totally 2.0. Can you make a good case for it? > > As a really edge-case IMAP user, definitely. In fact, it's one of the bigger > reasons cited for things like outlook. They use a different name: Public > Folders. For collaboration, the ability to have a mail folder, or many > folders that people can publish, and or subscribe to is not minor. Yes, I > know Google Wave. The problem is, stuff like Wave requires you to pretty > much replace email with their client. For an email client, IMAP > subscriptions are the way to go, since most servers, (well, not Google's but > theirs sucks anyway) support it. > > Unfortunately, it's one of those things you have to use to really get.
Are you saying that IMAP supports some method of having shared folders that anyone can read/write to? Or have I misread you? I thought IMAP subscribe was simply to request that certain folders you created were given prominent position in the UI, rather than allowing any sharing between users. _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
