jf> DBMail doesn't currently work in multiple databases at one jf> time. Thus you would end up with multiple instances of dbmail jf> databases and applications running. The LDAP authentication would jf> allow you to have 1 central location for user/pass combos, however jf> your users would need to always log into the same instance of jf> databases/apps to even see the same content as before. Regular TCP
Thanks. I think you may have misunderstood what I'm thinking of (not least because I didn't go into detail on that part). I intend to do load balancing with an IMAP proxy like perdition which will transparently connect my users to the correct server. Incoming mail will similarly be fanned out by my MTA's local delivery mechanism. So, I fully expect there to be one dbmail instance controlling exactly one MySQL instance, and I don't expect the dbmail instances to know anything about each other. If my front end connects to a dbmail instance and tries to access a given folder (belonging to someone else), will the ACL system freak because the connecting user doesn't have a mailstore in that dbmail instance? _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
