- dovecot - dovecot.org

[Dovecot] Summerising users subfolders imap logs?
by Sysadmin 11 Aug '06

11 Aug '06

Hello. Migrating from pop3 to imap I have now situation, that every user has a lot sub folders, for example 100 sub folders and now every mail check writes in the mail log also login/logout log for every sub folder: dovecot: Jul 11 16:16:31 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:31 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:31 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:32 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:32 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:32 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:32 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:32 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:32 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:32 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:33 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:33 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:33 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:33 Info: IMAP(anti): Disconnected dovecot: Jul 11 16:16:33 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:33 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:34 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:34 Info: IMAP(anti): Disconnected in IDLE dovecot: Jul 11 16:16:34 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:34 Info: IMAP(anti): Disconnected: Logged out dovecot: Jul 11 16:16:35 Info: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS dovecot: Jul 11 16:16:35 Info: IMAP(anti): Disconnected in IDLE etc. So maillogs are full thiskind of stuff. But as I cant see here which subfolder the user access, so is it possible to summerise somehow this per users mass logging witth one row, something like: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS, accessed 100 folders, or just: imap-login: Login: anti, [192.168.20.1], PLAIN, TLS Or someting else? Any idea to make this happend? -- Sysadmin

5 8

[Dovecot] Login process died too early - shutting down
by Bilal Ahmed Mazhar 11 Aug '06

11 Aug '06

Hi I installed dovecot-1.0.rc6.tar.gz on Fedora - 5 (i86) with MySQL - 5.0.24 to authenticate pop3 & imap requests. But dovecot doesn't start properly. I got below error from error log Error: Login process died too early - shutting down Error: Child 2521 (login) killed with signal 11 Please help me to sort out this problem as early as possible. Regards, Bilal Ahmed

2 1

[Dovecot] [PATCH]
by Johannes Berg 11 Aug '06

11 Aug '06

This patch makes it possible to use a negative offset to count from the end of a variable. Signed-off-by: Johannes Berg <johannes(a)sipsolutions.net> --- dovecot-1.0.rc2/doc/variables.txt 2006-04-12 09:39:31.000000000 +0200 +++ dovecot-1.0.rc2.mod/doc/variables.txt 2006-07-19 19:27:15.611041184 +0200 @@ -35,7 +35,10 @@ You can take a substring of the variable by giving optional offset followed by '.' and width after the '%' character. For example %2u gives first two characters of the username. %2.1u gives third character of the username. If -offset points outside the value, empty string is returned. +the offset is negative, it counts from the end, for example %-2.02i gives +the UID mod 100 (last two characters of the UID printed in a string). If a +positive offset points outside the value, empty string is returned, if a +negative offset does then the string is taken from the start. For login_log_format_elements there are also these variables: --- dovecot-1.0.rc2/src/lib/var-expand.c 2006-04-12 09:39:32.000000000 +0200 +++ dovecot-1.0.rc2.mod/src/lib/var-expand.c 2006-07-19 19:35:25.821041184 +0200 @@ -11,7 +11,8 @@ #include <stdlib.h> struct var_expand_context { - unsigned int offset, width; + int offset; + unsigned int width; }; struct var_expand_modifier { @@ -109,6 +110,7 @@ const char *(*modifier[MAX_MODIFIER_COUNT]) (const char *, struct var_expand_context *); unsigned int i, modifier_count; + int sign = 1; bool zero_padding = FALSE; memset(&ctx, 0, sizeof(ctx)); @@ -120,12 +122,16 @@ /* [<offset>.]<width>[<modifiers>]<variable> */ ctx.width = 0; + if (*str == '-') { + sign = -1; + str++; + } if (*str == '0') { zero_padding = TRUE; str++; } while (*str >= '0' && *str <= '9') { - ctx.width = ctx.width*10 + (*str - '0'); + ctx.width = ctx.width*10 + sign * (*str - '0'); str++; } @@ -178,9 +184,21 @@ if (var != NULL) { for (i = 0; i < modifier_count; i++) var = modifier[i](var, &ctx); - while (*var != '\0' && ctx.offset > 0) { - ctx.offset--; - var++; + if (ctx.offset < 0) { + /* if offset is < 0 then we want to + * start at the end */ + size_t len = strlen(var); + var += len; /* point to trailing NUL byte */ + while (ctx.offset < 0 && len > 0) { + ctx.offset++; + var--; + len--; + } + } else { + while (*var != '\0' && ctx.offset > 0) { + ctx.offset--; + var++; + } } if (ctx.width == 0) str_append(dest, var); @@ -205,7 +223,7 @@ const struct var_expand_modifier *m; /* [<offset>.]<width>[<modifiers>]<variable> */ - while (*str >= '0' && *str <= '9') + while ((*str >= '0' && *str <= '9') || *str == '-') str++; if (*str == '.') {

