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([EMAIL PROTECTED]): Disconnected: > > Logged out > > dovecot: Apr 09 04:55:08 Info: managesieve-login: Login: > > user=<[EMAIL PROTECTED]>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS > > dovecot: Apr 09 04:55:08 Info: MANAGESIEVE([EMAIL PROTECTED]): Effective > > uid=1001, gid=1001 > > dovecot: Apr 09 04:55:08 Info: MANAGESIEVE([EMAIL PROTECTED]): sieve > > storage: Using active sieve script path: > > /usr/local/virtual/[EMAIL PROTECTED]//.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 [EMAIL PROTECTED] 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.
signature.asc
Description: This is a digitally signed message part