I'm trying to compile cyrus imap so that I can use sieveshell with my MIT account, which uses kerberos 4. I'm able to get everything compiled and running, but I can't connect to the server. When I packet sniff, I get the greeting message and a logout message, and nothing else. I think what's happening (from looking at the imap source) is that it's finding that it can't do any of the protocols, and quitting. I'm at a total loss as to why this would be happening, and would really appreciate anyone's help. Here's the relevant information:
david@laptop i686-linux $ /usr/athena/bin/klist Ticket file: /tmp/tkt1000 Principal: [EMAIL PROTECTED] Issued Expires Principal Feb 6 03:23:04 Feb 6 13:23:04 [EMAIL PROTECTED] david@laptop cyrus-imapd-2.1.12 $ CPPFLAGS="-L/usr/athena/lib/" LDFLAGS="-L/usr/athena/lib/" ./configure '--prefix=~/imapd/' '--exec-prefix=~/imapd/' '--with-cyrus-prefix=~/imapd/' --with-krb=/usr/athena/ --enable-statickrb creating cache ./config.cache checking host system type... i686-pc-linux-gnu checking for makedepend... makedepend *SNIP* checking for sigvec... yes checking for res_search in -lresolv... (cached) yes checking for des_ecb_encrypt in -ldes... yes checking for Kerberos includes... /usr/athena//include checking for krb.h... yes checking for krb_mk_priv in -lkrb... yes checking for RSAPublicEncrypt in -lrsaref... no checking for BIO_accept in -lcrypto... yes david@laptop cyrus-sasl-2.1.12 $ ./configure --prefix=~/imapd/ --exec-prefix=~/imapd/ --with-cyrus-prefix=~/imapd/ --with-krb=/usr/athena/ --enable-statickrb loading cache ./config.cache checking host system type... i686-pc-linux-gnu checking for a BSD compatible install... (cached) /bin/install -c checking whether build environment is sane... yes *SNIP* checking SRP... disabled checking for res_search in -lresolv... (cached) yes checking for krb.h... (cached) yes checking for com_err in -lcom_err... (cached) yes checking for krb_mk_priv in -lkrb... (cached) yes checking for krb_get_err_text... (cached) yes checking KERBEROS_V4... enabled checking for gssapi.h... (cached) no checking for gssapi/gssapi.h... (cached) no configure: warning: Disabling GSSAPI checking GSSAPI... disabled checking for crypt... (cached) no So, as far as I can tell, it's enabling Kerberos 4 in SASL and IMAP, but it doesn't seem to be actually using it. I'd be happy to provide any more debugging information that would be useful, but at this point, I don't know what is useful and what isn't. Thank you *so* much in advance! -- -David Ziegler [EMAIL PROTECTED]
