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/