- dovecot - dovecot.org

[Dovecot] POP to IMAP Transition
by Yudhvir Singh Sidhu 14 Aug '06

14 Aug '06

I am using Dovecot IMAP and added an IMAP folder to an Outlook client which is also popping another account. Both account folders exist in the same client. I am wondering if I can drag the pop-ed mail to the IMAP folder, thereby transferring old mail to the IMAP folder? Outlook allows me to click and drag folders into the IMAP folder. You see where I am going with this, I wnat to transition from the old POP accounts to the new IMAP accounts and delete the old folders. Is this possible? I'd love to hear from someone who has done this. ======== Yudhvir Singh Sidhu Systems Administrator Industry-University Cooperative Research Program www.ucdiscoverygrant.org 2087 Addison Street, 2nd Floor Berkeley, CA 94720-3340 510 643 4039 fax 510 643 7839

3 2

[Dovecot] Dovecot fails to come up when using ACLs (1.0.b5)
by Jeff Turner 14 Aug '06

14 Aug '06

Hi, I just had a go at enabling ACLs with 1.0b5. As per the docs I've done the configuration bit: protocol imap { .. mail_plugins = acl } ... plugin { acl = vfile:/usr/local/etc/dovecot-acls } and created the dovecot-acls file. When I start dovecot, it hangs for a few seconds and dies with this: [root@redback root]# /etc/init.d/dovecot restart Shutting down IMAP daemon (/usr/local/sbin/dovecot1.0rc5): [ OK ] Starting IMAP daemon (/usr/local/sbin/dovecot1.0rc5): IEffective uid=65534, gid=65534 INamespace: type=private, prefix=, sep=/, inbox=yes, hidden=no, subscriptions=no Imaildir: data=/imap/mailboxes/dump-capability Imaildir: root=/imap/mailboxes/dump-capability, index=/imap/mailboxes/dump-capability, control=, inbox= INamespace: type=public, prefix=JiraSupport/, sep=/, inbox=no, hidden=no, subscriptions=no Imaildir: data=/imap/mailboxes/jira-support:CONTROL=/imap/mailboxes/dump-capability/shared-settings/jira-support/control:INDEX=/imap/mailboxes/dump-capability/shared-settings/jira-support/index Imaildir: root=/imap/mailboxes/jira-support, index=/imap/mailboxes/dump-capability/shared-settings/jira-support/index, control=/imap/mailboxes/dump-capability/shared-settings/jira-support/control, inbox= Elstat(/imap/mailboxes/jira-support/cur) failed: Permission denied [FAILED] there's a strange dump-capability mailbox created: [root@redback root]# ls -la /imap/mailboxes/dump-capability/ total 20 drwxrwx--- 5 nfsnobody nfsnobody 4096 Aug 4 19:59 . drwxr-xrwx 28 root mail 4096 Aug 4 19:59 .. drwxrwx--- 2 nfsnobody nfsnobody 4096 Aug 4 19:59 cur drwxrwx--- 2 nfsnobody nfsnobody 4096 Aug 4 19:59 new drwxrwx--- 2 nfsnobody nfsnobody 4096 Aug 4 19:59 tmp [root@redback root]# First I tried making /imap/mailboxes/jira-support/* world-readable, which fixes the 'Permisison denied' error. Dovecot still fails to come up. When I strace the process on startup, this is what it looks like: ...... open("/etc/passwd", O_RDONLY) = 3 fcntl64(3, F_GETFD) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fstat64(3, {st_mode=S_IFREG|0644, st_size=3091, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40016000 read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 3091 close(3) = 0 munmap(0x40016000, 4096) = 0 access("/usr/local/libexec/dovecot/imap", X_OK) = 0 access("/usr/local/lib/dovecot/imap", R_OK|X_OK) = 0 geteuid32() = 0 pipe([3, 4]) = 0 fcntl64(3, F_GETFD) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fcntl64(4, F_GETFD) = 0 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 dup(2) = 5 fcntl64(5, F_GETFD) = 0 fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 fork() = 16282 close(5) = 0 close(4) = 0 alarm(5) = 0 wait4(-1, IEffective uid=65534, gid=65534 INamespace: type=private, prefix=, sep=/, inbox=yes, hidden=no, subscriptions=no Imaildir: data=/imap/mailboxes/dump-capability Imaildir: root=/imap/mailboxes/dump-capability, index=/imap/mailboxes/dump-capability, control=, inbox= INamespace: type=public, prefix=JiraSupport/, sep=/, inbox=no, hidden=no, subscriptions=no Imaildir: data=/imap/mailboxes/jira-support:CONTROL=/imap/mailboxes/dump-capability/shared-settings/jira-support/control:INDEX=/imap/mailboxes/dump-capability/shared-settings/jira-support/index Imaildir: root=/imap/mailboxes/jira-support, index=/imap/mailboxes/dump-capability/shared-settings/jira-support/index, control=/imap/mailboxes/dump-capability/shared-settings/jira-support/control, inbox= 0xbfffcb7c, 0, NULL) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- +++ killed by SIGALRM +++ I tried chmod ugo+r'ing the /imap/dump-capability/ directory tree and it made no difference. I've attached my dovecot.conf, stripped of comments. Cheers, Jeff

