From owner-freebsd-ports@FreeBSD.ORG Tue Jan 3 00:52:14 2006 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14C1416A41F for ; Tue, 3 Jan 2006 00:52:14 +0000 (GMT) (envelope-from jan@1kdigital.com) Received: from mail.1kdigital.com (coffin.1kdigital.com [194.204.33.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE8943D5C for ; Tue, 3 Jan 2006 00:52:11 +0000 (GMT) (envelope-from jan@1kdigital.com) Received: (qmail 92926 invoked by uid 89); 3 Jan 2006 00:54:51 -0000 Received: by simscan 1.1.0 ppid: 92916, pid: 92918, t: 1.8429s scanners: attach: 1.1.0 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on coffin.1kdigital.com X-Spam-Level: X-Spam-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from rohi.1kdigital.com (HELO chipmunk) (jan@1kdigital.com@194.106.125.98) by mail.1kdigital.com with ESMTPA; 3 Jan 2006 00:54:49 -0000 Message-ID: <001a01c60fff$b3655ec0$0200000a@chipmunk> From: "Jan-Erik Moon" To: Date: Tue, 3 Jan 2006 02:50:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: ports@FreeBSD.org Subject: FreeBSD Port: qmail-1.03_4 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, 03 Jan 2006 00:52:14 -0000 Hi, First - a happy new year to the FreeBSD community. I found a small bug in qmail ports Makefile. WITH_AUTHCRAM knob modifies the SELECTED_OPTIONS variable by adding "cram-md5=yes". When WITH_AUTHCRAM is not defined, "cram-md5=no" is added. These values actually should be "cram_md5=yes" and "cram_md5=no". (See README.spamcontrol). I discovered this bug when I tried to disable CRAM-MD5. Spamcontrol seems to have CRAM-MD5 auth enabled by default, so the only effective value is "cram_md5=no". PS. Have you had time to think about the custom error patch? Thank you, Jan-Erik Moon