From owner-freebsd-ports@FreeBSD.ORG  Sun Jan 16 18:25:55 2005
Return-Path: <owner-freebsd-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 17CAB16A4CE
	for <ports@freebsd.org>; Sun, 16 Jan 2005 18:25:55 +0000 (GMT)
Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A479043D5A
	for <ports@freebsd.org>; Sun, 16 Jan 2005 18:25:54 +0000 (GMT)
	(envelope-from clint@0lsen.net)
Received: from 0lsen.net ([24.20.127.157])
          by comcast.net (sccrmhc11) with ESMTP
          id <20050116182553011000k5tce>; Sun, 16 Jan 2005 18:25:54 +0000
Received: by 0lsen.net (Postfix, from userid 1001)
	id 6C8C1179F9; Sun, 16 Jan 2005 10:25:53 -0800 (PST)
Date: Sun, 16 Jan 2005 10:25:53 -0800
From: Clint Olsen <clint@0lsen.net>
To: ports@freebsd.org
Message-ID: <20050116182553.GA19411@0lsen.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Organization: NULlsen Network
X-Disclaimer: Mutt Bites!
Subject: Courier-imap upgrade broke me going to 4.0
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Sun, 16 Jan 2005 18:25:55 -0000

I just knew I shouldn't have screwed around with this, but I just had to be
up to date, and now I got burned.

It looks as if the SSL variable for rc.conf changed to
courier_imap_imapd_ssl_enable.  Nice...

Does authdaemond need to be started?  I tried running it, but it complained
about a missing file - /usr/local/sbin/courierlogger.  I can't find any
documentation on why this is missing.

So, I have couriertcpd listening on ports 993 and 143, but I can't get
a client now to talk to the server.

Maybe it's just me, but I find this proram really irritating.  It was a
bitch to get 3.X up and running correctly, and now I'm finding myself
trying to sift through scant documentation getting 4.X moving.  Actually, I
need to correct myself.  There is a lot of documentation.  It's just that
none of it seems to help me get courier-imap up and running correctly.

-Clint