0. Attachments usability
If attachments are not "straight" attachments, but are instead wrapped
within a composite which itself is the attachment, user needs to navigate
twice : once to open the composite, and then again for the individual
attachment. 
Try to program a work-around.

0.1 Huge Inboxes
There seems to be a problem when user displays more than 100 messages in 
INBOX, regarding refreshing. There may be an issue related either to
backend (imap) cacheing, or to JavaMail fetching mechanisms. 
Need to investigate further.

1. Backend management: folder store
Old confs in imap store are not always deleted. They are marked as deleted,
but the expunge does not always work - I do not know why as yet

2. Backend error handling

2.1 timeout not well handled
When the IMAP backend is gone (timed out, or killed), but the Websession is still active,
the error is not nicely handled.
-> need to add some logic to generalexception.xml, parsing the exception for the imap close
stuff (it's an IOException).
-> or, if we notice IMAP is gone, try to reopen it ? 
Try to reproduce this by killing the imapdaemon when session is active

2.2 when sending mails
When backend refuses to send a mail, the error message is not clear
Example: sending a mail when from is set to a non-locally accepted domain
such as on nawak, @www.nawak-online.org
Exim refuses to send mail, but we do not see the real reason in IronMailer

2.3 when losing mailbox locks (for instance when other client opens the same
  mailbox)
error handling must become nicer

3. Refresh mechanism
Flo says:
"Du schickst dir eine neue Mail. Dann drückst du auf
INBOX und auf den Refresh-Button im rechten Frame. Dann
drückst du auf die Nachricht. Nun
drückst du auf den Refresh-Button im oberen
Frame. Somit wird das Flag von neu auf gelesen gesetzt, du hast aber immer
noch eine Instanz von der neuen Nachricht. Nun
drückst du auf Antworten und es knallt."

4. Folder hierarchies
There seems to be a problem when creating several depths of folders -
need to investigate !

10. Handling of non-standard messages (for instance, a Powerpoint-message without text body
and without Multipart wrap): a work-around exists to display these as a message with an
attachment, however the attachment can be downloaded only once (after which the stream
is consumed and can't be recreated)

11. Deploy  mechanism
Provide "nice" ant deploy mechanisms, configurable through properties file for locations

