atom feed14 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Aliases via D...
FromSent OnAttachments
Jesse KeatingJan 13, 2003 10:07 am 
Tim HunterJan 13, 2003 2:19 pm 
Sam VarshavchikJan 13, 2003 2:54 pm 
Jesse KeatingJan 13, 2003 3:23 pm 
Eduardo RoldanJan 14, 2003 5:28 am 
Andrew NewtonJan 14, 2003 5:38 am 
ecu...@encontacto.netJan 14, 2003 6:21 am 
Eduardo RoldanJan 14, 2003 9:24 am 
ecu...@encontacto.netJan 14, 2003 9:45 am 
Peer Oliver SchmidtJan 14, 2003 11:47 am 
Sam VarshavchikJan 14, 2003 3:31 pm 
Eduardo RoldanJan 15, 2003 8:38 am 
Sam VarshavchikJan 15, 2003 3:21 pm 
Daniel HigginsJan 15, 2003 4:22 pm 
Subject:Re: [courier-users] Re: Aliases via DB (was: Looking to migrate a metric ton of users.)
From:Eduardo Roldan (tra@adinet.com.uy)
Date:Jan 15, 2003 8:38:37 am
List:net.sourceforge.lists.courier-users

On Tue, 2003-01-14 at 20:29, Sam Varshavchik wrote:

Peer Oliver Schmidt writes:

Does the "now" imply you are thinking about adding alias handling via DB to other authentication methods as well? *drool*

Well, eventually. I don't see many people doing it. A lot of people are doing it via LDAP, which is why it's there.

How can you see people using SQL alias handling if it isn't available? Mmm, maybe you refer to auth. Either way, I think that SQL alias is a must for a complete SQL backend.

The past couple of weeks I thought about writing a feature request for this. It is the one thing that keeps me from moving to a SQL DB backend for authentication.

This is separate from authentication. It's basically a separate table, listing the aliases. Given a carefully-designed schema you could, perhaps, implement both functionalities with a single table.

_______________________________________________ courier-users mailing list cour@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

-- Eduardo Roldan <tra@adinet.com.uy>