On Monday, April 1, 2002, at 11:52  PM, Michael Bartosh wrote:

> At 11:23 PM -0500 4/1/02, Kevin Bond wrote:
>>
>> I am having an odd problem using 2.1.3 in Mac OS X.
>
> Hi-
>
> You might try telling cyrus to sleep for 30-60 before you start it. 
> This worked for me with 2.0.16. Are you giving it its own startup item?
>
Here is the plist I use:

{
   Description   = "Cyrus IMAP server";
   Provides      = ("IMAP");
   Requires      = ("Resolver","NetInfo","Disks","Network","System Log");
   Uses          = ("Network Time");
   OrderPreference    = "Late";
   Messages =
   {
     start = "Starting Cyrus";
     stop  = "Stopping Cyrus";
   };
}

> Set the order to last, and make it require a late startup item.
>

I can't make it last, since I need the LMTP port to come up before 
sendmail or I will get delivery failures for queued messages.  I changed 
the sendmail plist to depend on IMAP to make this order correct.

>
> On another note:
>
> Is cyradm working for you?
>
Yes, cyradm works fine.

> If so, could you send me your --configure and build environment 
> (compiler flags, etc)? I'd greatly appreciate it.
>

I use the files from http://www.apache.org/~pier/macosx/ for OpenSSL, 
libtool, automake and autoconf.  I started using FINK but that turned 
out to be more trouble than it was worth.  The only thing I had to do to 
make cyradm work was fix the build command lines to include a -L option 
so that the sasl2 library was found.

The configuration lines are:

For sasl2.1.1:

./configure  --with-statissasl --enable-otp --disable-gssapi 
--enable-login --disable-krb4 --with-bdb-
libdir=/usr/local/BerkeleyDB.4.0/lib --with-bdb-
incdir=/usr/local/BerkeleyDB.4.0/include

For cyrus 2.1.3:

./configure  --with-dbdir=/usr/local/BerkeleyDB.4.0

Using Pier's glibtoolize makes sasl build just fine.  I did have to make 
some patches to cyrus 2.1.3 which I have attached.

Attachment: imap.diff
Description: Binary data




> I have to run 2.0.16 in order to use sasl 1.5.27, since 2.x doesn't 
> work with OpenLDAP yet- but maybe you've done something I'm missing, 
> since perl is perl, after all.
>

I am not currently using LDAP so I can't speak to the auxprop plugin 
issue for that.

Reply via email to