2 2

Re: [Dovecot] dovecot tring to load sql modules
by Axel Thimm 14 Aug '06

14 Aug '06

On Sun, Aug 13, 2006 at 10:15:43AM -0700, Dean Gibson (Mail Administrator) wrote: > On 2006-08-13 02:50, Axel Thimm wrote: > >The fix is to _never_ use --nodeps in rpm and other package managers, and > >to simply add the mysql libs and ignore their presence. > > > >Unless you are setting up an embedded system and are running out of space > >there is no reason not to allow mysql libs to install. > > OT gripe: > > Well, if that's what I have to do, that's what I'll do. It's > getting to the state where, when you install Linux, you just have to > install everything, or administration becomes a treasure hunt. > Otherwise, every time you want to install a package, you have to go > on a treasure hunt. It's also why I search for RPMS rather than > doing a build from source; that's also a treasure hunt for more > files. Do you know that you can't run the printer command-line > configuration tools on Linux unless you have the GUI installed? You > can't set the time zone with the tools provided unless you have some > other giant package installed (I forget which) that I don't need. I > run several Linux servers, and I don't need that GUI crap on each > server. I thought one of the fundamental security concepts was, if > you don't need it, don't install it. Installing support for mysql client libs does not imply you have to run a mysql server (or even access one). That's what security is about when discussing minimal systems in a security context. > I first started with RH Linux 5.2 and it was a joy. However, > starting with about RH Linux 7.0, Linux developers have lost sight > of the original goal, in my opinion, which is to have a small, > easily managed server system. > > I don't have any problem with the dovecot RPM having support for God > knows what, built in. What would be nice is that if I don't reference > it in dovecot.conf, then it doesn't get called. Do you need hyperbole and elliptic functions? Or maybe not even sqrt? Should then glibc allow riping them out? Of course not. And what shoudl any packaging system do when you suddenly do reference mysql support in dovecot.conf? Should it automatically install the missing libs the moment you leave the editor? > End of gripe. I'll go find the required (but unused) packages and > install them, and hope that they don't drag in stall more (unused) crap. If you use --nodeps you'll end up with a broken system. -- Axel.Thimm at ATrpms.net

3 3

[Dovecot] Comments in dovcot.conf files
by Marc Perkel 12 Aug '06

12 Aug '06

Suggestion for comments. Why not support this syntax for comments as well as # /* comments comments */ It will allow for neater looking config files.

2 3

[Dovecot] Ignoring dot files
by Andrew 11 Aug '06

11 Aug '06

