Hi, Thanks for all the help. The relay was not open after all. I did not think and have tested using telnet from a machine for which top.health.gov.za is suppose to relay. My problem was basicly solved by removing the lines that were added to local-host-names by the update. These lines have told sendmail that health.gov.za is another name for top.health.gov.za and caused the machine to look for a user on top instead of relaying the message. thanks aggain Willem
On Mon, 17 Mar 2003, Cowles, Steve wrote: > > -----Original Message----- > > From: Willem van der Walt<[EMAIL PROTECTED]> > > Sent: Monday, March 17, 2003 7:27 AM > > To: Willem Brown > > Cc: [EMAIL PROTECTED] > > Subject: Re: sendmail secondary relay gives user unknown after up2date > > > > > > Hi, > > Thanks sofar. > > It worked, but now i have an open relay. > > Editing the two files you mentioned should not create an open relay. Have > you tested your server against an external relay tester like: > > http://abuse.net/relay.html > > > > I had a modified local-host-names file that was modified by > > the update. It had the comment that it made the entry > > top.health.gov.za health.gov.za > > from the obsoleted /etc/sendmail.cw file > > regards, Willem > > Any domain names listed in local-host-names would be considered local. i.e. > sendmail would hand off any e-mail addressed to these domains to procmail > for local delivery, not relay them. > > Based on my understansing of your post, it sounds like all you need are the > mailertable entries for the domain names that you wish to relay to your > primary mail server. local-host-names would be empty. > > Steve Cowles > > > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
