3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] imap on Solaris
FromSent OnAttachments
Gjermund SorsethOct 4, 2000 3:20 am 
Mike JacksonOct 4, 2000 4:46 am 
Leonid AndreevOct 4, 2000 10:19 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] imap on SolarisActions...
From:Mike Jackson (jack@ssh.com)
Date:Oct 4, 2000 4:46:52 am
List:net.sourceforge.lists.courier-users

On Wed, 04 Oct 2000, you wrote:

I'm looking into using the courier imap server on Solaris 2.6 at the moment, and my conclusion so far is that it is unusable due to the configure error mentioned in the FAQ:

checking if wait function is broken... yes configure: error: I give up -- neither wait nor wait3 works properly configure: error: ./configure failed for waitlib

The latest recommended patches do not help. Does anyone have more information on this issue?

Just use the --with-waitfunc=wait3 configure flag. I have it running on my Solaris 8 box and it's been in testing for a couple of weeks now, and I haven't had one problem. If you want that specific patch that "supposedly" corrects this, you have to buy service from Sun. Everything seems to be working fine with my server; I've been pumping several hundred messages a day into it and reading with various clients. The one main problem that was keeping me from considering production use was the inability to restart courier 1.0 if imap clients were still open -- "unable to bind address", but this is eliminated with 1.1.

Mike