4 4

[Dovecot] vacation messages (dovecot lda cmusieve)
by Rene Luria 11 Aug '06

11 Aug '06

Hi, I am experiencing some problems with vacation messages feature. Using dovecot from alpha4 to 1.0.rc6 with lda from cvs, when setting up a vacation message, there is a parameter ":days" which specifies the interval between auto-reply messages. After the first reply, should wait that amount of days before sending a new reply to the same sender. The list of sender addresses is to be kept in $maildir/.dovecot.lda-dupes Now, what happens is that at random intervals, auto-replies are sent. It happens with any account, from thirty minutes to one hour maybe. How is it possible ? How to fix it ?

1 0

[Dovecot] Pb with ssl_disable in 1.0RC6
by Laurent Papier 11 Aug '06

11 Aug '06

Hi, I have a problem after upgrading dovecot 1.0rc1 to 1.0rc6. I don't use SSL at all so I have 'ssl_disable = yes' in my configuration. This works fine in 1.0rc1 but dovecot 1.0rc6 failed to start with the following error message "dovecot: Login process died too early - shutting down". Setting 'ssl_disable = no' resolves the problem but now dovecot announce TLS capability which is not what I want. Any suggestion ? -- Laurent Papier - 03 88 75 80 50 Admin. système - SdV Plurimedia - <http://www.sdv.fr/>

3 3

Re: [Dovecot] imap-login (proxy) Connection queue full
by Bill Boebel 11 Aug '06

11 Aug '06

On Thu, August 10, 2006 11:15 pm, Bill Boebel <bill(a)webmail.us> said: > On Thu, August 10, 2006 5:22 pm, Timo Sirainen <tss(a)iki.fi> said: > >>> Aug 10 16:23:34 director5 dovecot: imap-login: Disconnected: Connection queue >>> full: >>> >>> I am seeing this logged several times per minute. From netstat, the server has >>> 650 proxied IMAP connections and 450 proxied IMAPS connections, there are >>> currently 10 imap-login processes running, and using the following config: >> >> I did some changes to CVS which hopefully should fix this? > > It is still disconnecting with "Connection queue full", although less frequently. > Testing with about 315 IMAP connections right now and same config as earlier > today, so it should never hit this condition, right? > > The weird thing is sometimes when I am testing via telnet, my session encounters > this condition and disconnects within the first 5 seconds. It does this with and > without these patches. Here is another symptom: The number of IMAP connections drops steeply repeatedly ever 30 seconds or so. It does this only with the latest CVS (dovecot-20060811), not with the version I was testing previously (dovecot-20060808). These were taken about 2 seconds apart: # netstat -an | grep -c "192.168.1.69:143.*ESTA" 85 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 108 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 108 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 114 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 52 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 73 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 80 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 85 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 89 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 99 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 105 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 114 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 122 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 135 # netstat -an | grep -c "192.168.1.69:143.*ESTA" 32 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 67 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 69 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 74 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 83 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 88 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 95 # netstat -an | grep -c "192.168.1.69:993.*ESTA" 48 # lsof -nu dovecot |wc -l 616 # lsof -nu dovecot |wc -l 665 # lsof -nu dovecot |wc -l 690 # lsof -nu dovecot |wc -l 687 # lsof -nu dovecot |wc -l 706 # lsof -nu dovecot |wc -l 713 # lsof -nu dovecot |wc -l 735 # lsof -nu dovecot |wc -l 767 # lsof -nu dovecot |wc -l 803 # lsof -nu dovecot |wc -l 853 # lsof -nu dovecot |wc -l 891 # lsof -nu dovecot |wc -l 910 # lsof -nu dovecot |wc -l 933 # lsof -nu dovecot |wc -l 958 # lsof -nu dovecot |wc -l 575 # lsof -nu dovecot |wc -l 620 # lsof -nu dovecot |wc -l 629 # lsof -nu dovecot |wc -l 669 # lsof -nu dovecot |wc -l 701

1 0

Re: [Dovecot] Suggestion for dovecot default SSL configuration...
by Timo Sirainen 11 Aug '06

11 Aug '06

