July 2006 - dovecot - dovecot.org

[Dovecot] dovecot-lda, sieve, maildir
by Frank Cusack 14 Aug '06

14 Aug '06

I'm unable to get dovecot-lda with sieve filtering to deliver into maildir folders. The examples on the wiki explicitly say "mbox", so I'm wondering, does the dovecot-lda sieve implementation not support filtering into maildir folders? -frank

5 13

[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] [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] 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 10 Aug '06

10 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 10 Aug '06

10 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

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

10 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] OpenLDAP only?
by ssoo＠siliconfile.com 10 Aug '06

10 Aug '06

I tried to compile Dovecot v1.0RC2 on Opeteron/Solaris 10 box. "db-ldap.c", line 343: undefined symbol: LDAP_SASL_QUIET "LDAP_SASL_QUIET" is defined as "2U" in OpenLDAP's ldap.h but not in /usr/include/ldap.h How can I compile Dovecot with Sun's LDAP implementation?

3 3

[Dovecot] maildir++ specification compliance.
by Apps Lists 10 Aug '06

10 Aug '06

Hi folks. I was doing some testing this morning and realized Dovecot RC2 isn't fully compliant with the maildir++ specification. Most notably, it appears that Dovecot isn't creating a "maildirfolder" file (0 byte length) in folders it creates. >From http://www.inter7.com/courierimap/README.maildirquota.html "Within each subdirectory there's an empty file, maildirfolder. Its existence tells the mail delivery agent that this Maildir is a really a folder underneath a parent Maildir++." and "Make sure to create the maildirfolder file in any new folders created within the Maildir++." Also, GETQUOTAROOT on a folder (with messages in it) will always return the entire usage, not the usage in the folder itself. For example: INBOX - really has 100 mb of messages. Sent - has a few messages totalling 1mb. Drafts - no messages A GETQUOTAROOT on INBOX will return 101 mb, 100mb for INBOX and 1mb for Sent. Drafts will show zero, because there's nothing. Unfortunately, Sent will also show 101 mb, not 1mb. While Dovecot shouldn't be creating maildirsize files in each folder (the maildirfolder file is there to tell clients to look in .. for a maildirsize) ... it should still be able to answer queries about the number of messages (count of files in the folder) as well as the total size of all messages in that folder (sum of S=xxxx or by stat() on individual message files). Steve

4 4