From owner-freebsd-ports@FreeBSD.ORG Sun Sep 14 05:59:46 2014 Return-Path: Delivered-To: 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 ESMTPS id 1F615A50 for ; Sun, 14 Sep 2014 05:59:46 +0000 (UTC) Received: from mailhost.netlab.sk (mailhost.netlab.sk [84.245.65.10]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92071A07 for ; Sun, 14 Sep 2014 05:59:44 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan) by mailhost.netlab.sk with ESMTPA; Sun, 14 Sep 2014 07:54:34 +0200 id 00DD6011.54152D9A.00014DC8 Date: Sun, 14 Sep 2014 07:54:28 +0200 From: Milan Obuch To: admin@saigol.ca Subject: Re: FreeBSD Port: courier-0.65.3_3 Message-ID: <20140914075428.350c13c4@zeta.dino.sk> In-Reply-To: <54152493.6010302@saigol.ca> References: <54152493.6010302@saigol.ca> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; i386-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 05:59:46 -0000 On Sun, 14 Sep 2014 01:16:03 -0400 "Saigol.ca Admin" wrote: > Hello, > > It seems that the Courier-MTA current version is 0.73.2. > > The latest FreeBSD port is based on version 0.65.3, which seems to be > more than 3 years old. Are there any plans to update the port to the > latest version of the software? > > Thanks, > > Abid > Yes, there are. Unfortunatelly, other tasks have currently more urgent attention here, and there are some issues to be solved - new dependencies are introduced and new port should be created first for library needed to build new courier... also old port was recently staged, which was necessary to keep it in tree at all. Also it looks like recently a bit more work needs to be put into patch to get new version committed into port tree, so it will take a bit of time before new version of mail/courier could be published in port tree. Before that, I will contact you as soon as I will have something to test. Your setup is most probably different from mine and thus together we can cover more usage scenarios, which is good thing everytime. Regards, Milan