From owner-freebsd-ports@FreeBSD.ORG Wed Oct 9 10:49:36 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 139D456B for ; Wed, 9 Oct 2013 10:49:36 +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 E27762C74 for ; Wed, 9 Oct 2013 10:49:35 +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 09C1B438BC for ; Wed, 9 Oct 2013 05:49:22 -0500 (CDT) Message-ID: <525534A9.70600@marino.st> Date: Wed, 09 Oct 2013 12:49:13 +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: <52541129.9020209@marino.st> <20131009010106.GB27593@jubz> 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: Wed, 09 Oct 2013 10:49:36 -0000 On 10/9/2013 12:31, Carmel wrote: > On Tue, 8 Oct 2013 21:01:06 -0400 > Sahil Tandon articulated: > >> Did you, by chance, report this to postmaster@freebsd.org? >> >> We'll look into it. > > No I didn't because: > > A) I was not sure if it was a local problem; ie, only me > > B) Who to actually report it to > > Since it is not a local problem, I am glad that you are looking into it. > I suspect that question was addressed to me. I reported it on irc #bsdports. We figured it would return at some port, nobody felt it was necessary to disable horde@ and potentially return all the horde ports to the pool at the time... John