Any ideas on what I'm doing wrong with my recompile? What file is it
looking for? I thought libgdm.so would be the one.
Thanks!
Jen
On Sun, 2002-03-24 at 09:35, jennyw wrote:
Thanks! That was one problem. Another is that it seems that the version
of courier-imapd that Debian packages doesn't use BerkeleyDB ... arg.
Maybe it's using gdbm. Unfortunately, I have libgdbm.so installed
(1.7.3) in /usr/lib and I guess that's not what it's looking for? Or
it's in the wrong place? Any ideas on what I could be using instead?
On Sunday, March 24, 2002, at 07:23 AM, Sam Varshavchik wrote:
On Sat, 23 Mar 2002, je...@dangerousideas.com wrote:
I tried doing "apt-get source maildrop" (debian's way to download
source) and then "./configure --with-db=db --enable-userdb". Then
"make"
and "make install". The resulting maildrop also seems to ignore userdb.
I then downloaded the latest maildrop from sourceforge and the same
thing happened.
Clearly I'm missing something here -- how do I tell maildrop to use
userdb? How do I tell it where userdb lives?
It's possible that debian's port of courier-imap modifies the default
location of the userdb database. The distributed tarballs of both
maildrop and courier-imap use /etc/userdb*. It's possible that debian's
courier-imap port either does not enable userdb by default, or uses some
other file path. Check the port's patches for more information.
3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Help! Can't get maild...
