I'm working on getting subdomains to work with wildcard dns. I'm still lost, but have tracked down that Courier doesn't even hit the DB with the mysql_select_clause, so my earlier thought of a "solution" won't work with Courier, as I understand it.
Sam, if the line ".foobar.com" is in esmtpacceptmailfor, why does the mail server accept RCPT TO's in any wildcard subdomain, but then not bother looking up the subdomain info in authlib?
Only addresses in local domains are looked up: domains listed in locals or hosteddomains.
I've got a "better" idea than my last one, which was probably more complicated than Sam would want: add dot-domain support (".domain.com") into just hosteddomains, with the assumption that one will use it in an alias (or that one is defining literal "[EMAIL PROTECTED]" entries; regardless, no extra queries or modifications in authlib).
E.g., we're already able to do:
domain.com
foobar.domain.com <TAB> domain.comCourier should allow hosteddomains/files to also read like:
domain.com
.domain.com <TAB> domain.com
(Currently, this results in an MX error dsn.)When going to do the locally-hosted check, this would only add a check for each super domain; e.g. looking up locally hosted domains for mail sent to [EMAIL PROTECTED] would add additional lookups for ".bar.domain.com", then ".domain.com". (and stop there? or complete to TLD?)
This should, if I understand, be all that's necessary to allow for wildcard DNS to work with Courier. What are the performance ramifications? Any other drawbacks?
Doable? Thoughts?
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