Hi, Is there any way to have dovecot ignore files begining with . in directories that contain mbox formatted mail folders (in addition to the already ignored .imap and .subscriptions)? I've looked in the docs and haven't found anything but perhaps I'm not looking in the right place. Thanks, Andrew

2 1

[Dovecot] rc6 + ssl proxy patch = no go
by Jeff A. Earickson 11 Aug '06

11 Aug '06

Timo, I nervously ran rc6 plus the patch: http://dovecot.org/tmp/ssl-proxy-openssl.c on my Solaris 9 box, in production, this morning. My dovecot.conf file is attached. Like similar reports for BSD, rc6 fell over after an hour and a half. The final syslog message was: dovecot: [ID 920869 mail.error] Login process died too early - shutting down I rolled back to rc2 for production. BTW, last night's CVS compiled ok. Jeff Earickson Colby College

2 1

Re: [Dovecot] IMAP4rev1 broken with evolution
by Charles Bueche 11 Aug '06

11 Aug '06

Hi Luca, Good to know. In that case, I won't try to debug Dovecot more. I should have thought about a client issue. Thanks a lot, Charles On ven, 2006-08-11 at 15:15 +0200, Luca Corti wrote: > On Fri, 2006-08-11 at 10:20 +0200, Charles Bueche wrote: > > If I configure my evolution client with server-type IMAP, everything > > works fine. However, dovecot claims IMAP4rev1 support. However, when I > > set server-type to IMAP4rev1 in evolution, I get a popup : > > The evolution IMAP4rev1 server-type is know to be broken. I've not been > able to ever get it even connect to aby IMAP server. Use the standard > IMAP driver, which implements IMAP4 by the way. > > http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/2006-Apr… > > > Luca -- Charles Bueche <charles(a)bueche.ch> sand, snow, wave, wind and net -surfer

1 0

[Dovecot] IMAP4rev1 broken with evolution
by Charles Bueche 11 Aug '06

11 Aug '06

Hi, I'm running 1.0rc6 on Solaris/SPARC, compiled myself against openssl. Client is Evolution 2.6.2 on my gentoo x86 laptop. As Dovecot is not yet productive, we run it parallel to UW-imap, on other ports. I use TLS. If I configure my evolution client with server-type IMAP, everything works fine. However, dovecot claims IMAP4rev1 support. However, when I set server-type to IMAP4rev1 in evolution, I get a popup : -------------------------------------------------------------------- Evolution popup : Error while Scanning folders in "IMAP server xxx.yyy.com". IMAP4 server xxx.yyy.com unexpectedly disconnected : Invalid argument -------------------------------------------------------------------- Using --debug with evolution doesn't show more. In dovecot logs, nothing interesting. I'm ready to test, so please hints me. TIA, Charles -- Charles Bueche <charles(a)bueche.ch> sand, snow, wave, wind and net -surfer

2 2