On Mon, 2006-07-24 at 13:48 -0700, Douglas Moore wrote: > First off, thanks for the effort on this software, it's a world > better than the uw-imap that I used to have to deal with... > > This isn't a bug report per se, but rather a response to something > that came up during some recent security scans. Given that SSLv2 > has it's share of issues, I'd like to suggest that you remove it from > the default ciphers supplied with the source distribution. A > simple :!SSLv2 added to the default cipher list would aid in the > overall security of the package. I'm not an expert in SSL, so I'd rather be sure that it's actually more helpful than harmful. Does something still use SSLv2? If I do the change, I guess the only thing it does is to break those clients that still try to use it? Is its security already bad enough that it's just better to break them?

1 0

[Dovecot] SSL CRL checking
by Timo Sirainen 11 Aug '06

11 Aug '06

Is there a reason that CRL is required to exist in the ssl_ca_file? Could it just use it only if it's there, but otherwise ignore it? Or is this a bad idea? Is it even possible at all to tell that to OpenSSL?

1 0

[Dovecot] Seeing dovecot crash under rc6, seems to go almost exactly every 2.5 hours...
by Dean Blackburn 11 Aug '06

11 Aug '06

We're getting the following crash report, but I'm not sure it contains anything immediately useful (especially since we're running on a minority platform in OS X)... Anyone see where we might be able to resolve this? The crash doesn't kill existing imap processes, but dovecot/imap-login needs to be restarted. ********** Host Name: mailserver Date/Time: 2006-08-10 14:24:16.131 -0700 OS Version: 10.4.6 (Build 8I127) Report Version: 4 Command: dovecot Path: /opt/local/sbin/dovecot Parent: dovecot [10099] Version: ??? (???) PID: 13818 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020 Thread 0 Crashed: 0 dovecot 0x0000482c log_set_prefix + 36 (log.c:190) 1 dovecot 0x000070b0 create_mail_process + 1576 (mail-process.c:535) 2 dovecot 0x00005150 auth_master_callback + 96 (login-process.c:92) 3 dovecot 0x00002d9c auth_process_input + 460 (auth-process.c:121) 4 dovecot 0x00017d58 io_loop_handler_run + 388 (ioloop-select.c:140) 5 dovecot 0x0001006c io_loop_run + 48 (ioloop.c:273) 6 dovecot 0x00008c54 main + 1816 (main.c:577) 7 dovecot 0x000020a8 _start + 344 (crt.c:272) 8 dovecot 0x00001f4c start + 60 Thread 0 crashed with PPC Thread State 64: srr0: 0x000000000000482c srr1: 0x100000000200d030 vrsave: 0x0000000000000000 cr: 0x84002404 xer: 0x0000000020000000 lr: 0x0000000000004810 ctr: 0x00000000901313a0 r0: 0x00000000000070b0 r1: 0x00000000bffff320 r2: 0x0000000000024810 r3: 0x0000000000000000 r4: 0x000000000006f380 r5: 0x0000000000000001 r6: 0x0000000000000000 r7: 0x0000000000000002 r8: 0x000000006b690073 r9: 0x000000000006f104 r10: 0x00000000bffff310 r11: 0x0000000000020b3c r12: 0x000000000006f399 r13: 0x00000000ffffffff r14: 0x0000000000000000 r15: 0x0000000000000000 r16: 0x000000000006f113 r17: 0x000000000006f228 r18: 0x0000000000000000 r19: 0x000000000006f0fc r20: 0x0000000000000014 r21: 0x000000000001b0c0 r22: 0x000000000000041a r23: 0x000000000001b0c0 r24: 0x00000000018006e8 r25: 0x000000000001bfe0 r26: 0x000000000006f133 r27: 0x000000000006f2a8 r28: 0x000000000006f380 r29: 0x0000000000000000 r30: 0x0000000024002422 r31: 0x0000000000004810 Binary Images Description: 0x1000 - 0x1ffff dovecot /opt/local/sbin/dovecot 0x8fe00000 - 0x8fe51fff dyld 44.4 /usr/lib/dyld 0x90000000 - 0x901bbfff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x90213000 - 0x90218fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib 0x936d1000 - 0x936f2fff libmx.A.dylib /usr/lib/libmx.A.dylib

3 2

[Dovecot] dovecot process no longer dies
by Ceasar V. Navato, Jr. 11 Aug '06

11 Aug '06

Bill, After applying the patch from http://dovecot.org/list/dovecot-cvs/2006- August/006209.html, my dovecot rc6 is finally working. Thank you very much for the info. Regards, -- Ceasar V. Navato, Jr.

1 0