From owner-freebsd-ports@FreeBSD.ORG Thu Jun 2 12:31:15 2005 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 654A316A41F; Thu, 2 Jun 2005 12:31:15 +0000 (GMT) (envelope-from mark@antsclimbtree.com) Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 008BB43D53; Thu, 2 Jun 2005 12:31:14 +0000 (GMT) (envelope-from mark@antsclimbtree.com) Received: from lilbuddy.antsclimbtree.com (adsl-69-232-30-131.dsl.snfc21.pacbell.net [69.232.30.131]) by pimout4-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j52CVDPA148710; Thu, 2 Jun 2005 08:31:13 -0400 Received: from 212.229.216.81.s-s.vf.siwnet.net ([81.216.229.212] helo=[10.11.11.32]) by lilbuddy.antsclimbtree.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.51 (FreeBSD)) id 1DdosI-000GcI-NY; Thu, 02 Jun 2005 05:32:39 -0700 In-Reply-To: References: <790a9fff050601150173d7bd34@mail.gmail.com> <94f6a6f4db839f65d907d729e14a15ad@antsclimbtree.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mark Edwards Date: Thu, 2 Jun 2005 14:31:24 +0200 To: Hajimu UMEMOTO X-Mailer: Apple Mail (2.622) Cc: ports@freebsd.org, Scot Hetzel Subject: Re: FreeBSD Port: cyrus-sasl-2.1.21 -- Couldn't update db 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: Thu, 02 Jun 2005 12:31:15 -0000 On Jun 2, 2005, at 2:10 PM, Hajimu UMEMOTO wrote: > mark> It occurs every time saslpasswd2 updates the db. The db is > mark> successfully updated, but there is a warning issued. When > saslauthd > mark> updates the db, no warning. > > mark> I also get the following non-sensical warnings in > /var/log/auth.log: > > mark> Jun 2 02:03:49 lilbuddy imaps[61325]: no user in db > mark> Jun 2 02:18:30 lilbuddy exim: no user in db > > You can simply ignore the messages. You can see following chunk in > saslpasswd.c: > > /* Either we were setting and succeeded or we were disabling and > failed. In either case, we want to wipe old entries */ > > /* Delete the possibly old entries */ > /* We don't care if these fail */ > propctx = prop_new(0); > if (!propctx) ret = SASL_FAIL; > if (!ret) ret = prop_request(propctx, delete_request); > if (!ret) { > ret = prop_set(propctx, "cmusaslsecretCRAM-MD5", NULL, 0); > ret = prop_set(propctx, "cmusaslsecretDIGEST-MD5", NULL, 0); > ret = prop_set(propctx, "cmusaslsecretPLAIN", NULL, 0); > ret = sasl_auxprop_store(conn, propctx, userid); > } > if (propctx) prop_dispose(&propctx); > > The messages are out by this compatibility craft. Aha, so its *supposed* to work that way. So, there must be similar code in whatever is used to authenticate sasl connections. That's really absurd, shouldn't this be considered a bug? These messages totally saturate my /var/log/auth.log I did try to raise the issue on the cyrus-sasl and cyrus-imap lists, with no response whatsoever. It should at least be explained somewhere, in a FAQ on the cyrus site, or in the FreeBSD port pkg-message. Or something. Its so confusing. Thanks for the help! -- Mark Edwards mark@antsclimbtree.com cell: +46704070332