One "icky" feature of using wildcard aliasing is having to use a complete table entry to simply turn on aliasing. I think the entry only has to exist and most of the other fields are ignored.
Would there be any interest in having an extra enum(1,0) on/off toggle available that would simply turn on wildcarding for the $(domain) part of the email identity ?
[EMAIL PROTECTED] uid gid home etc
could be
[EMAIL PROTECTED] uid gid home alias etc
which turns on aliasing for @domain.com using any other needed parameters from this users entry.. like the homedir/maildir.
--markc
But, (_IF_ I understand you correctly) then you have to look at ALL the rows in the table to see if the setting exists somewhere, (or do a special lookup on that field, which I don't know if Courier is really able to do currently) rather than just looking up one address.
Personally, I prefer having a few extra rows instead of "messing up" my table structure with additional columns as you suggest. But I suppose different people see different things as "icky". =)
Plus, what happens if someone accidentally sets one entry to on, and one to off? Which entry is correct?
Honestly, I don't know what difference one row in a table actually makes. It's not "clean" I suppose, since it should probably be split out into another table -- a table of domain names with their settings, such as this domain aliasing thing. ... Though some people might find an extra table to manage to be their headache I suppose. And not to mention that Courier can't look up "config settings" in a database to my knowledge.
But anyway, what problems do you see it as causing to have 1 extra entry per domain? And how would you suggest implementing the lookup if it is handled some other way? 'Cause I don't think your initial suggestion would work very well, due to issues of how Courier will actually *do* the lookup.
I don't actually know how Sam is having Courier do the lookup. But I just kind of suspected that it was merely passing the address '[EMAIL PROTECTED]' to authdaemon for normal processing. If it comes back valid, it does the aliasing thing. If not, it doesn't. But (if that is what happens... Sam, is it?) then to change it you'd have to make Courier do it's own lookup on another field, or pass a new param to authdaemon which authdaemon then would use to know *what* it was checking for and what kind of response to send back.
Messy, I think. -- But then again, I'm not 100% sure I read the same thing that you meant by what you wrote, nor that I'm guessing properly at how Courier finds out whether to do the aliasing thing or not. It's really early after all, and I'm no expert on Courier internals anyway. :) ... So, anyone can feel free to shoot me down if they have more informed comments to make.
-jab
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
