Date: Thu, 4 Jan 2001 22:56:48 +0000
   From: Cillian Sharkey <[EMAIL PROTECTED]>

   Now for the problems: ;)

   Berkeley DB 3 on NetBSD (and similarly in FreeBSD) is installed as:
   /usr/pkg/lib/libdb3.a and /usr/pkg/include/db3/*.h so as not to
   conflict with the "native" db in NetBSD.

I'm not sure how I'm suppose to deal with this; I could be chasing db
files all around eternity.  I'd welcome patches.

   In configure I had to change db-3 to db3 and in some source files
   had to change includes for <db*.h> to <db3/db*.h>. This is for both
   IMAPD and SASL.  [Incidentally, I'm not using sasldb in SASL so is
   it truly necessary to compile both with the same DB version as is
   recommended?]

Sometimes mismatched db libraries cause crashes.  The documentation
could also say to compile libsasl without db support
(--with-dblib=none).

   For imapd I had to do CPPFLAGS="-I/usr/include/krb5
   -I/usr/include/openssl" before running configure to pick up include
   files. However some of the Makefiles under perl/ didn't "inherit"
   these CPPFLAGS, so I had to add the includes to the "INC" hash key
   in Makefile.PL as these seem to be (post-configure) generated
   Makefiles

If there are generic fixes for these problems, I'd love to have them.
(I don't really have time to chase this down right now.)

   - libwrap wasn't detected, even though it exists and works!
     /usr/lib/libwrap.a, /usr/lib/libwrap.so* and /usr/include/tcpd.h
     are there ok. passing --with-libwrap=/usr doesn't work either.

I think the next release will fix this.

   - configure has a problem with NetBSD's mmap() and warns:
     *** This system does not have a working mmap() Expect a
     *** considerable performance penalty

     Is this serious? The IMAP system will eventually have ~700
     accounts and at most 30 simultaneous IMAP sessions, with a
     'reasonable' volume of incoming mail via lmtpd.

For 30 simultaneous IMAP sessions it's not going to be a big deal.

     Would NetBSD's Unified Buffer Cache (not in 1.5) solve this?

Yes.

   - Do you recommend poll or idled for the "IDLE" method? How do
   these benefit the server/client if they make use of them?

Ken Murchison is the man for IDLE; I'll let him tackle this and then
argue with him about it.

   - Is ~700 accounts enough to warrant enabling "hashimapspool"? On
   the currentPOP3 system there is ~700 mail spoolfiles in /var/mail (FFS +
   soft updates) with no noticeable problems or complaints.

Probably doesn't matter.

   - With plaintext login [using pwcheck], cyradm asks for the
   password twice:
     first "Please enter your password:" then "IMAP Password:" - any
     reason why?

I'm not sure.  Has anyone else run across this?  Can anyone else solve
this?

   - Is it safe to make the same user cyrus runs as ("cyrus") part of
   the "admins" list in imapd.conf? Should I just create another user
   ("cyradm") for the sole purpose of this? (Yes I could use "root")

It's safe; the biggest worry would be your cyrus password being
compromised if you send it over the wire in cleartext.

[...]
   - What do people recommend for "distribution lists" in an IMAP
     environment:

     - Use a shared folder with an email alias for posting to it and
       then use ACLs to grant/deny people access the folder?
       Unfortunately, the Netscape MUA only checks "Inbox" for new
       mail so it's easy to miss new mail in other folders..

I thought there was a way of making Netscape check multiple folders.
Anyway, this is somewhat of a religious issue.  At CMU, we use shared
folders extensively; our production server has well over 20000 shared
mailboxes.

Larry

Reply via email to