move db config to defaults.conf

wrap headers that are too long (break on commas, or 80 chars if needed)
add <META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=utf-8"> in the headers when displaying with mswordview
refresh cookies so they don't expire when you're active in a session - make sure that composed email is not lost
add an option to view a message (or an attachment) with an arbitrary MIME handler (ie, html, mswordview, whatever)

possible reason for regex problems: using system library instead of php regex

trash folder?
cancel message option

screen addressbook data better (addslashes()?)

allow selection of the ispell dictionary

config option for where imp is on the filesystem, to replace all of the ./'s...

add option for having message viewing, folders, etc take place in seperate
windows... also make sure it's a config option

add patches...

/ - terminate $default->root_url, make these changes all over
note that root_url needs to be / terminated
add a warning that cookies won't work right if one copy of imp is inside a
dir that another is in

config option for caching of mailbox pages

allow user to pick color schemes. find a way to store several default ones. (style sheets?)
allow specification of a list of allowable servers (instead of just one - create a popup on the fly)
allow filtering of outgoing addresses - ie, can only send mail to a limited range
config option to turn off folders completely

add resume of postponed messages - also in sent-mail folder, show the to: address instead of from: ...

mailbox sorting (imap_sort!)
filters (procmailrc generation?)
save selected messages between pages of a mailbox
printing-friendly display option
possibly integrate print.php3/html2ps for generating postscript...
allow import/export of addressbook in various formats (pine, mutt, eudora, etc...)

ZeroDiVide:
--- [ Projects ] ---- ( There is no particular order in which these get done )
1.  Database Intergration ( ImpDb ) -> *HordeDb [ aka v2 database ].
   a. login ... database auth works... make the autocreate code work
   b. skeleton user support, also allow for multiple skeletons. ( THESE CANNOT LOGIN, and get a Skeleton_* prefix )
   c. Add object grant system
   d. Add the addressbook / contact management code ( Troll ).
   e. Perl script to migrate the v1 database into the v2 format.
   f. Migrate into live source for testing.
   e. dummy database driver ( also usable as a template ).
   g. password file migration / sync ( Whee enc passwds ).
   h. Deleting users                - May push off for a while.
   i. Management Security roles
   j. Unix Account Management code. Intergrate the code ( uses a perl backer for security reasons )
2. Contact management ( Troll )
3. File management ( Gollum )
4. Improve folders interface ( folder management )
--- [ Random Thoughts / Notes ] --- ( So I dont forget to do something )
Database :
   Add the ability to configure cascading passwords to the db.
   horde username / pass -> imap user name / pass without user
   changing anything.
   
Database stored server configurations : 
   This is a idea that i kicked around about storing all of the
   configuration of the imp system within an actual database.  It seems to
   hold up until you have a VERY large ammount of users tagging the imp
   system which in change is tagging the database everytime for a config.

   The solutions :
   1. To have a user runnable configfile creator, that when ran scoops out the
      config file stuff from the database and creates a configuration file.
   2. Store the configuration file in the database, seperately from the rest
      of the tables. This made a big improvement on the max users concurent.
      I think if someone tweaked their system and tweaked their database
      it should be possible to run a 1000+ concurrent user imp system on
      a on-the-fly config.

   There should be a configurable setting to allow certain parts of the configuration
   to change dynamically. ( More on this later ).

mpb:
Fix decoding of MIME headers *again* (got some test data that breaks the current implementation)
Work on encoding of messages that are being sent (currently proclaims to be 7bit only, but passes 8bit chars).
Do some work on internationalization.
