From owner-freebsd-questions@FreeBSD.ORG Sat Feb 25 19:03:25 2012 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 93544106564A for ; Sat, 25 Feb 2012 19:03:25 +0000 (UTC) (envelope-from jon@radel.com) Received: from wave.radel.com (wave.radel.com [216.143.151.4]) by mx1.freebsd.org (Postfix) with ESMTP id EFDA88FC1E for ; Sat, 25 Feb 2012 19:03:24 +0000 (UTC) Received: by wave.radel.com (CommuniGate Pro PIPE 4.1.6) with PIPE id 10569571; Sat, 25 Feb 2012 13:03:24 -0500 Received: from [192.168.43.246] (account jon@radel.com HELO winesap.local) by wave.radel.com (CommuniGate Pro SMTP 4.1.6) with ESMTP-TLS id 10569565; Sat, 25 Feb 2012 13:03:15 -0500 Message-ID: <4F492262.5090505@radel.com> Date: Sat, 25 Feb 2012 13:03:14 -0500 From: Jon Radel User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Bender, Chris" References: <863259E16B6C464DAD1E9DD10BB31154059CFBAE@wmsexg01.corp.cellularatsea.com> <4F48BAF6.9070204@ifdnrg.com> <863259E16B6C464DAD1E9DD10BB31154059CFBE7@wmsexg01.corp.cellularatsea.com> <4F48EC21.7040805@ifdnrg.com> <863259E16B6C464DAD1E9DD10BB31154059CFBEE@wmsexg01.corp.cellularatsea.com> <4F48F45F.4080304@ifdnrg.com> In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070607080608030900060107" X-Radel.com-MailScanner-Information: Please contact Jon for more information X-Radel.com-MailScanner: Found to be clean X-Mailer: CommuniGate Pro CLI mailer X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure 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: Sat, 25 Feb 2012 19:03:25 -0000 This is a cryptographically signed message in MIME format. --------------ms070607080608030900060107 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable On 2/25/12 10:26 AM, Bender, Chris wrote: > > On telnet w IP it says unable to connect. =2E.. > Its weird that the delivery on A says deferred connection timed out but= on tcpdump I see the port 25 If you can't establish a TCP connection from A to your relay server on=20 port 25, I'd expect all of the above. If you can't establish a TCP=20 connection to port 25 at all from A, I'd stop focusing on the details of = the e-mail server on the relay machine (as they're likely to be beside=20 the point) and start focusing on what is blocking the traffic from A.=20 Have you audited all the firewalls involved? To be really focused, if=20 you see traffic (both ways) at the relay server when A tries to talk to=20 port 25, but A is convinced that no TCP connection is established,=20 either you're stomping on things at the relay server (do your attempts=20 to telnet to port 25 fail immediately or just sit there for a good long=20 time and then fail?), the reply packets from relay to A are getting=20 mis-routed, or A is ignoring the packets coming in from the relay. Can=20 you ping from the relay to A? There's a distinct difference between failure to establish a TCP=20 connection (look to the network stuff) and the e-mail server giving you=20 an error response rejecting your attempt to transfer mail or just=20 quietly loosing the mail (look to the e-mail servers). --=20 --Jon Radel jon@radel.com --------------ms070607080608030900060107--