On Tue, 2007-04-03 at 14:55 +0530, JOYDEEP wrote: > Rudy Gevaert wrote: > > JOYDEEP wrote: > >> Dear list, > >> > >> after implementing the imaps , I need to configure sieve to start > >> STARTTLS. > >> > >> sivtest -a aftab -u aftab linux.kolkatainfoservices.in -m LOGIN -t > >> "" > >> > >> is working well. is there any config file for sieve so that I can force > >> sieve to start STARTTLS ? bcoz I am using sieve from a web-based email > >> client called felamimail. > > > > I'm not sure what you are trying to say, because it is the client that > > has to issue STARTTLS, and not the server. The server just advertises > > his capabilities. E.g. TLS > > OK Rudy, thanks for your hints. I think I must be more verbose here. > > I have imaps. whenever I try to use sieve from felamimail web mail > client it reports > > ------------------------------------------------------- > Apr 3 14:51:12 linux slapd[4169]: conn=727 op=0 RESULT tag=97 err=0 text= > Apr 3 14:51:12 linux master[10304]: about to exec > /usr/lib/cyrus/bin/timsieved > Apr 3 14:51:12 linux sieve[10304]: executed > Apr 3 14:51:12 linux sieve[10304]: accepted connection > Apr 3 14:51:12 linux sieve[10304]: badlogin: > linux.kolkatainfoservices.in[127.0.0.1] PLAIN encryption needed to use > mechanism Sorry for interruption ;) In the log you can see that: 1. Using sivtest with LOGIN mechanism and TLS you are able to connect to timsievd. (IT IS NOT IMAP - SIEVE !=IMAP). 2. Using PLAIN mechanism and with NO TLS the felamimail failed to connect to timsievd. It says to you: If you want PLAIN then encryption is required Conclusion: You need to configure __felamimail__ to use STARTTLS for sieve connections. On the cyrus side everything is OK (so far). Regards, Olaf -- Olaf Fraczyk <olaf@xxxxxxx> NAVI ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
