From owner-freebsd-questions@FreeBSD.ORG Tue May 20 03:01:15 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FE7E106564A for ; Tue, 20 May 2008 03:01:15 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 4FB368FC17 for ; Tue, 20 May 2008 03:01:15 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id 9796D11438F for ; Mon, 19 May 2008 22:01:06 -0500 (CDT) Date: Mon, 19 May 2008 22:01:12 -0500 From: Paul Schmehl To: freebsd-questions@freebsd.org Message-ID: In-Reply-To: <20080520021525.GA1571@shepherd> References: <1211239052.24579.1254029483@webmail.messagingengine.com> <27CE98CC-346E-4051-A745-1F47DEF0760B@mac.com> <20080520021525.GA1571@shepherd> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Problem Sending Mail With Postfix X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 03:01:15 -0000 --On May 19, 2008 10:15:25 PM -0400 Sahil Tandon wrote: > On May 19, 2008, at 4:17 PM, Montag wrote: > >> host mx1.free.bsd.org said: my.mywebsite.com: Helo command rejected: > > Are you sure it wasn't mx1.freebsd.org? And are you mangling > my.mywebsite.com or is that really the hostname with which your server > is configured to EHLO/HELO? The FreeBSD MXs also run Postfix and > employ the reject_unknown_helo_hostname restriction; it rejects HELO > and EHLO hostnames that lack DNS A or MX records. Your log excerpt > looks suspicious because my.mywebsite.com does have a valid DNS A > record: > > my.mywebsite.com. 96 IN A 208.87.33.150 Yes, but this is a bit weird. Macintosh:~ pauls$ telnet my.mywebsite.com 25 Trying 209.181.247.105... Connected to nullmx.mywebsite.com. Escape character is '^]'. 220 nullmx SMTP EHLO testing.mydomain.com 220 Hello quit 220 Buh-bye! Connection closed by foreign host Why "nullmx.mywebsite.com"? Which resolves to an entirely different IP address. Macintosh:~ pauls$ dig +short nullmx.mywebsite.com 209.181.247.105 But it *is* the MX for that domain. Macintosh:~ pauls$ dig -t MX mywebsite.com ; <<>> DiG 9.4.1-P1 <<>> -t MX mywebsite.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49578 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;mywebsite.com. IN MX ;; ANSWER SECTION: mywebsite.com. 300 IN MX 10 nullmx.mywebsite.com. So I've got no idea why he's having this problem, unless it's because the MX record doesn't point to my.mywebsite.com. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/