-----Original Message----- From: cour...@lists.sourceforge.net [mailto:cour...@lists.sourceforge.net]On Behalf Of Jeff Potter Sent: Tuesday, November 18, 2003 6:12 PM To: Sam Varshavchik Cc: Courier Subject: [courier-users] Re: Wildcard DNS + Courier?

But if one defined a record "user@.domain.com", then that same record could apply to both us...@foo.domain.com and us...@bar.domain.com. 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 fo...@domain.com and ba...@domain.com into 1 entry (ali...@domain.com) 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 "sa...@foo.domain.com" looks up entry "sa...@foo.domain.com", then if not found, "ali...@foo.domain.com", then "sam@.domain.com", and finally, "alias@.domain.com". "ali...@domain.com" and "sa...@domain.com" 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?