On Freitag 26 Juni 2009 Paul J Stevens wrote: > Even we do very much the same in our main installation, we use LDAP > to extend the user model, so the extra tables would be redundant for > us. Also, I fail to understand how the additional tables effect > dbmail internals. My business logic builds on ldap, and doesn't > require any tweaking of the dbmail code or tables. Most of the > delivery process is handled by postfix talking to ldap - no dbmail > involved. All the lmtp server needs to be able to do is route a > message (that already was verified as destined for a valid user) to > the correct user's inbox (or sieve script).
Can you post your LDAP schema? I guess I really should change and use that. I didn't until now, as I can't see the advantage of LDAP over dbmail (for us). But as you're using it that way, I'd like to change to the same model in order to have the same usage in dbmail-2.3, once we switch. And if others you the same scheme, it'l be easier to understand each other or workout features. I've recently expressed our will to provide our web interface. I'm in the process to do that, but it's tricky as it's heavily using our internals. So using a "standard model" should be less pain for the 2.3 adopted version. I hope you're able to post your LDAP schema (confidential?), and that I can adopt to use it. Then I could start trying out dbmail-2.3 with that schema already, so migration should be easier also. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
