Hello, Yes, it was patched for mysql and pgsql and applied clean last I'd tried, but that's been a couple months. I'm not sure on the graceful failure when usermap table doesn't exist, but I'm sure that can be done. I can forward the patch now if you want to work with it, but I may not/probably won't get to working on it today. This thread ought to probably move to dbmail-dev about now. :)
---- Original Message ---- From: Paul J Stevens <[email protected]> To: [email protected] Subject: Re: [Dbmail] solicit feature interest Sent: Tue, 07 Oct 2003 09:40:03 +0200 > Jesse, > > I'm interested. > > Does the patch apply cleanly to current CVS-head? Does it support both > mysql and postgresql? If so, could you please send me the patch, or > upload it to sf.net. I'll see if I can extend the current debian > packages with this added capability. > > fwiw, I have no problems with extending the debian packages beyond > dbmail-1.1 as long as those patches apply cleanly, support both db > backends and gracefully degrade. That is, I won't apply patches that > will break dbmail for people doing an apt-get upgrade. So your patch > shouldn't break dbmail for people who don't have the usermap table. > > > > Jesse Norell wrote: > > Hello, > > > > Trying to solicit some response for interest in a feature of dbmail. > > We had a fairly good size user base when we migrated to dbmail that > > were all using short usernames, and we wanted to start using long names, > > but knew we couldn't just up and switch, so we wrote a little patch to > > help the migration which allows users to use multiple login names via > > another lookup table. Would anyone else find this useful? If so, > > we've patched both mysql and pgsql to do this (under dbmail 1.x tree) > > and if we could get it adopted into the main dbmail source, we can > > stop maintaining our own custom patches and go to the debian packages. > > :) > > > > The actual implimentation is a simple lookup table (which we called > > usermap), which is simply a map of user_idnr, userid pairs. The > > normal lookup is done for a matchind userid in users table, and if > > one is not found, a query is done for a matching usermap entry (or it > > may be reversed, falling back to users table if usermap entry isn't > > found). All new users are only added to the users table, using full > > email address logins, and at the time of conversion we filled the > > usermap with all the short names. The same table could facilitate > > a number of other scenarios as well (login names at different > > domains, etc.). > > > > I don't know that we've tested the results without having the > > usermap table created, but I'm sure it could be handled so that if > > you've not done so it continues on without a problem. So - anyone > > interested? (And will any new features eveb be accepted for dbmail > > 1.x?) > > > > Jesse > > > > -- > > Jesse Norell > > jesse (at) kci.net > > > > > > _______________________________________________ > > Dbmail mailing list > > [email protected] > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > > -- > ________________________________________________________________ > Paul Stevens mailto:[EMAIL PROTECTED] > NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] > The Netherlands________________________________http://www.nfg.nl > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- End Original Message -- -- Jesse Norell jesse (at) kci.net
