Vexim3 Requirements

From Veximwiki

• Tight integration with DSPAM (ditch spamassassin? make it optional?)

 - The current (perl) DSPAM UI is horrible. In fact, in many situations
   it is totally broken! We would have to write our own simple UI,
   which would actally be a good thing, as it would make vexim look
   better intregrated.
 - DSPAM is GPL and we are BSD licensed. We'll need to bundle DSPAM
   with vexim, and have it set up in a very specific way, this will
   need clear documentation. The licenses are compatible enough that I
   think this won't be a problem. We won't be using DSPAM code inside
   vexim code so we won't have to convert licenses.
 - (The above was written a while ago, and I'd like to see it expanded more generally to "other anti-spam solutions", including SpamBouncer, and TrafficControl.)

• Use of a good web framework

 - No more writing everything from scratch, and no more database
   incompatibilities, or hours of database debugging to get the SQL
   "just right".
 - This will allow (hopefully) faster development too.

• Store more exim configuration data in vexim database

 - Possibly find some way to use memcached with Exim to lower the load
   on the DB for high-use sites; someone will need to modify the exim
   source code to do that.

• Store user data in LDAP

 - Some admins like to use LDAP, they should be able to store the user
   data there.

• Make vexim work with other MTAs (postfix for sure)

 - This would increase our exposure and allow more people to run vexim.
   There's nothing preventing this working today - but having example configurations would be good.

• Integrate user patches

 - http://www.schirmacher.de/display/INFO/improved+Vexim+frontend+and+bug+fixes

• Archiving

 - Add the ability to "copy" user's inbound, outbound, or both to a specified destination or mailbox.
   Exim has the unseen_deliver option, but a nice way to enable certain users to have this option.

• Config file editing

 - Enable editing of config files via web interface, use includes from web accessible are to make
   adding minor changes and tweaks simpler for a shared hosting environmant, possibly store sections 
   of the exim config in a database (MySQL or LDAP) and enable turning them on/off with a simple 
   checkbox control.

• Password recovery option

 - enable clients to recover/reset passwords somehow. (emailing isn't really an option, but we can think of something I'm sure)

• Mailing list integration

 - Integrate real virtual mailing list management, enabling lists to have the same name for different virtual domains
 - Web interface / API to mailing list membership

• Fix the UI

 - find some interface designers guru and talk to him about how horible it is and how to make it pleasant to use. :)