Alright then let me try to make it more clear for you: > if you have a local-domain it will not make a lookup if it would the mail could not be delivered local That's the point. Even though it's configured as local-domain I would want it to look up any records (MX, A) and try to sent the mail to the underlying mailserver.
> why should it do this and what should happen relay the message? Why: because there is probably a configuration variable that allows me this configuration. If not then I have to do it differently What should happen: Email -> lookup -> connect -> deliver Normally with local-domains it would be Email -> local deliver. I would want to add 'lookup -> connect' as it's done with non-local-domains > why if it is as local domain configured? To ensure that mails are delivered to the right server since a 100% dynamic system sadly is open for fraudulent entries. > again: it is generally a complete misdesign to use a mailserver with whatever tricks to do strange things even if it would work - such solutions are the root cause for most of our problems these days Not really. Open relays cause problems. Non-standard designs that are well maintained and secured don't. > in other words: this all does not make any sense Neither do parts of your email. I, and I think many others, would appreciate it if you reply in a more polite way since we're only here to share information and furthermore it would be amazing if you re-read your emails before sending them since they are full of weird sentences, typos and wrong grammar. Thanks -----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 1:22 PM An: postfix-users@postfix.org Betreff: Re: forcing MX lookups how should anybody imagine "lookups for every mail" if you have a local-domain it will not make a lookup if it would the mail could not be delivered local so no, you can have not in one instance local inboxes for "example.com" and force postfix to do any dns-lookups for "example.com" why should it do this and what should happen relay the message? why if it is as local domain configured? again: it is generally a complete misdesign to use a mailserver with whatever tricks to do strange things even if it would work - such solutions are the root cause for most of our problems these days in other words: this all does not make any sense Am 16.02.2012 19:05, schrieb Dipl.-Ing. Juergen Ladstaetter: > I know that it doesn't need a MX record. I just want to know if there > is some way of configuring postfix to make DNS (A or MX) lookups for > every mail sent. > Since a two instance configuration would work, I just wanted to know > if there is a way to configure one instance to do this. No need to get > impolite... > > -----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:54 PM > An: postfix-users@postfix.org > Betreff: Re: forcing MX lookups > > what is this for a strange day > > you are the second one in a few hours not understand that a domain > does not need any MX-RECORD to be a valid maildomain > > your other things are also not job of postfix > > if you have a application where users can input data you are > responsible to verify the input inside your application before proceed > > make DNS requests and whatever verifications in your app and leave > postfix in peace - postfix is a MTA and should only be used as MTA > > Am 16.02.2012 18:45, schrieb Dipl.-Ing. Juergen Ladstaetter: >> 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 > > -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm
