Hello, There are 2 sides, delivery and authentication, and they're handled differently. What I'd do if I were you is have my mta rewrite the destination addresses to something consistent (ie. rewrite all aliased addresses to the standard domain), and then use the dbmail_usermap table to handle the multiple possible usernames for authentication. (I don't remember exactly how flexible the usermap is, but even if you have to have an entry for every username, that could probably work with only a "couple thousand" users (not elegant, but quick/easy).)
On Fri, 2006-12-15 at 13:26 -0500, Rod K wrote: > Setup: > > dbmail 2.2 > postgres 8.1.4 > > We have a legacy system running qmail/vpopmail with a couple thousand > users that we'd like to migrate. With vpopmail having an aliased > domain, the user can sign in as [EMAIL PROTECTED] or > [EMAIL PROTECTED] Due to some legacy issues, we have 3 domains > aliased together and various users using any of the 3 aliased domains in > their login. > > I've thought of creating a view in PG that would be the union between > dbmail_users and a select joining dbmail_users and dbmail_aliases that > would return userid as the alias. This would allow a login using an > alias. Of course, I'd have to rename the dbmail_users and give the view > that name, along with some rules to handle INSERT, UPDATE, DELETE on the > view. > > Basically, I've got three questions: > > 1) Would doing this cause a problem somewhere in the dbmail apps that > I'm not aware of. > 2) Would it be better to modify the queries that handle pop3 and imap > auth in the source > 3) Does anyone have any ideas of another way to accomplish this? > -- Jesse Norell - [EMAIL PROTECTED] Kentec Communications, Inc. _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
