I run Cyrus on sid, and I see tons of stuff in /usr/lib/sasl2 "IMPLEMENTATION" "Cyrus timsieved v2.1.18-IPv6-Debian-2.1.18-2.0.1" "SASL" "PLAIN GSSAPI DIGEST-MD5 NTLM LOGIN CRAM-MD5" "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational regex"
as you can tell, where they should be. * OK desolation.livid.dk Cyrus IMAP4 v2.1.18-IPv6-Debian-2.1.18-2.0.1 server ready C01 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE AUTH=GSSAPI AUTH=DIGEST-MD5 AUTH=NTLM AUTH=CRAM-MD5 ANNOTATEMORE C01 OK Completed Long story short, this is how your Cyrus should respond, port 143 on the 2nd, port 2000 on the first. All I had to do is tweak imapd.conf, nothing more. On Sat, 29 Oct 2005 12:15:00 -0700 (PDT) > > On Sat, 29 Oct 2005, Ken Murchison wrote: > > > Andrew Morgan wrote: > >> > >> I've been trying to setup timsieved on my test cyrus box (v2.2.12), > >but I > seem to be missing something, probably obvious. > >> > >> I have a working installation of cyrus with imap, imaps, and lmtp. > >I use > saslauthd. I added a stanza for timsieved in cyrus.conf, > >and I can > successfully telnet to the sieve port. sivtest returns > >the following: > > >> --------------------------------------------- > >> [EMAIL PROTECTED] config]# sivtest -a cyrus localhost > >> S: "IMPLEMENTATION" "Cyrus timsieved v2.2.12" > >> S: "SIEVE" "fileinto reject envelope vacation imapflags notify > >subaddress > relational comparator-i;ascii-numeric regex" > >> S: "STARTTLS" > >> S: OK > >> Authentication failed. generic failure > >> Security strength factor: 0 > >> --------------------------------------------- > >> > >> It never asks me for a password, and I appear to be missing a SASL > >> capabilities line following the IMPLEMENTATION line. I don't know > >why > sieve isn't detecting my sasl settings from imapd.conf. Here > >are my sasl > settings: > > > > If you try imtest, do you get any AUTH=<mech> capabilities (I'm > > guessing not). I'm sure its detecting your SASL settings, but its > > not finding your SASL plugins. Where did you install them? If > > they aren't in /usr/lib/sasl2, you can just make a symlink from > > directory to directory. > > I don't see an AUTH=<mech> capabilities with imtest. I'm using the > Debian sarge libsasl2 package, which installed libsasldb libraries in > > /usr/lib/sasl2/. However, I am using 'saslauthd -a pam', so I don't > expect it to be looking for the sasl plugins anyways. > > Andy > ---- > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > > !DSPAM:4363d3ec297094190714843! > > -- "What does one want when one is engaged in the sexual act? That everything around you give you its utter attention Think only of you, care only for you... Every man wants to be a tyrant when he fornicates" ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html