What am I missing? Using hosted domains, you can assign all the aliases you need... Can't even see a reason to structure your setup this way, but assuming there is one, there can't possibly be an unlimited number of domains - so just plug them into the hosted file by script like I'm sure many of us do and rebuild the DB.
maindomain.com sub1.maindomain.com<TAB>maindomain.com etc. The only other time I've seen something similar requested had to do with the postmaster account - can I ask the reasoning behind the existance of the structure you are seeking? m/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jeff Potter Sent: Tuesday, November 18, 2003 6:12 PM To: Sam Varshavchik Cc: Courier Subject: [courier-users] Re: Wildcard DNS + Courier? >> Does hosteddomains not support ".domain.com"? Any reason against >> supporting it? (I.e., would it break anything?) > > Because that for a given domain in hosteddomains, .domain.com means > that you > now have local mailboxes [EMAIL PROTECTED], [EMAIL PROTECTED], etc… > > It's doubtful that you will want to insert an infinite number of > records in > your LDAP, MySQL, or PostgreSQL database for each local mailbox. But if one defined a record "[EMAIL PROTECTED]", then that same record could apply to both [EMAIL PROTECTED] and [EMAIL PROTECTED] It's in some ways the same thing as dash extensions - we have a mechanism for .courier-foo and .courier-bar to be generalized into 1 file (.courier-default) so that we don't have to define an infinite number of files; and we have a mechanism to collapse [EMAIL PROTECTED] and [EMAIL PROTECTED] into 1 entry ([EMAIL PROTECTED]) so we don't have to define an infinite number of addresses. Parts of Courier support the idea of collapsing any subdomain of a domain into 1 entry (esmtpacceptmailfor and bofh's ".domain.com"); but the other half still requires an infinite number of records. It would be logical to be able to accept and deliver all email for <anything>.domain.com with the same dot-domain mechanism. Apply the same logic that's used for selecting a dash extension file: most specific is used; so email to "[EMAIL PROTECTED]" looks up entry "[EMAIL PROTECTED]", then if not found, "[EMAIL PROTECTED]", then "[EMAIL PROTECTED]", and finally, "[EMAIL PROTECTED]". "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" should be separate entries and not searched; otherwise there's no way to define a separate address space for the top level. Given my understanding of Courier, I don't think this would break anything currently in use, and it seems like a logical fit to the rest of the spirit of how addresses can be defined. Is my thinking reasonable, or am I overlooking something that would cause this functionality to break? best, Jeff ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
