Hi,
I am hoping an email domain-expert who is familiar with qmail-ldap can help me with a question "RTFM" doesn't seem to help with. If RTFM is the right answer to my questions, please just point me to the right M.
My situation: I am setting up a qmail-ldap+ldap_control server.
My problem: We are working with domain name registrars. When a user registers his domain with one of our partners, that partner will create an MX record for that new domain, and that MX record will point to our email server. So, for example, "joe.com" could have its mail routed to "mail.partnername.com" which we host. Now, the problem is that our server will *not* know that it receives for joe.com (rcpthosts) and will not know that joe.com is local (locals). These values are initialized at SMTPD init time currently in qmail, I think. I need 'joe.com' to be considered receivable and local, but I am not sure how to accomplish this *best*.
My thoughts: I *believe* I can reduce this problem in the following way: suppose I tell qmail that any mail that gets to the locals stage is local -- that is, if I already agreed to receive the email (rcpthosts), then it's local. Then, my remaining problems are: (1) how do I tell locals that all email is local (does a blank locals mean this?), and 2) how can I *dynamically*, at delivery time, figure out whether the proposed email is receivable (rcpthosts)? I could definitely hack the qmail main code to do this. Are there better ways? Are there better ways to accomplish my overarching goal/solve my overarching problem?
My questions: Is there anything in my thoughts leading me down the wrong path? Is there a better way than hacking qmail main code? Am I going to violate any protocols of standard or kindness in my solution if I do it the way I propose?
Any and all comments welcome and requested. Thank you,
-Ed Abrams
[EMAIL PROTECTED]
