7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier+mySQL+Ali...
FromSent OnAttachments
Jeff RosenbergApr 26, 2002 3:49 pm 
Sam VarshavchikApr 26, 2002 4:15 pm 
Julian MehnleApr 26, 2002 4:31 pm 
Julian MehnleApr 26, 2002 4:40 pm 
Jeff RosenbergApr 26, 2002 5:05 pm 
Julian MehnleApr 26, 2002 5:20 pm 
Sam VarshavchikApr 26, 2002 5:33 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Courier+mySQL+Aliases : can you do mySQL aliases like this?Actions...
From:Jeff Rosenberg (je@webisaur.com)
Date:Apr 26, 2002 5:05:54 pm
List:net.sourceforge.lists.courier-users

-keep aliases in the same mySQL password table, but load it up with the same password info as the main account.

No, this is the wrong approach. There is already a mechanism for LDAP- based alias lookups. An equivalent MySQL-based will do the trick.

thanks for the reply Sam. But I'm unsure what you mean by "An equivalent MySQL-based will do the trick".

Is such an item in development right now? As a bit of a "script kiddie", I'm not really prepared for that kind of software development to do a port of the LDAP function....

I just wondered if me doing the above trick will set me up for headaches later. it doesn't sound like there's anything fundamentally wrong with this approach, just that it's not the ideal way to do it. But I can live with that, especially if there is no other option for me at present (I really don't want to run LDAP for this one function, for several reasons (memory costs + the additional complexity of integrating ldap queries (sql statements are much more vanilla, and can be implemented in more situations..)). My proposed solution seems like it could be easily tweaked to do "proper" aliasing, when SQL alias support comes along for Courier...

Of course, if someone is already working on such an animal (SQL aliases), then I can probably wait...

TIA for your help,

-Jeff