Just out of curiosity, what OS are U using. I bet that this would work
directly out of the box from FreeBSD ports (Those guys/gals are good!) But
trying to do this on Solaris 8 x86 which is highly proprietary and u have to
basically reconfigure and unproprietarize (I guess this on on of those Jesse
Jackson made up words) the box.
The berkeley libs are not found here either but I assume that this is not a
problem because U can use gdbm or ndbm. But its strange that in my
LD_LIBRARY_PATH includes /usr/local/Berkeley3.1...
The authentication mechanism in my case are not found by configure because I
had to change the library names to support Mit krb5-121, such as -lkrb
and -ldes are named -ldes425 -lkrb4. Routines such as the ecb_encrypt() are
in the mit libs but they are not named properly. But after rewriting the
configure script and it find the libs the authentication mechanisms are not
enabled when running imtest.
Other libraries such as libcrypt from openssl are found after doing the
above procedure (putting my /usr/local/ssl in LD_LIBRARY_PATH) but those
authentication mechanisms are not enabled in imtest.
Using Cyrus-imapd 1.6.4 and cyrus-sasl. The 2.0.9 didn't compile. Will try
the new version.
Will try again
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Chuck Dale
Sent: Wednesday, February 14, 2001 7:55 AM
To: [EMAIL PROTECTED]
Subject: Re: Ahhh!! Pulling my hair out over imapd/sasl configure!
Wrote dglynn on Tue, Feb 13, 2001 at 10:31:45PM -0500:
> Ok, I REALLY need this server up and running but I can't
> get the authentication right!
Hey! Sounds just like me over the past month.
> imtest doesn't work either! Does ANYONE on this list have a clue
> on how to "simply" use sasldb? Configure options would help...
<FrustratedRant>
Here are some of the problems I've had:
* configure doesn't find Berkeley DB even when it's apparently
installed in a standard system location (hello RedHat)
* there is almost *no* common ground between the source and the
various packages included with Linux distributions.
i.e:
I run Debian at home: The Debian maintainers appear to have
haxored all over Cyrus to make it play how they want it to. Yet
that isn't how the normal defaults work.
I run RedHat 7.0 on my development server: And so I grab the
included Cyrus 2. Which of course works totally differently to the
other versions I've been using.
I run RedHat 6.2 on my main hosting server: Good luck trying to
get Cyrus 2 running on that! And even the RPMS that RedHat put out
with PowerTools are buggy.
Between all of these distributions hardly any of the default
configurations were similar. And it never worked without a lot of
coaxing.
* strace is your friend for tracking the voodoo that SASL does
trying to authenticate.
One moment it's reading Cyrus.conf, another it's reading
imapd.conf.
Then the maintainers forget to make the /etc/sasldb file readable
by group mail.
* Getting Postfix to play with Cyrus is not difficult but the
documentation sucks. The default transport map line included with
my currently installed version of Postfix doesn't work. So I
search the net to find people with the same problem and find two
different answers neither of which seem to work.
Worked finally..
* There is *no* easy way to make Cyrus listen on a certain IP
address. Surely this would be a common thing for people testing it
before moving from UW or testing a new version?
I got out my C cluelessness and haxored away at the code for about
10 minutes and managed to modify the call to bind() in master.c
but could there be a configuration option to set the interface to
bind to?
* The build process appears to be very brittle and managed to break
whenever the system wasn't perfect as expected. The idea of a
configure script is that it is reasonably clued up and can look
for "libdb3" instead of the nonstandard "libdb-3".
</FrustratedRant>
Sorry to sound ungrateful and abusive. I'm very grateful for Cyrus.
Hey! Maybe even I should put in a hand to help with some of this stuff..
Whoa..
Chuck
[ [EMAIL PROTECTED] ]
