Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 May 2005 19:38:32 -0700
From:      "greg@grokking.org" <greg@grokking.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Cyrus IMAP from Ports in 5.X?
Message-ID:  <428AAAA8.6060805@grokking.org>
In-Reply-To: <20050517220403.T96779@zoraida.natserv.net>
References:  <20050517220403.T96779@zoraida.natserv.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Francisco Reyes wrote:
> Anyone got Cyrus IMAP working from installing the ports?
> 
> After 3 days trying.. I am leaning towards possible problems with the
> ports options. For example upon installation the cyrus-sasl-2.1.20_1
> port there are errors in /var/log/auth.log
> 
> May 16 23:47:39 testpompa saslpasswd2: setpass succeeded for cyrus
> May 16 23:47:39 testpompa saslpasswd2: Couldn't update db
> 
> Runing saslapsswd produces the same, yet running sasldblistusers2 I see
> cyrus@localhost: userPassword
> 
> My imapd.conf is
> configdirectory: /var/imap
> partition-default: /var/imap/spool
> servername: testpompa.natserv.net
> allowanonymouslogin: no
> admins: cyrus root
> autocreatequota: 102400
> loginrealms: stringsutils.com, dataeverywhere.net
> sieveusehomedir: false
> sievedir: /var/imap/sieve
> sasl_pwcheck_method: auxprop
> lmtpsocket: /var/imap/socket/lmtp
> idlesocket: /var/imap/socket/idle
> notifysocket: /var/imap/socket/notify
> virtdomains: yes
> defaultdomain: stringsutils.com
> 
> The "Couldn't update db" seems like a common problem when installing
> Cyrus, yet I could not find a single reference on how to fix the problem.
> 
> Ran the mkimap without any problems. Both the impad and sasl programs
> are running and no errors reported at startup for either of them.
> 
> Moreover, I tried using a different Berkeley DB with cyrus-sasl and
> after that got different errors, so I am wondering if the default
> options in the port may be wrong.


Are you running both sasl AND sasl2 ports at the same time?
sasldblistusers2 is from sasl2 and saslpasswd is from sasl.
If that was just a typo, check permissions on /usr/local/etc/sasldb
(or /usr/local/etc/sasldb2) and make sure it allows reading by the
user running your pop/imap/mta.

G



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?428AAAA8.6060805>