From owner-freebsd-ports@FreeBSD.ORG  Mon Feb  2 16:48:50 2015
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 248F7646
 for <freebsd-ports@freebsd.org>; Mon,  2 Feb 2015 16:48:50 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D8725EEA
 for <freebsd-ports@freebsd.org>; Mon,  2 Feb 2015 16:48:49 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1YIKB5-000Fav-7g; Mon, 02 Feb 2015 17:48:47 +0100
Date: Mon, 2 Feb 2015 17:48:47 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Marko Cupa?? <marko.cupac@mimar.rs>, freebsd-ports@freebsd.org
Subject: Re: mail/dovecot2: who calls doveconf upon boot?
Message-ID: <20150202164847.GH44537@home.opsec.eu>
References: <20150202164301.29d6d14b@efreet.mimar.rs>
 <20150202160520.GB79227@over-yonder.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150202160520.GB79227@over-yonder.net>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 16:48:50 -0000

Hi!

> > My question is: Who calls doveconf, and for what purpose?
> 
> A quick look at the dovecot.in rc script in the ports tree suggests
> that it's unconditionally running dovecot when it's run try try and
> populate base_dir, whether $dovecot_enable or not.

I prepared a patch that tries to fix it:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197275

Marko: Can you test wether it works for you ?

-- 
pi@opsec.eu            +49 171 3101372                         5 years to go !