Hello, I don't know if this is even news to you probably not, dbmail ships now with an sqlite back end option.
I really like the idea of using sqlite as the backend but I am trying to get them to make a modification so I took it on my self to do the research for it to make it easier on them if at all possible. Here I go: The sqlite backend right now works the same way as mysql and the pgsql backend. Meaning all data in one db. What I would like is to have a sqlite db file per user. This would have many advantages like easy backup on a per user base. No reader/writer lock concerns Better security since each user would have access only to there own db. Faster data access since data is stored in small chunks. etc etc. The challenge: There is data like email aliases which need to be accessed by the MTA. It wouldn't be a good idea to open each users db to check the aliases for each email that arrives. So what we would need is a common db which mirrors one table from all the user databases. The dbmail guys suggest to use ldap, witch is already in existence and could probably be easy modified to do this. However I don't like the idea of having one more component specially ldap. So how could this be done with sqlite only is the question. Thanks Demi
