Hello dovecot users, I have finally updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. Also, I included a proxy implementation based on imap-proxy.c. This patch is designed for dovecot release 1.0.2 and it will not apply cleanly to the 1.1 versions yet. Change Log V5 ------------- - Applied patch by Uldis Pakuls to fix master_dump_settings bug - Added some compilation/installation info to the README - Moved README to source tree's root as README.managesieve - Fixed minor error handling bug in sieve_storage.c with respect to a missing root directory. - Now sieve capabilities are reported as they are specified by the implementing library and not in forced upper case. The sieve RFC now explicitly states that sieve capability identifiers are case-sensitive. This broke compatibility with SquirrelMail/Avelsieve. - Disabled ANONYMOUS login entirely until proper support is implemented. V4 claimed to do so as well, but in fact it only stopped announcing it. - Implemented managesieve-proxy. It is not so much a clean copy of imap-proxy, since the managesieve greeting is much more complex and requires parsing. Configuration is identical to imap-proxy. This seems to be a little under-documented however (http://wiki.dovecot.org/PasswordDatabase/ExtraFields). This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html). Current plans include merging src/lib-managesieve with src/lib-imap, updating the patch for dovecot-1.1 and fixing any problems you might find. The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.2-MANAGESIEVE-v5.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Notify me when there are problems. Regards, -- Stephan Bosch stephan at rename-it.nl IRC: Freenode, #dovecot, S[r]us
Stephan Bosch wrote:> I have finally updated the MANAGESIEVE patch to fix the currently known > small problems with the protocol implementation. Also, I included a > proxy implementation based on imap-proxy.c. This patch is designed for > dovecot release 1.0.2 and it will not apply cleanly to the 1.1 versions > yet.Thank you Stephan !
On Tuesday 31 July 2007 01:41:11 Stephan Bosch wrote:> Have fun testing the patch. Notify me when there are problems.Hello Stephan, I still get the following message when trying to connect and authenticate: Choose a different authentication method to PLAIN. The same with LOGIN when I tell Dovecot to use the login authentication method. The logs show: Aug 1 15:25:52 hostname dovecot: managesieve-login: Login: user=<username>, method=PLAIN, rip=aa.bb.cc.dd, lip=ww.xx.yy.zz, TLS Aug 1 15:25:52 hostname dovecot: MANAGESIEVE(username): Disconnected: Logged out I am using real Unix users and Dovecot is configured with authdb pam and userdb passwd. I previously described the problem in [1]. Does your patch not support PLAIN or LOGIN or am I missing something? TIA Andreas [1] http://www.dovecot.org/list/dovecot/2007-June/023283.html -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: <http://dovecot.org/pipermail/dovecot/attachments/20070801/69f7de28/attachment-0002.bin>
On Wed, 2007-08-01 at 15:27 +0200, Andreas Ntaflos wrote:> On Tuesday 31 July 2007 01:41:11 Stephan Bosch wrote: > > Have fun testing the patch. Notify me when there are problems. > > Hello Stephan, > > I still get the following message when trying to connect and authenticate: > > Choose a different authentication method to PLAIN. > > The same with LOGIN when I tell Dovecot to use the login authentication > method. The logs show: > > Aug 1 15:25:52 hostname dovecot: managesieve-login: Login: user=<username>, > method=PLAIN, rip=aa.bb.cc.dd, lip=ww.xx.yy.zz, TLS > Aug 1 15:25:52 hostname dovecot: MANAGESIEVE(username): Disconnected: Logged > out > > I am using real Unix users and Dovecot is configured with authdb pam and > userdb passwd. I previously described the problem in [1]. > > Does your patch not support PLAIN or LOGIN or am I missing something?Could you give me some more information, i.e. your config, what client you test with and (if possible) a log of the connection. This way I can reproduce the situation. The managesieve patch should support all SASL mechanisms supported by dovecot. In fact, I only test using PLAIN. Most likely the problem relates to the fact that, unless configured otherwise, dovecot will refuse to use plain text SASL mechanisms if the connection is not encrypted. I haven't re-tested the STARTTLS command in the last versions... I will give it a go. Regards, Stephan
Stephan Bosch wrote:> Have fun testing the patch. Notify me when there are problems.Stephan, There's a small problem with your patch as it stands: it depends on a number of GCCisms, and fails to compile with, for example, Sun CC under Solaris 10. Removing all of your "__attribute__((unused))" declarations goes some way, but the build then fails with the following: /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/li b-storage -I../../src/lib-mail -I../../src/lib-sievestorage -I/app/openssl/0.9.7 m/include -g -c sieve-implementation.c -KPIC -DPIC -o .libs/sieve-implementatio n.o "sieve-implementation.c", line 193: void function cannot return value cc: acomp failed for sieve-implementation.c A reasonable error given that sieve_runenv_mark_duplicate() is a void function with a return :) Removing the "return" leads to a clean build, but it's not clear what implications that might have. NB: this is applied against dovecot-1.0.3, though only one of the hunks is off by 1 line. Regards, Robin
Maybe Matching Threads
- dovecot-2.0-pigeonhole/ManageSieve: wrong service name
- Latest MANAGESIEVE patch -- how to start daemon?
- managesieve & checkpassword authdb interface
- How to deal with mail to unknown virtual recipients?
- deliver can't connect to auth server at */usr/local*/var/run/dovecot/auth-master