Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Ok, this is an RFE I guess, not a bug.  Why not allow imap servers to store
*all* kinds of data.  I've never understood why all of these email utils
that encapsulate calendar and appointment data into email messages already
(ie evolution, starfish, outlook netfolders), don't also allow using an
imap server as the data store for their calendar/task/contact data.  It's
especially frustrating on Exchange, when you can connect with an imap
client and *see* the notes, contacts, appointments, etc as messages - the
client just isn't written to interprete them.

Why not encapsulate everything you want into the actual messages.  It
wouldn't give great performance immediately, but after caching locally
(which you already do for indexing email), performance would be fine.  It
would enable server-based calendaring.  I don't see why it would require
modifications to the actual server.  Just encapsulate the data.  Then turn
around and publish your spec for encapsulating the data (but don't get
bogged down in that process, just publish the code) and everyone else will
pick it up.  *That's* your MSExchange-killer!

Steps to reproduce the problem:
1. N/A
2. 
3. 

Actual Results:
Can't create a "calendar" type of folder on an imap server.

Expected Results:
Can create *any* type of folder on an imap server, even one where the data
is stored on the remote server but is useless unless the client has extra
code to interpret the encapsulated data.

How often does this happen? 
N/A

Additional Information: