On Tue, Feb 24, 2004 at 01:49:39PM -0600, Albert Chin wrote:
> On Tue, Feb 24, 2004 at 10:55:51AM -0600, Albert Chin wrote:
> > $ telnet [host] 2000
> > "IMPLEMENTATION" "Cyrus timsieved v2.2.3"
> > "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational
> > regex"
> > OK
> >
> > Any reason I don't see the SASL auth mechanisms? Cyrus IMAPd is
> > working fine against saslauthd/pam. My main problem is that sieveshell
> > won't connect to [host] and I think the lack of displaying the SASL
> > auth mechanisms is the cause.
>
> BTW, imapd doesn't display the auth mechanisms either:
> $ telnet [host] imap
> a001 CAPABILITY
> * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS
> NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND
> BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE
> IDLE
Ok, I looked at the sieve_get_handle() function in
perl/sieve/managesieve/managesieve.xs. It errors out if no SASL auth
mechanisms are displayed:
mechlist=read_capability(obj);
if(!mechlist) {
globalerr = "sasl mech list empty";
XSRETURN_UNDEF;
}
So, that's definitely my problem. Anyone with ideas as to why I don't
see any auth mechanisms displayed? Should I query the cyrus-sasl
mailing list?
--
albert chin ([EMAIL PROTECTED])
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
