Nope, that wan't it (problem is solved, after REALLY closely comapring every byte in all the configfiles with another host) I may relay. I did that already. No problems there. The problam was that my mailserver wouldn't let any mail come in. It seemed to me it couldn't resolve the sending domainname. This was the solution: In /etc/host.conf, put a comma instead of a space between 'hosts' and 'bind'..... Stupid, isn't it? Now to find out who did the change, and I'm all happy again. Thanks for your help anyway! Rogier Maas Brevsville Administrator wrote:

Roger

You need to add your private IP's to your /etc/access and then makemap (or SuSEconfig) and then restart sendmail. My guess would be that you have changed your internal MASQ'd ip range or messed up the db files.

If your internal ip's are 192.168.x.x just add 192.168 RELAY to your access file as above.

Chris

On Fri, 02 Jun 2000 15:41:23 +0200, Rogier Maas wrote:

...

Hi,

I have the most ugly problems using DNS. I have three internal networks and one external (connected to Internet). I don't run named and my nameservers are those of my ISP.

Whenever I connect to my box with pop3, the messages are: Unable to find canonical name of client (err=2). This is no surrise, since my internal IP's are not known to the nameservers outside.

But when email is beeing sent to my box, sendmail suddenly says: 'Sender domain must resolve' and 'Sender domain must exist'. Why is this? And why did it work before? Are the nameservers of my ISP malfunctioning? I've never had this with RedHat or Debian, why SuSE? Is there something different in configurating SuSE?

I hope anyone can give me some pushes in the right direction, because this is driving me crazy.

Thanks.

Rogier

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Thorsten Kukuk wrote:

"order hosts bind" is a valid syntax and should work in every case. And, the "order" option in /etc/host.conf should be ignored by sendmail. Instead, /etc/nsswitch.conf should be used. Seems a program uses it's own, incompatible resolver library. I thought only libc5 does this, not sendmail :(

Thorsten

That's ehat I thought... But look here! # man host.conf DESCRIPTION The file /etc/host.conf contains configuration information specific to the resolver library. It should contain one configuration keyword per line, followed by appropriate configuration information. The keywords recognized are order, trim, multi, nospoof and reorder. Each keyword is described seperately below. order This keyword specifies how host lookups are to be performed. It should be followed by one or more lookup methods, seperated by commas. Valid methods are bind, hosts and nis. "seperated by commas"... This is SuSE Linux 6.4, maybe they've altered this somewhat somehow. I'm not sure.. The minute I changed the space into a comma, the damned thing worked again. This cost me a lot of aspirines, and the mail.suse.com-server a lot of traffic to handle... not nice! Rogier Maas -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Thorsten Kukuk wrote:

On Sat, Jun 03, Rogier Maas wrote:

...

Thorsten Kukuk wrote:

...

"order hosts bind" is a valid syntax and should work in every case. And, the "order" option in /etc/host.conf should be ignored by sendmail. Instead, /etc/nsswitch.conf should be used. Seems a program uses it's own, incompatible resolver library. I thought only libc5 does this, not sendmail :(

Thorsten

That's ehat I thought... But look here!

# man host.conf

Who tells you, that the manualpage is correct ? The only relevant part are the bind, libc5 and glibc sources and documentation. And there stand, that it is correct and the comma is not needed.

...

"seperated by commas"... This is SuSE Linux 6.4, maybe they've altered this somewhat somehow. I'm not sure.. The minute I changed the space into a comma, the damned thing worked again. This cost me a lot of aspirines, and the mail.suse.com-server a lot of traffic to handle... not nice!

The only question is: Why does it work for over 5 years without problems ? If the syntax is wrong, a lot of more people should have found it due the last 5 years. But I cannot find any bug report about it.

And WAS this the correct solution? Who's going to tell me there is another program looking into that file? Why did it work? And why did it not work when there was no comma? (the WAS a space, though..) I hope this gets figured out.. Rogier

I don't know in the moment where the "to the official resolver library from bind incompatible version" comes from, but I will try to find them next week.

Thorsten

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/