From owner-freebsd-questions Thu Nov 30 6:43:24 2000 Delivered-To: freebsd-questions@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 70F3F37B401 for ; Thu, 30 Nov 2000 06:43:19 -0800 (PST) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA30402; Thu, 30 Nov 2000 16:48:20 +0100 Message-ID: <3A2667BB.9020208@i-clue.de> Date: Thu, 30 Nov 2000 15:44:11 +0100 From: Christoph Sold User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20001127 X-Accept-Language: de, en MIME-Version: 1.0 To: Will Mitayai Keeso Rowe Cc: Christoph Sold , questions@FreeBSD.ORG Subject: Re: Sendmail rulesets. References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are right. It is the MX IP that must resolve both ways. Shame there are some providers who don't worry about reverse lookup. HTH -Christoph Sold Will Mitayai Keeso Rowe wrote: > That does not seem right... > > Not every company even HAS an ip address for their domian, especially when > they are just using it for mail. after all, for mail, all you need is an MX > record.... > > > > -----Original Message----- > From: Christoph Sold [mailto:so@server.i-clue.de] > Sent: Wednesday, November 29, 2000 1:03 PM > To: Will Mitayai Keeso Rowe > Cc: questions@FreeBSD.ORG > Subject: Re: Sendmail rulesets. > > > Will Mitayai Keeso Rowe wrote: > >> Hi, folks... >> >> i'm running 4.2-STABLE with an updated sendmail.cf file, and i'm getting >> some strange things going on... >> >> here's a message i get a lot: >> >> Nov 26 12:44:50 castle sendmail[14916]: eAQHhTu14916: ruleset=check_mail, >> arg1=, relay=tomts1.bellnexxia.net >> [209.226.175.139], reject=451 4.1.8 ... Domain >> of sender address paulf@canadianalliance.ca does not resolve >> Nov 26 12:44:50 castle sendmail[14916]: eAQHhTu14916: >> from=, size=10963, class=0, nrcpts=0, >> proto=ESMTP, daemon=MTA, relay=tomts1.bellnexxia.net [209.226.175.139] >> >> What exactly can it not resolve? I resolve canadianalliance.ca just fine > > on > >> that machine... > > > Both forward and reverse name mapping must resolve. That is, if a.b.com > resolves to 1.2.3.4, 4.3.2.1.in-addr.arpa must resolve to a.b.com. > > Just check this is the case using either dig or nslookup for the host(s) > in question. > > HTH > -Christoph Sold > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message