From owner-freebsd-ports@FreeBSD.ORG Tue May 17 11:38:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 279AE106566B for ; Tue, 17 May 2011 11:38:50 +0000 (UTC) (envelope-from kkobb@skylinecorp.com) Received: from mail.skylinecorp.com (mail.skylinecorp.com [64.141.137.166]) by mx1.freebsd.org (Postfix) with ESMTP id DE6998FC16 for ; Tue, 17 May 2011 11:38:49 +0000 (UTC) Received: from [172.16.2.1] ([172.17.0.161]) (authenticated bits=0) by mail.skylinecorp.com (8.14.4/8.14.4) with ESMTP id p4HBMFj0068289 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 17 May 2011 07:22:15 -0400 (EDT) (envelope-from kkobb@skylinecorp.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=skylinecorp.com; s=mail; t=1305631335; bh=NxpWKiS4EyseHrYtfMji5xZwzGAht5KRnIGYiioYZXU=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=SqtshCrzQcCUYFQJcr2mdtiohbgDQkw2K1HwpT9X2KrnhGfkQGL6pm4fOzu1vfS/L 1etU0qD92mX7Gn4BOI2TOcECNYwIQDbVR+5W8oD6IyidJ9HurMskxMTypauwSiyxr1 jpsfdE0Wwa1jXSu8XtX18ShKPdyYK7phDzoNdzE4= DomainKey-Signature: a=rsa-sha1; s=mail2; d=skylinecorp.com; c=simple; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:references:in-reply-to:content-type:content-transfer-encoding; b=IJDcIZPKRyUK+topvuuI6OJb4lK7oRRWtTRmSqrU4WKbT/b5xUCjZN1VsvQBnSwVi 14D/zWhjP6A1/5eKTsG0w== Message-ID: <4DD25A66.2010900@skylinecorp.com> Date: Tue, 17 May 2011 07:22:14 -0400 From: Kevin Kobb Organization: Skyline Corporation 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-ports@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Skyline-MailScanner-Information: Please contact the ISP for more information X-Skyline-MailScanner-ID: p4HBMFj0068289 X-Skyline-MailScanner: Found to be clean X-Skyline-MailScanner-MCPCheck: MCP-Clean, MCP-Checker (score=0, required 1) X-Skyline-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-105.2, required 4.25, autolearn=not spam, ALL_TRUSTED -4.80, BAYES_00 -0.30, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, USER_IN_DKIM_WHITELIST -100.00) X-Skyline-MailScanner-From: kkobb@skylinecorp.com X-Skyline-MailScanner-Watermark: 1306236136.40219@3EFRHUT5I+3pzJjRn4C76w X-Spam-Status: No Subject: Re: Mailscanner update -- changes to the port 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: Tue, 17 May 2011 11:38:50 -0000 On 5/15/2011 6:38 AM, Chris Rees wrote: > Hi all, > > I've just finished working on the update for MailScanner, and I've > changed a few things that have annoyed me loads-- perhaps it's been > irritating for you too! > > > I've removed the extra targets for initial configuration etc, and > moved them into a pkg-install script, which means that it also does > the Right Thing when being installed from packages; no more messing > about doing manual moves of the million .sample files installed! > > Since I know loads of people rely on this port, please would people > try this out and let me know of any issues? Patch at [1] and shar at > [2]. > > Before people ask why I haven't done the usual method of putting lines > in pkg-plist for config files, take a look at how many there are... > > TIA, > > Chris > > [1] http://www.bayofrum.net/~crees/patches/mailscanner-4.83.5.patch > > [2] http://www.bayofrum.net/~crees/patches/mailscanner-4.83.5.shar > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Did some quick testing on a non-production machine, and it seemed to work OK. Not so sure you need to get rid of the CHANGES.port file as I think it is more FreeBSD specific than just the upstream change log. However, it probably isn't a big deal either way. I'll keep working with it and let you know if I run across anything strange. Thanks.