On Montag, 18. Dezember 2006 06:08 Aaron Stone wrote: > Patience, patience. Nobody's in a rush to overhaul the way we resolve > deliveries. Even if it's only a couple hours of coding, it's tens or > hundreds of hours of thinking it through.
Of course. I didn't want the solution right now, but the discussion. ;-) > Unless we added another few flags or abstractions, though, it would > require that users have unique names within an *organization* even if > that org had many different *domains*. Something to think about. Yes, I was thinking about that too. In case the userid is stored without the @domain part, there are this options: 1) insert another customer_domains n:m abstraction between the customer and its domain tables 2) insert the domain name into the dbmail_users table, to know which domain group should be taken. It should be the root of that domain group, to make it easier and not necessary for another lookup. The 2nd approach is bad, more sort of a hack. The 1st one could generate more lookups possibly somewhere, but would be cleaner, and I think I will already adopt my db model before I start to transfer users from the existing cyrus to dbmail. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846914666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi3.asc | gpg --import" // Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE // Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
pgpL0tTzfHZwD.pgp
Description: PGP signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
