The configuration for domains etc. is stored in mysql tables but that has nothing to do with the initial problem described in my other email.
-----Ursprüngliche Nachricht----- Von: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] Im Auftrag von Reindl Harald Gesendet: Thursday, February 16, 2012 12:20 PM An: postfix-users@postfix.org Betreff: Re: forcing MX lookups Am 16.02.2012 18:13, schrieb Dipl.-Ing. Juergen Ladstaetter: > We're currently developing a project where customers can add their own > domains to our mailsystem. The biggest problem would be that a > customer adds a domain he doesn't own or isn't represented by our mail cluster. > For example a customer adds ibm.com - a manual validation through one > of our employees isn't possible and an automated validation makes no > sense since the MX records could be changed at any time, which would force a re-check. > > My thought was this: when sending the mail, configure postfix that he > does a MX lookup and sends the mail to the IP given by the lookup. In > this case the customer could add ibm.com, but he wouldn't be able to > grab the mails sent from our cluster. I tried a few things but haven't > come to a clean solution yet. Is there any way to configure postfix to > always make MX record DNS lookups, or is the only way through a second > postfix instance that has no localdomains specified? put your postfix-configuration in mysql-tables and create a limited user for query if input is valid and allowed from the moment on you are dealing with websites AND configurations you should have as much as possible of your config in databases
