As I said, I'm not interested in 'disabling' DNS lookups. That isn't what the problem is. On Tuesday 18 November 2003 18:10, Frederik Vos wrote:

On Tue, 2003-11-18 at 18:03, Örn Hansen wrote:

...

SuSE uses postfix, as default and in SUSE 8.2 setting it up to receive email was quite simple and easy. With 9.0 it's impossible.

First, I've got the setup that my machine is behind a broadband router. Beyond the router, the router is known as virtual.foobar.org. The mail is redirected to the machine on the inside, mail.virtual.foobar.org. On the intranet, virtual.foobar.org is referring to the intranet. And now, here comes postfixes neat setup. Whenever it receives email, it tries to relay this email to virtual.foobar.org, even though this is specified as mydomain, and mydestination. The realy of course fails, because postfix doesn't look for virtual.foobar.org in the /etc/hosts file, but does a direct dns lookup (pfft). Now, setting relaydomains to "", gets postfix to try and locate localhost. But, hold your horses, its trying to locate localhost as a relay host! and it's trying to locate it via DNS.

Now, I don't really care if you can setup options to fix this ... this "handling" of the email is stupid. It's so stupid, that this mail delivery agent can't really be a well programmed stuff. Or, SUSE's version is so buggy it's hilarious. And I'll tell you why: UNDER NO CIRCUMSTANCES SHOULD DNS TAKE PRECEDANCE OVER HOSTS, EVER. Unless it's specified in the nsswitch.conf, which it isn't and postfix is bypassing the local operating system setup. And *that* boys, reminds me of WINDOZE.

if dns resolution is not available or you are using 'non-existed' host/domainnames: disable_dns_lookups=yes

and this reminds me of Windows users who never read the manual -- Frederik Vos VosBerg@SuSE & L4L

On Tuesday 18 November 2003 21:48, Carlos E. R. wrote:

The Tuesday 2003-11-18 at 18:03 +0100, Örn Hansen wrote:

...

localhost. But, hold your horses, its trying to locate localhost as a relay host! and it's trying to locate it via DNS.

Yes, mail delivery looks for a DNS entry of type MX. You must configure your dns to handle it, not the host file.

Just to clarify this for those that don't understand that, the reason mail delivery *NEEDS* to use DNS is that it needs to look for the MX records to find out what the right mail server is for a domain, which is a separate question than what is the IP address associated with a domain name. So the hosts file cannot answer the question. ---------------------------------------------------------------------------- DDDD David Kramer david@thekramers.net http://thekramers.net DK KD DKK D Isn't the universe an amazing place? DK KD I wouldn't live anywhere else. DDDD J'Kar