Things that need to be worked:

* Allow gyrus to get notificated when the server sends a "BYE LOGOUT" message.
  Then the application must get logged out. 

  Speaking more generally, gyrus is not able to cleanly finish a connection
  when this is closed by the server. You can realize of this if you connect
  gyrus to your local imap server and kill the connection with the 'kill'
  command.

* Rewrite the gyrus-session.[ch] API to make it clearer. I suggest to use 
  GObject to get a 'nice' piece of work. If possible, do not modify the 
  interface with the rest of the application. I don't think it's necesary.

* Change the error handling (currently it only uses gchar**) to GError.

* Separate the client side of GyrusAdmin and make a GyrusImapClient object, 
  that should be totally GTK+ independient (i.e., only must depend of GLib and
  GNet libraries). Then, make GyrusImapClient an aggregated class of 
  GyrusAdmin.

  What do we win with that? well, GyrusImapClient can be the beginning of a 
  C library to work with mail servers. I don't really know how evolution and
  other GNOME mail software establish connections and work with mail servers, 
  but i think that creating an gyrus independient library (i don't know, maybe 
  we can call it libgyrus) gyrus can be more easily extensible than it is right
  now.

* Right now the report module for users overquota is slow. It needs a little 
  of love, as I think that it can get faster.
    
New Nice Features:

* Orfaned mailboxes dealing. Mailboxes usually get orfaned when some
  poor quality software deletes only a parent mailbox, leaving the children 
  ones in the server. Many applications do not get notification of this, 
  so these orfaned mailboxes get unaccesible.

  A nice feature would be to get a list of orfaned mailbox so the administrator
  can decide what to do with them. Currently gyrus ignores the orfaned mailbox,
  so the administrator doesn't know of its existence, at least by gyrus.
