[Dovecot] MANAGESIEVE patch v4 for dovecot 1.0.rc28 / problems

Robert Schetterer robert at schetterer.org
Tue Apr 10 18:16:38 EEST 2007

Hash: SHA1

Timo Sirainen schrieb:
> On Sun, 2007-04-08 at 16:10 +0200, Stephan Bosch wrote:
>> Robert Schetterer wrote:
>>> Hi,ok setui above works
>>> using avelsieve squirrelmail plugin
>>> with managesieve dovecot latest
>>> (perhaps i shouldnt use 1.30 rc)
>>> as well there may be other problems between suse and quotawarn patches )
>>> please see this just as info to help coders to debug
>>> following problems in logs appear
>>> /var/log/messages
>>> 9 04:51:41 suse10-2-vmware kernel: managesieve-log[2326]: segfault at
>>> 0000000000000000 rip 0000000000000000 rsp 00007fff8995b938 error 14
>>> i  have no idea where this comes from
>> Hmm. That's not good.. what ever happens, dovecot(-managesieve) must 
>> never segfault. Maybe you could provide a core-dump. Btw, I don't really 
>> know what managesieve-log is supposed to be. Timo, any ideas?
> Truncated managesieve-login most likely. Unfortunately it's really
> difficult to get login processes to produce core dumps. It's a lot
> easier to attach gdb into it while it's still running. First set:
> login_process_per_connection = no
> login_processes_count = 1
> Then you should have only one managesieve-login process. Then attach gdb
> into it:
> gdb attach `pidof managesieve-login`
> cont
> Then wait for it to crash and then give "bt full" command.
>>> /var/log/dovcot.info
>>> dovecot: Apr 09 04:55:00 Info: IMAP(tester at example.de): Disconnected:
>>> Logged out
>>> dovecot: Apr 09 04:55:08 Info: managesieve-login: Login:
>>> user=<tester at example.de>, method=PLAIN, rip=, lip=, TLS
>>> dovecot: Apr 09 04:55:08 Info: MANAGESIEVE(tester at example.de): Effective
>>> uid=1001, gid=1001
>>> dovecot: Apr 09 04:55:08 Info: MANAGESIEVE(tester at example.de): sieve
>>> storage: Using active sieve script path:
>>> /usr/local/virtual/tester at example.de//.dovecot.sieve
>>> ( this line looks strange to me, but it musnt be false )
>> That looks very strange. Assuming you are not using the userdb to 
>> specify the SIEVE path (code directly borrowed from dovecot-sieve), 'the 
>> problem' seems to be that the home directory of tester at example.de ends 
>> in a /. By looking at dovecot's home_expand code I discovered this is 
>> not checked while expanding ~/.dovecot.sieve. However, linux/unix/POSIX 
>> (?) seems to be handling duplicate slashes as single ones, so it should 
>> work properly anyhow. But, maybe Timo is interested in making some 
>> cosmetic changes. :)
> I do remove extra slashes in a couple of places, but here it's easier
> just to change userdb not to return the extra slashes. :) Anyway, like
> you said it should cause no problems.
Thx Timo,
i will wait for the new managesieve patch
to do more testings, perhaps version dovecot stable 1 will be out there too

- --
Mit freundlichen Gruessen
Best Regards

Robert Schetterer

Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org


More information about the dovecot mailing list