Here is a list of articles that I setup for email hosting for a friend of mine. She hosts for a couple of different people. The first one is the one I used because it was for Debian and the system being used was Ubuntu, a Debian derivative. The second one is for gentoo. I included it for completeness and also using Courier. I'm not to happy with Courier, but it still works the same.

http://workaround.org/articles/ispmail-etch/

http://www.gentoo.org/doc/en/virt-mail-howto.xml

(From Samir's blog)
dev notes:

language of choice atm is C++.
need support for mysql/postgres/sqlite (maybe)
possible solutions: SOCI: http://soci.sourceforge.net/
QT4 (no point doing qt3)
gtkmm (ie. gtk+)
wxwidgets

For the backend C++ is the very obvious choice. I agree with that. I was looking at SOCI and that does look like it will do what we need. Abstraction of the DB languages, that way we just say what backends are used. I also dont think that doing any sql parsing on the sensors would be a good idea.

sloggerd
1) Stable with MySQL, Postgress, and Oracle.
2) detect loss of database connection and re-establish with out loss of data
3) Work properly with multiple daemons on one server
4) Single server to handel multiple servers.
5) Good logging of statics
6) mailing of alerts to specified address for a specific time frame.
7) Good debugging logging

Sensord
1) Able to start at any time.
2) Detect is snort dies and alert on it.
3) Able to log to multiple sloggerd's
4) Detect if it losses connection to sloggerd and reconnect

At this time I am announcing a new project that I am starting. I am calling it Snort/SQL logger, or slogger.
This is a fork of the FLoP project.

The main reason I have decided to do this fork is several fold, and to address several issues that I have found with FLoP.

1. FLoP is unreliable and requires it to start up at a specific time in the snort, and is problematic with stability.
2. The naming of the Sensor and the Database programs are badly named and easily confused.

I have fixed the login issue to the site. I missed a patch when I was updating drupal.