From owner-freebsd-ports@FreeBSD.ORG Thu Dec 13 16:52:42 2007 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E4DF16A41B for ; Thu, 13 Dec 2007 16:52:42 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 6721A13C46A for ; Thu, 13 Dec 2007 16:52:42 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 2ACBB654FF for ; Thu, 13 Dec 2007 10:52:42 -0600 (CST) Date: Thu, 13 Dec 2007 10:52:41 -0600 From: Paul Schmehl To: ports@FreeBSD.org Message-ID: In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Re: problem to reach a maintainer X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2007 16:52:42 -0000 --On Thursday, December 13, 2007 10:17:43 -0500 yves.guerin@muhc.mcgill.ca=20 wrote: > > > Dear > > I try to send a bug report to: mi@aldan.algebra.com for tclhttpd-3.5.1_2 > but =C3=89I got this error > > Votre FreeBSD Port: tclhttpd-3.5.1_2 > document : > > n'a pas =C3=A9t=C3=A9 mi@aldan.algebra.com > distribu=C3=A9 =C3=A0 > : > > Motif : Router: Failed to connect to SMTP host ALDAN.ALGEBRA.COM > because : The server is not responding. The server may be > down or you may be experiencing network problems. Contact > your system administrator if this problem persists. > > Dig shows a resolvable host and dig -t MX shows a correctly configured MTA. Try again. It's likely exactly what the error message says - network=20 problems or the server was down. --=20 Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/