From owner-freebsd-ports@FreeBSD.ORG Tue Oct 8 14:06:01 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 94338E66 for ; Tue, 8 Oct 2013 14:06:01 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6FDFF25D1 for ; Tue, 8 Oct 2013 14:06:00 +0000 (UTC) Received: from [192.168.0.22] (unknown [130.255.26.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 1A73243B4A for ; Tue, 8 Oct 2013 09:05:46 -0500 (CDT) Message-ID: <52541129.9020209@marino.st> Date: Tue, 08 Oct 2013 16:05:29 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Undelivered Mail: horde@FreeBSD.org References: In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 14:06:01 -0000 On 10/8/2013 15:21, Carmel wrote: > I attempted to contact the maintainer of the > "deskutils/horde-groupware" port, , but I received > the following notification: > > : Host or domain name not found. Name service error for > name=freebsdnorth.com type=AAAA: Host found but no data record of requested > type > > Has anyone else experienced this problem? Is there a change in the > maintainers address that is not reflected in the port? > Yes, I experienced this months ago. The address horde@ points to has been bogus, it's not a new thing. And yes, something should probably be done. John