[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

[Dovecot] LDA Command time limit exceeded
by Dominique Feyer 11 Aug '06

11 Aug '06

I have many errors of this type in my logs: 2 * postfix/pipe[21511]: BC8DD3356A: to=<*****@******>, relay=dovecot, delay=1001, status=bounced (Command time limit exceeded: "/usr/local/dovecot-1.0-rc2/libexec/dovecot/deliver") My command time limit is 1000s in postfix (more than 15 minutes) After many check, I found that a lots of this error is not really an error. The mail is delivered in the mailbox, but postfix send an error message. Like if Dovecot LDA process dont exit correctly after sending a mail. Do you know this bug ? As workaround i set the command time limit to 1400s but this is too long for our customer. They need in time service. We use an NFS server as storage for all our mail. Output of nfstat: Server nfs v3: null getattr setattr lookup access readlink 1 0% 744955962 21% 34845109 1% 397981329 11% 818838045 24% 0 0% read write create mkdir symlink mknod 649838729 19% 502171416 14% 29188492 0% 301741 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 54138192 1% 19903 0% 30702957 0% 27796623 0% 1294453 0% 84457031 2% fsstat fsinfo pathconf commit 48529 0% 31463 0% 0 0% 11339977 0% Output of iostat: Linux 2.4.27-3-686-smp (data.clm.net4all.ch) 21. 07. 06 cpu-moy: %user %nice %sys %iowait %idle 0,16 0,00 1,65 0,00 98,19 Device: tps Blk_lus/s Blk_�crits/s Blk_lus Blk_�crits scsi/host0/bus0/target0/lun0/disc 165,50 310,46 617,07 1800983948 3579692632 scsi/host0/bus0/target0/lun0/part1 165,48 309,32 617,06 1794404866 3579616544 scsi/host0/bus0/target0/lun0/part5 0,02 1,13 0,01 6579064 76088 Thanks for your answers, -- Net4all S.A. Dominique Feyer Administrateur Système Ch. de la Colline 5bis CH-1007 Lausanne dfeyer(a)net4all.ch

2 1

[Dovecot] xfs quota support
by polish 11 Aug '06

11 Aug '06

Hello, quota support is out of action on xfs filesystem on my centos 4.x . Problem is that i haven't these file #include <linux/dqblk_xfs.h> on my system. Solution is simple. After instalation xfsprogs-devel you get necessary files, but you must use another header file in dovecot/src/plugins/quota/quota-fs.c. Instead <linux/dqblk_xfs.h> you should use <xfs/xqm.h>. If you advise me, how can i detect if <xfs/xqm.h> exist instead <linux/dqblk_xfs.h>, i can send patch back. I'm not familiar with autotools. existing code in dovecot/src/plugins/quota/quota-fs.c : #ifdef HAVE_LINUX_DQBLK_XFS_H # include <linux/dqblk_xfs.h> #endif new code : #ifdef HAVE_XFS_XQM_H #include<xfs/xqm.h> #endif Best regards Polish -- ********************************************************** * starnem a porad nic, rozum jako kdyby se nam vyhybal * **********************************************************

2 1

[Dovecot] Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable
by Matt Roman 11 Aug '06

11 Aug '06

So I just upgraded from Dovecot 0.99 to the latest 1.0 RC2 because I was having all sorts of Authentication problems and crashes in 0.99. The upgrade did not solve the problem apparently. Dovecot still crashes periodically and always needs to be manually rebooted. The log file errors at the time of the crash: dovecot: Jul 12 14:30:59 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:04 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:09 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:14 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:19 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:24 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:29 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:30 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:33 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:35 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:39 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:40 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:44 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:45 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:49 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:50 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:54 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:55 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:59 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:59 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:31:59 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:00 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:04 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:04 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:04 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:05 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:09 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:09 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable dovecot: Jul 12 14:32:09 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable I use PAM on the dovecot server connecting to a separate OpenLDAP server with the maildirs on NFS. Currently only the dovecot server talks to the maildirs. Postfix is also on this server, using the same PAM Authentication for SASL and works fine - It does not appear to be a problem with the Authentication server. Thanks in advance!!! -Matt

2 2

Re: [Dovecot] Dovecot deliver logging problem and procmail
by Gerhard Wiesinger 11 Aug '06

11 Aug '06

Hello Timo! Any ideas why it may take so long time to open big mbox files with indexes and delivered through dovecot deliver? So it looks like that something is wrong with the indexes or the algorithm. For details have a look below. BTW: procmail filtering through deliver works well now for me in production environment. I'll make some code cleanups and configuration options. Maybe I can release the patch today. Ciao, Gerhard On Mon, 3 Jul 2006, Timo Sirainen wrote: > On Jul 3, 2006, at 11:07 PM, Gerhard Wiesinger wrote: > >> As far as I saw dovecot's deliver process updates some header fields and the >> index files: >> Status: >> X-Keywords: (with a lot of spaces, why?) >> Content-Length: 6 > > The extra spaces are there so that if Dovecot needs to update some headers it > can take the needed space from there so it doesn't have to move the whole > mbox. > Yes, I saw it after I wrote the mail ... >> After access with dovecot the following header fields change: >> Status: O >> X-IMAPbase: 115195111 0000000009 >> X-UID: 2 >> >> So basically this isn't an advantage over the procmail or any other >> delivering process top mbox. The problem is that after the first access the >> X-UID and X-IMAPbase header must be added, so on large mbox files this might >> take a long time. > > Well, first of all Dovecot should take the space it needs from the X-Keywords > spaces, so it doesn't need to write all that much data. > > Second, the X-UID etc. headers are added by deliver if the mbox file is fully > synced against the indexes. So after you had opened it once with IMAP, after > that deliver should write the X-UID headers also as long as you don't use > something else than Dovecot to modify the mbox. Ok, that worked well. I tried to deliver some large mails (~50MB) which worked well. After sending around 500MB (10 Mails) I opened the mailbox with pine over imap. It still took a lot of time (>20s) to open the mbox. Indexes should be up2date, so why does it take so long time? After opening a second time everything is fine. Any ideas? Ciao, Gerhard

2 2

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

11 Aug '06

On Thu, August 10, 2006 5:22 pm, Timo Sirainen <tss(a)iki.fi> said: > On Thu, 2006-08-10 at 16:28 -0400, Bill Boebel wrote: >> When running Dovecot (rc6 CVS dovecot-20060808) as a proxy, why would it log the >> following when it has not yet maxed out the allowed number of imap-login >> processes? >> >> 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? Cool, thanks. I will try this tonight. Bill

1 0

[Dovecot] 1.0.rc2 released
by Timo Sirainen 11 Aug '06

11 Aug '06

Final 1.0 release is looking to get closer. There's nothing left in my TODO list for it, so please report any old and new bugs you see. This release also makes upgrades from 0.99 more transparent with automatic renaming of .subscriptions and .customflags files with maildir. http://dovecot.org/releases/dovecot-1.0.rc2.tar.gz http://dovecot.org/releases/dovecot-1.0.rc2.tar.gz.sig * disable_plaintext_auth=yes: Removed hardcoded 127.* and ::1 IP checks. Now we just assume that the connection is secure if the local IP matches the remote IP address. * SSL code rewrite which hopefully makes it work better than before. Seems to work correctly, but if you suddently have trouble with SSL connections this is likely the reason. + verbose_ssl=yes: Log also SSL alerts and BIO errors - If namespace's location field wasn't set, the default location was supposed to be used but it wasn't. - When copying ssl-parameters.dat file from /var/lib to /var/run its permissions went wrong if it couldn't be copied with hard linking. - Fixed filesystem quota plugin to work with BSDs. - Maildir: Saving mails didn't work if quota plugin was enabled (again) - Maildir: Messages' received time wasn't saved properly when saving/copying multiple messages at a time. Also if using quota plugin the S= size was only set for the first saved file, and even that was wrong. - passdb passwd-file: Don't require valid uid/gid fields if file isn't also being used as a userdb. - PostgreSQL: Handle failures better so that there won't be "invalid fd" errors in logs. - Don't try to expunge messages if the mailbox is read-only. It'll just cause our index files to go out of sync with the real mailbox and cause errors. - ANONYMOUS authentication mechanism couldn't work because anonymous_username setting wasn't passed from master process.

9 15

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

11 Aug '06

When running Dovecot (rc6 CVS dovecot-20060808) as a proxy, why would it log the following when it has not yet maxed out the allowed number of imap-login processes? 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: login_process_per_connection = no login_processes_count = 3 login_max_processes_count = 20 login_max_connections = 225 I would think that under these conditions we should never see "Connection queue full" being logged. Thanks, Bill

2 1