Eduardo Roldan writes:
I'll rephrase this: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?
I see a lot of people doing LDAP-based aliasing with sendmail, postfix, and other MTAs.
I don't see ANYONE doing the same with SQL.
Things must be prioritized. I do not see this as a top priority. There is already in place a decent infrastructure for LDAP directory-based mail routing, and most folks who want a directory-based mail routing setup are going to go with LDAP.Mmm, maybe you refer to auth. Either way, I think that SQL alias is a must for a complete SQL backend.
-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
