From owner-freebsd-questions@FreeBSD.ORG Mon Jun 20 21:29:00 2011 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 9335C106564A for ; Mon, 20 Jun 2011 21:29:00 +0000 (UTC) (envelope-from mark@msen.com) Received: from shell.msen.com (msen.com [148.59.86.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE6D8FC16 for ; Mon, 20 Jun 2011 21:29:00 +0000 (UTC) X-Sent-To: Received: from [192.168.1.106] (c-68-40-255-141.hsd1.mi.comcast.net [68.40.255.141]) (authenticated bits=0) by shell.msen.com (8.14.3/8.14.3) with ESMTP id p5KLSxbE010832 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 20 Jun 2011 17:28:59 -0400 (EDT) (envelope-from mark@msen.com) Message-ID: <4DFFBBA8.8020705@msen.com> Date: Mon, 20 Jun 2011 17:29:12 -0400 From: Mark Moellering User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4DFF7DBF.4030504@msen.com> In-Reply-To: <4DFF7DBF.4030504@msen.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: Pass (sender authenticated); receiver=msen.com; client-ip=68.40.255.141; envelope-from= Received-SPF: Pass (sender authenticated); receiver=msen.com; client-ip=68.40.255.141; helo=[192.168.1.106] X-Milter: Spamilter (Reciever: shell.msen.com; Sender-ip: 68.40.255.141; Sender-helo: [192.168.1.106]; ) Subject: Re: (email) server connection problem : Help -- SOLVED 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: Mon, 20 Jun 2011 21:29:00 -0000 I want to thank everyone who helped me with this. It turned out that due to an administrative error, our hosting company had the ip addresses I was having trouble with routed to the wrong server. Everything is working now. Thanks again, Mark Moellering