- dovecot - dovecot.org

[Dovecot] namespaces and creation of folders that contain folders...
by bhayden＠umn.edu 14 Aug '07

14 Aug '07

Hi Timo and all. imap/cmd-create.c contains the following bit of code: len = strlen(full_mailbox); if (len == 0 || full_mailbox[len-1] != ns->sep) directory = FALSE; else { /* name ends with hierarchy separator - client is just informing us that it wants to create children under this mailbox. */ directory = TRUE; mailbox = t_strndup(mailbox, len-1); full_mailbox = t_strndup(full_mailbox, strlen(full_mailbox)-1); i_info("Z CREATE NAME: YYY%sYYY", mailbox); } We've been having trouble with people not being able to create a mail folder that will contain other folders. Tried it both with users using mbox (where this would be a filesystem directory) and maildir. Failed everytime because of a test which rejects folder names that end with MAILDIR_FS_SEP. Looks like the above bit of code is supposed to catch these, make a note of the fact that the client wants a directory, and strip off that trailing separator. In fact, it does this in the case of 'full_mailbox'. However, for 'mailbox' (it seems to me) the code is incorrect as its using the len-1 which is the length of 'full_mailbox', not 'mailbox'. This means that when 'mailbox' and 'full_mailbox' are the same length--that is, for the default namespace (no prefix), it happens to work. However, in any other namespace, it won't, as 'full_mailbox' will always be longer then 'mailbox' if there is a ns prefix, and hence that trailing separator won't be trimmed. (As a matter of fact, in the unlikely instance that the prefix is a single character this will trim the null character from 'mailbox', which probably isn't a good thing.) So. Am I missing something, or crazy, or is this really a bug? Thanks, -Brian

2 2

[Dovecot] about index cache
by Joe Wong 14 Aug '07

14 Aug '07

Hi Timo, Is the dovecot index cache stored only standard header fields (from, to, cc, subject, content-type... )? What happen if there is non standard header, will it be cached? - Joe May the force be with you..

3 9

[Dovecot] Failed to compile dovecot 1.1 nightly build
by wenjie zheng 14 Aug '07

14 Aug '07

I downloaded the 1.1 night build from here: http://hg.dovecot.org/dovecot/archive/tip.tar.gz autogen.sh ./configure (with a long list of options) make I got this error information: ... rpcgen -c /usr/include/rpcsvc/rquota.x | \ -e 's/IXDR_PUT/(void)IXDR_PUT/g' \ -e 's/int32_t \*buf/int32_t *buf __attr_unused__/' > rquota_xdr.c /bin/sh: line 1: -e: command not found make[4]: *** [rquota_xdr.c] Error 127 make[4]: Leaving directory `/var/home/wzheng/code/vendor/src/plugins/quota' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/home/wzheng/code/vendor/src/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/home/wzheng/code/vendor/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/home/wzheng/code/vendor' make: *** [all] Error 2 Am I using the correct nightly build? Thanks, Wenjie

2 1

Re: [Dovecot] dovecot Digest, Vol 52, Issue 52
by Jerry Yeager 14 Aug '07

14 Aug '07

From the digest: On Aug 14, 2007, at 1:04 PM, dovecot-request(a)dovecot.org wrote: other messages cut out… > > > Message: 9 > Date: Tue, 14 Aug 2007 19:03:58 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070814170358.GA17390(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="us-ascii" > > also sprach Kyle Wheeler <kyle-dovecot(a)memoryhole.net> > [2007.08.14.1833 +0200]: >>> I understand that dovecot's deliver does a little more than >>> deliver: >> >> It also understands the 'seive' filter language (an alternative to >> procmail). > > I don't consider it an alternative to procmail because you cannot > pass mail to external programmes, like spamassassin or vacation. > Sure, sieve has its own vacation module, but I find that to be > rather limited. See this thread: > > http://dovecot.org/list/dovecot/2007-August/024686.html > >>> What do you think will be less resource-heavy: calling deliver >>> for every mail received *in addition to* procmail, or letting the >>> IMAP server update the metadata on access? >> >> Unless you're cutting it close to the limit on what your server >> can handle, that's probably the wrong question to ask. A better >> question is: which gives my users better performance? > > Good point. The users, however, as far as I know, all use tools like > offlineimap to synchronise in the background, so it hardly matters. > >> your users aren't paying attention. Dovecot will *seem* snappier >> if you do the indexing work on delivery rather than on access, >> even though it may spend more CPU cycles overall to do so. > > Does anyone have hard facts on how much the server process loses if > it encounters a folder with an index inconsistency? > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > mulutlitithtrhreeaadededd s siigngnatatuurere > > spamtraps: madduck.bogus(a)madduck.net >

1 0

[Dovecot] status of APPENDUID: returning a UID in response to APPEND
by martin f krafft 14 Aug '07

14 Aug '07

# dovecot-related content below, this one for debian bug tracking # system: retitle 435959 Please support RFC4315 UIDPLUS extension in APPEND reply severity 435959 wishlist thanks [please keep 435959(a)bugs.debian.org on Cc.] Hi there, I am working on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435959, which is a performance problem that offlineimap has on large mailboxes. We think that a simple patch to dovecot could cure this problem. I am willing to write the patch but would really like to get your opinion first. In order to keep track of which IMAP message is stored in which local file, offlineimap uses the message UID, which is guaranteed to be unique in the directory, but constant across sessions. When uploading a new message to the IMAP server with APPEND, offlineimap then has to run a SEARCH to obtain said UID for the message it just uploaded. This takes ages on larger mailboxes, as the way offlineimap identifies the message is via a header that's not indexed by dovecot. The solution I found in RFC4315 ("UIDPLUS"; http://www1.tools.ietf.org/html/rfc4315) and then I saw http://www.dovecot.org/list/dovecot/2004-July/003993.html, and now I am wondering: is anyone else interested in APPENDUID? What's the status of an implementation, if any? Newer Courier IMAP server implementation support UIDPLUS and offlineimap will likely obtain this functionality soon. Cheers, [please keep 435959(a)bugs.debian.org on Cc.] -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck "by accepting this brick through your window, you accept it as is and agree to my disclaimer of all warranties, express or implied, as well as disclaimers of all liability, direct, indirect, consequential or incidental, that may arise from the installation of this brick into your building." -- seen on irc spamtraps: madduck.bogus(a)madduck.net

4 3

[Dovecot] dovecot-1.1 + dovecot-sieve-1.1 deliver backtraces
by Sergey 14 Aug '07

14 Aug '07

Hi, I am trying dovecot-1.1 with dovecot-sieve-1.1. First, dovecot -n do not report about deliver settings. They are: --- protocol lda { postmaster_address = postmaster(a)parkheights.dyndns.org hostname = parkheights.dyndns.org mail_plugins = cmusieve mail_plugin_dir = /usr/lib64/dovecot11/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot11/auth-master } --- Then, $ sudo /usr/sbin/dovecot11 -n # 1.1.alpha1: /etc/dovecot11/dovecot11.conf base_dir: /var/run/dovecot11/ log_path: /tmp/dovecot11.log info_log_path: /tmp/dovecot11.debug protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/parkheights.cert ssl_key_file: /etc/ssl/parkheights.key login_dir: /var/run/dovecot11/login login_executable(default): /usr/lib64/dovecot11/imap-login login_executable(imap): /usr/lib64/dovecot11/imap-login login_executable(pop3): /usr/lib64/dovecot11/pop3-login mail_extra_groups: mail mail_location: maildir:/var/spool/imap/%n/.imap mail_debug: yes mail_executable(default): /usr/lib64/dovecot11/imap mail_executable(imap): /usr/lib64/dovecot11/imap mail_executable(pop3): /usr/lib64/dovecot11/pop3 mail_plugin_dir(default): /usr/lib64/dovecot11/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot11/modules/imap mail_plugin_dir(pop3): /usr/lib64/dovecot11/modules/pop3 auth default: debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot/dovecot.passwd userdb: driver: static args: uid=1927 gid=1927 home=/var/spool/imap/%n userdb: driver: passwd-file args: /etc/dovecot/dovecot.passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot11/auth-master mode: 384 user: vmail group: vmail --- Couple of backtraces from /tmp/dovecot11.log are here. I will try to attach them as a textfile to this message, so that lines will not be wrapped, but I'm not sure that attachements are not stripped. So, please excuse me for duplication in this case. --- dovecot: Jul 25 01:05:19 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/dovecot.index.cache: Corrupted cach ed message_part data (physical_pos less than expected) deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] dovecot: Jul 25 06:52:21 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.sisyphus-lists-altlinux-org/dovecot.index.cache: Corrupted cache d message_part data (physical_pos less than expected) --- -- With best regards, Sergey. dovecot: Jul 25 01:05:19 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/dovecot.index.cache: Corrupted cach ed message_part data (physical_pos less than expected) deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] deliver(seriv): Jul 25 04:17:26 Panic: seq = 1587, rec->uid = 0, first_new_seq = 1587, records = 1586 deliver(seriv): Jul 25 04:17:26 Error: Raw backtrace: /usr/lib64/dovecot11/deliver [0x46e045] -> /usr/lib64/dovecot11/deliver [0x46dd2c] -> /usr/lib64/dovecot11/deli ver [0x44de1e] -> /usr/lib64/dovecot11/deliver [0x44e687] -> /usr/lib64/dovecot11/deliver(index_transaction_finish_commit+0x28) [0x444488] -> /usr/lib64/dovecot11/de liver [0x41f53f] -> /usr/lib64/dovecot11/deliver(index_transaction_commit+0x38) [0x4442f8] -> /usr/lib64/dovecot11/deliver(mailbox_transaction_commit+0x11) [0x45f221 ] -> /usr/lib64/dovecot11/deliver(deliver_save+0x107) [0x414267] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab20987b] -> /usr/lib64/dovecot1 1/modules/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x6b8) [0x2aaaab219dc8] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x30 b) [0x2aaaab20a35b] -> /usr/lib64/dovecot11/modules/lda/lib90_cmusieve_plugin.so [0x2aaaab208806] -> /usr/lib64/dovecot11/deliver(main+0xc4e) [0x41505e] -> /lib64/li bc.so.6(__libc_start_main+0xf4) [0x2aaaaaee5c14] -> /usr/lib64/dovecot11/deliver [0x413739] dovecot: Jul 25 06:52:21 Error: IMAP(seriv): Corrupted index cache file /var/spool/imap/seriv/.imap/.sisyphus-lists-altlinux-org/dovecot.index.cache: Corrupted cache d message_part data (physical_pos less than expected)

2 5

[Dovecot] v1.1.alpha3 released
by Timo Sirainen 13 Aug '07

13 Aug '07

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha3.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha3.tar.gz.sig All kinds of fixes and API changes. Previous alphas had some problems with index handling, now I didn't get any errors after almost 24h of stress testing. As a new feature userdb passwd now supports overriding some fields with templates. http://wiki.dovecot.org/AuthDatabase/Passwd

3 4

[Dovecot] logging dovecot-sieve vacation responses
by pod 13 Aug '07

13 Aug '07

I attach a patch that adds some informational logging for the vacation outcome in a similar style as the 'notify', 'redirect' and 'reject' cases. I considered adding logging for the not-willing-to-respond case since I think that would greatly assist testing/debugging vacation responses, but couldn't see where to put it that wasn't in the CMU code.

1 0

[Dovecot] plain authentication
by Roger D. Vargas 13 Aug '07

13 Aug '07

After upgrading my server I have found that Im not able to use plain auth for clients conecting from outside server. localhost clients (pine, webmail) works fine, but if I use Thunderbird I got an error saying that server requires TLS or SSL. But if I enable TLS or SSL I got more errors. I have tried sevral combinations, but havent found a working one. Here is my config, can somebody see what Im doing wrong? # /etc/dovecot/dovecot.conf protocols: imap pop3 ssl_disable: yes ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no mail_extra_groups: mail mail_location: mbox:~/mail/:INBOX=/var/spool/mail/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: shadow userdb: driver: passwd -- Roger D. Vargas http://dsgp.blogspot.com

1 0

[Dovecot] "pipe" plugin
by Nicolas Boullis 13 Aug '07

13 Aug '07

Hi, Long ago (more than 2 month ago), I told about a "pipe" plugin I had written to perform some spam/ham learning (see the attached message). I'm now proud to say that I can make it available for use by anyone. You can get it from http://nicolas.boullis.free.fr/pipe.tar.gz Note that this is a temporary location. If someone had a good place to host it, feel free to do (and tell). I think it would be great if the feature could be merged into dovecot. I don't care whether my plugin is used or a rewrite is performed... Cheers, Nicolas

2 2

[Dovecot] Inbox re-initialized
by Joshua, C.S. Chen 13 Aug '07

13 Aug '07

Hi folks, I just replaced my mail server's UW-imap with dovecot yesterday. I use the following folder setting default_mail_env = mbox:/asiaa/home/%u/:/asiaa/home/%u/mail/:INBOX=/var/mail/%u:INDEX=/asiaa/home/%u/mail/dovecot_indexes This is a Scientific linux 4.2 with dovecot 0.99.11-2 . Now today the server loading is highly reduced because of the pop3 session impact is low. But users have the following problems: For outlook express users, when they come in the office, the first time they launch outlook express, they found that the previous Inbox is re-transmitted. So they got double the number of all past e-mails (they setup OE setting to keep a copy on the server). And some users also use pine. After the pine session, they get another whole copy of the past e-mails (so some users got 3X or even 4X the past e-mails). Am I missing something for the dovecot.conf setting, here is the entire configurations: Thanks in advance protocols = pop3 pop3s imap_listen = [::] pop3_listen = [::] log_path = /var/log/dovecot login_dir = /var/run/dovecot-login login = imap login = pop3 default_mail_env = mbox:/asiaa/home/%u/:/asiaa/home/%u/mail/:INBOX=/var/m ail/%u:INDEX=/asiaa/home/%u/mail/dovecot_indexes mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root Cheers Joshua

5 5

[Dovecot] using complete email address as username
by WJCarpenter 13 Aug '07

13 Aug '07

I've been poking around the dovecot wiki, and this idea looks plausible. I'm just double-checking with the assembled experts to see if there is some "gotcha" that will happen to me down the road. I have in mind a deployment of dovecot which will use serve several unrelated domains. My plan is to use the complete email address of the users as the unique userid. So, for example, a user with email address <foo(a)example.COM> is unrelated to a user with email address <foo(a)example.NET>. The "home" directories of such users will look something like: /some/path/foo(a)example.com/ /some/path/foo(a)example.net/ I do also plan to use ACLs for some things, so there could be ACL entries of the form: user:foo@example.com ... I will probably be using the quota plugin for individual users right away and group quotas later when that's officially available. So, is all this likely to work or will it collapse in a miasma of unmet expectations? Thanks in advance for any comments!

3 2

[Dovecot] Deleting deleted eMails
by Michael Weisgerber 11 Aug '07

11 Aug '07

Hello 2gether, I am using Dovecot 1.0.rc15 together with Outlook (I apologize) via IMAPS. Now I discovered, that all the old eMails, I marked for deleting, are still there, even the veeery old ones. Dovecot is marking the eMails (I am using maildir configuration) files with an "ST" extension. Is there any switch to turn on garbage collection and maybe a screw to tune the duration until deletion? Thanks for your help! Michael Weisgerber

5 5

[Dovecot] Dovecot shared mailbox folder problem
by Steffen Kaiser 10 Aug '07

10 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've set up a namespace to share some mailboxes. When I try to select them, I get an internal error: Client-server chat: * OK Dovecot ready. 1 login dvtest2 x 1 OK Logged in. 2 list "" * * LIST (\HasNoChildren) "." "Trash" * LIST (\HasChildren) "." "test" * LIST (\HasNoChildren) "." "INBOX" * LIST (\HasNoChildren) "." "test.test2" * LIST (\Noselect \HasChildren) "." "Shared" * LIST (\HasNoChildren) "." "Shared.testAccess" * LIST (\HasNoChildren) "." "Shared.testNOaccess" 2 OK List completed. 3 select "Shared.testAccess" 3 NO Internal error occurred. Refer to server log for more information. [2007-07-04 16:45:31] dovecot: Jul 04 16:45:31 Error: IMAP(dvtest2) [3512]: stat(/mnt/mailcache/shared/.testAccess/cur) failed: Permission denied # l /mnt/mailcache/shared/.testAccess -n total 24 drwxrws--- 5 31045 30005 4096 2007-07-04 15:53 ./ drwxr-xr-x 6 0 0 4096 2007-07-04 16:08 ../ drwxrwsr-x 2 31045 30005 4096 2007-06-21 12:19 cur/ - -rw-r--r-- 1 31045 30005 17 2007-07-04 15:38 dovecot-acl - -rw-rw---- 1 31045 30005 0 2007-07-04 15:53 dovecot-shared drwxrws--- 2 31045 30005 4096 2007-06-21 13:57 new/ drwxrws--- 2 31045 30005 4096 2007-06-21 13:57 tmp/ I added chmod o+rx for testing purpose, just in case. stracing the situation results in: gettimeofday({1183560101, 339756}, {4294967176, 0}) = 0 read(0, "3 select \"Shared.testAccess\"\r\n", 3978) = 30 setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 stat64("/mnt/mailcache/shared/.testAccess", {st_mode=S_IFDIR|S_ISGID|0770, st_size=4096, ...}) = 0 stat64("/mnt/mailcache/shared/.testAccess/cur", 0xbf8cb470) = -1 EACCES (Permission denied) write(2, "\1Estat(/mnt/mailcache/shared/.te"..., 72) = 72 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0 write(1, "3 NO Internal error occurred. Re"..., 95) = 95 setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0 gettimeofday({1183560101, 341458}, NULL) = 0 What do I wrong? # 1.0.1: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/ca.crt ssl_cert_file(default): /etc/ssl/certs/imap.pem ssl_cert_file(imap): /etc/ssl/certs/imap.pem ssl_cert_file(pop3): /etc/ssl/certs/pop3.pem ssl_key_file(default): /etc/ssl/private/imap.key ssl_key_file(imap): /etc/ssl/private/imap.key ssl_key_file(pop3): /etc/ssl/private/pop3.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_log_format_elements: %p: user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle: yes first_valid_uid: 1000 mail_location: maildir:%h/MailDir:CONTROL=/var/cache/dovecot/%i/control:INDEX=/var/cache/dovecot/%i/index mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes umask: 7 mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot-1.0.1/libexec/dovecot/rawlog /usr/local/dovecot-1.0.1/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot-1.0.1/libexec/dovecot/rawlog /usr/local/dovecot-1.0.1/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib acl mail_plugins(imap): quota imap_quota mail_log zlib acl mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 0 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: . inbox: yes hidden: yes namespace: type: public separator: . prefix: Shared. location: /mnt/mailcache/shared:CONTROL=/var/cache/dovecot/%i/sek/control:INDEX=/var/cache/dovecot/%i/sek/index auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot-1.0.1/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot-1.0.1/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /etc/passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 group: mail plugin: quota: fs Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRouzwS9SORjhbDpvAQLJwgf+NJ8bROXIRfoAjQy+eunNOtM+VoQB0I0A 6EUBG0XfTlgJ1hn63FxpQZPmKBMfLEl013DQQzm9Dw5GezrbgI815M+mZrP6BzYB 95ao1lCTo1hlyVGThG6LgE9JJS8BvE5ASaJOu4XD9u+d2LdV8I+MkcMC9o57XBQt nUV0RrNbxcQpuDq1Qpjf0tu9t0HCRoMzHD0p7cOHteSHiGvvrMeFD0JG7Ida7grQ Uzjbuw92qSNinwTE/89pVr3xrgJGmxdy7ix/y4UBeUx8I9YXOHheB7SOM3cQ6q6J KXKS89Fh9ZWZDsgQwmqaOfAhVgLQjyeAwyA6jqfNzg/Rx0J44m905w== =f+1y -----END PGP SIGNATURE-----

4 9

[Dovecot] Monitorize concurrent sessions
by Jordi Espasa Clofent 10 Aug '07

10 Aug '07

Hi all, ¿Is there some way/method to monitorize and see what users are working at same time? Thanks.

1 0

[Dovecot] dovecot: child 1690 (auth-worker) killed with signal 11
by Thomas Zajic 10 Aug '07

10 Aug '07

Hi there, I've been seeing this for quite a while now, but only today finally got off my lazy you-know-what and did a backtrace. Here's the requested info as per http://dovecot.org/bugreport.html: * Dovecot version [root@airframe]:~# dovecot --version 1.0.3 * Operating system or Linux distribution name Slackware 10.2, both kernel 2.6.21.3 and dovecot self-compiled * CPU architecture (x86 or something else?) x86 (AMD Athlon XP 3200+) * Filesystem you used (especially if you use NFS or not) ext3, local (no NFS) * Some kind of description of what you were doing and with what IMAP client. Thunderbird 2.0.0.4 (also happened with earlier versions) mail-notification-4.1 (" " " " " ) * If the problem can be reproduced, it helps a lot if you can tell how. Happens in almost regular intervals, not sure when exactly though. Usually when doing something in TB again (deleting or moving mails) after it has been sitting idling for a while. From the log files going back to July 22nd: [root@airframe]:~# grep "dovecot: child .* (auth-worker) killed with signal 11" /var/log/maillog* | wc -l 258 TB is configured to use TLS and secure authentication, use IDLE, and 5 cached server connections. Mail Notification is configured to use TLS, and to autodetect both the authentication mechanism and IDLE availability. * Dovecot configuration with dovecot -n [root@airframe]:~# dovecot -n # 1.0.3: /usr/local/etc/dovecot.conf login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes mail_location: maildir:/home/%u/Maildir:INBOX=/home/%u/Maildir/.INBOX mail_debug: yes fsync_disable: yes maildir_copy_with_hardlinks: yes mail_drop_priv_before_exec: yes auth default: mechanisms: plain digest-md5 cram-md5 debug: yes passdb: driver: shadow args: blocking=yes passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd args: blocking=yes * Backtrace [root@airframe]:~# gdb /usr/local/libexec/dovecot/dovecot-auth /usr/local/stow/dovecot-data/var/run/dovecot/core GNU gdb 6.3 [...] Core was generated by `dovecot-auth -w'. Program terminated with signal 11, Segmentation fault. [...] (gdb) bt full #0 0x00000000 in ?? () No symbol table info available. #1 0x08056954 in auth_worker_handle_passl (client=0x8089e18, id=3, args=0x808a082 "user=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:242 auth_request = (struct auth_request *) 0x808a3f0 credentials_str = 0x2 <Address 0x2 out of bounds> #2 0x08056c15 in auth_worker_handle_line (client=0x8089e18, line=0x808a078 "PASSL\t1\t2\tuser=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:326 id = 3 #3 0x08056ca7 in auth_worker_input (context=0x8085ac8) at auth-worker-client.c:359 client = (struct auth_worker_client *) 0x8089e18 line = 0x808a076 "3\tPASSL\t1\t2\tuser=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1" ret = 118 #4 0x0806b841 in io_loop_handler_run (ioloop=0x80851a8) at ioloop-poll.c:199 ctx = (struct ioloop_handler_context *) 0x80851d0 pollfd = (struct pollfd *) 0x80851f0 tv = {tv_sec = 1, tv_usec = 999620} io = (struct io *) 0x8089f88 t_id = 2 msecs = 134765256 ret = 0 call = true #5 0x0806ae89 in io_loop_run (ioloop=0x80851a8) at ioloop.c:329 No locals. #6 0x0805a04b in main (argc=2, argv=0xbfa36e98) at main.c:321 foreground = false (gdb) Please let me know if you need any additional info (log snippets, etc.). Thanks, Thomas -- =-------------------------------------------------------------------------= - Thomas "ZlatkO" Zajic <zlatko(a)gmx.at> Linux-2.6.21 & Thunderbird-2.0 - - "It is not easy to cut through a human head with a hacksaw." (M. C.) - =-------------------------------------------------------------------------=

2 3

[Dovecot] Version 1.1 Alpha 2 Various Stuff
by Jerry Yeager 09 Aug '07

09 Aug '07

Some preamble information… OS X 10.4.10 (all updates) Power Mac Dual G5, 2.0 Postfix with Dovecot SASL, Dovecot LDA, Dovecot imaps (openssl) Mail clients Apple Mail v 2.1 SquirrelMail v 1.4.10a Thunderbird v 2.0.0.6 Mulberry v 4.06 For various versions of Dovecot, from 0.9m up through 1.0.3 things went well, no memorable big problems, with one exception: Mulberry v 4.0.8 would/will not work; i.e. it refuse(d) to connect saying it could not start SSL to begin the connection. Dropped back to version 4.0.6. I switched to version 1.1 alpha 2 (compile and configuration information is attached at the end of this message) 1) Started up Apple mail. Mail boxes disappeared in Apple Mail's list, except for the main Inbox mail box. Fixed by setting mailbox_list_index_disable = yes in the Dovecot.conf file, restarted both Dovecot and Mail, all the mailboxes reappeared and worked correctly. 2) Started up Squirrel Mail using several different browsers. No problems. 3) Started up Thunderbird. No problems. 4) Started up Mulberry. It partially connected, but stopped with the error saying that it had hit the limit for maximum connections. Mail logs show: dovecot: imap-login: Maximum number of connections exceeded: user=<username>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.50, TLS I tried increasing the various limits in the Dovecot.conf file up through a maximum limit of 2048 connections, to no avail. Mulberry will initially connect to several of the mailboxes, but will stop without getting all of them and will throw up the 'over the connection limit' error and will then show you a dialog box that asks you to log-in. Attempting to doing so returns a fatal error 54. I have not tried Mulberry's version 4.0.8. 5) Mail logs had this message suddenly begin appearing: auth-worker(default): pam(username,192.168.1.1): pam_authenticate() failed: Authentication failure Fixed by completely commenting PAM authentication section out; It was: passdb pam { # [blocking=yes] [session=yes] [setcred=yes] # [cache_key=<key>] [<service name>] # ... essentially a placeholder section, since everything inside is commented out # # } now is: #passdb pam { # # ... even the outer block is commented out # #} The error has now disappeared from the logs. Dovecot was build using: CPPFLAGS=-I/usr/local/include/openssl LDFLAGS='-L/usr/local/lib -R/ usr/local/lib' \ ./configure \ --with-ssl=openssl \ --with-libiconv-prefix=/usr/local Dovecot.conf: # 1.1.alpha2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imaps ssl_listen: *:993 ssl_parameters_regenerate: 24 ssl_cipher_list: ALL:!LOW:!SSLv2 verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: Dovecot login_greeting: Hello, Dovecot is ready. valid_chroot_dirs: /var/mail/vmail/ mail_extra_groups: mail mail_location: maildir:/var/spool/vmail/%d/%n:INDEX=/var/spool/vmail/% d/%n:INBOX=/var/spool/vmail/%d/%n mail_debug: yes mailbox_list_index_disable: yes lock_method: flock imap_client_workarounds: delay-newmail auth default: mechanisms: plain login passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/users socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: virtual group: virtual

2 2

[Dovecot] Crash with 1.1alpha2 when lazy_expunge is enabled?
by Rich at Whidbey Telecom 09 Aug '07

09 Aug '07

I'm seeing a crash in 1.1alpha2 when trying to expunge a folder when "lazy_expunge" is enabled: namespace private { separator = . prefix = .EXPUNGED/ location = maildir:/mailstore/%u/Expunged hidden = yes } ... lazy_expunge = .EXPUNGED/ .EXPUNGED/ .EXPUNGED/ Commenting out "lazy_expunge" prevents the crash and mail is expunged. It happens with and without ACL's. Attached is the log output. The messages never actually get moved to the "Expunged" directory, but there is a "temp" file created each time: /mailstore/testuser/Expunged/ drwx------ 6 testuser users 4096 Aug 9 11:39 . drwxr-xr-x 4 testuser users 4096 Aug 9 10:59 .. drwx------ 2 testuser users 4096 Aug 9 10:59 cur -rw------- 1 testuser users 24 Aug 9 11:39 dovecot.list.index.log -rw------- 1 testuser users 28 Aug 9 11:39 dovecot.list.index.uidmap drwx------ 5 testuser users 4096 Aug 9 11:02 .Junk -rw------- 1 testuser users 0 Aug 9 10:59 maildirfolder drwx------ 2 testuser users 4096 Aug 9 10:59 new -rw------- 1 testuser users 0 Aug 9 11:04 temp.mail4.whidbey.net.8596.7b344a891b2c6691 -rw------- 1 testuser users 0 Aug 9 11:32 temp.mail4.whidbey.net.8761.bfe04f5457e4ba7e -rw------- 1 testuser users 0 Aug 9 11:33 temp.mail4.whidbey.net.8765.44e803d87275348a -rw------- 1 testuser users 0 Aug 9 11:37 temp.mail4.whidbey.net.9031.f4a972591af59e05 -rw------- 1 testuser users 0 Aug 9 11:39 temp.mail4.whidbey.net.9125.d67b160254a01631 drwx------ 2 testuser users 4096 Aug 9 10:59 tmp Lazy expunge works on our production 1.0.0 systems. Anyone else seen this? Rich dovecot: Aug 09 11:04:25 Info: imap-login: Login: user=<testuser>, method=PLAIN, rip=209.166.64.35, lip=172.16.125.4 dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Loading modules from directory: /usr/local/lib/dovecot/imap dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib01_acl_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Effective uid=40308, gid=100, home=/var/mail/testuser dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Quota rule: root=storage=102400 mailbox= storage=256000kB messages=0 dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Namespace: type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes dovecot: Aug 09 11:04:25 Info: IMAP(testuser): maildir: data=/mailstore/testuser/Maildir:INDEX=MEMORY dovecot: Aug 09 11:04:25 Info: IMAP(testuser): maildir++: root=/mailstore/testuser/Maildir, index=, control=, inbox=/mailstore/testuser/Maildir dovecot: Aug 09 11:04:25 Info: IMAP(testuser): acl: initializing backend with data: vfile:/adminstore/configs/dovecot-acls:cache_secs=600 dovecot: Aug 09 11:04:25 Error: IMAP(testuser): Sending log messages too fast, throttling.. dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: acl username = testuser dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: owner = 1 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl vfile: Global ACL directory: /adminstore/configs/dovecot-acls dovecot: Aug 09 11:04:26 Info: IMAP(testuser): Namespace: type=private, prefix=.EXPUNGED/, sep=., inbox=no, hidden=yes, list=no dovecot: Aug 09 11:04:26 Info: IMAP(testuser): maildir: data=/mailstore/testuser/Expunged:INDEX=MEMORY dovecot: Aug 09 11:04:26 Info: IMAP(testuser): maildir++: root=/mailstore/testuser/Expunged, index=, control=, inbox=/mailstore/testuser/Expunged dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: initializing backend with data: vfile:/adminstore/configs/dovecot-acls:cache_secs=600 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: acl username = testuser dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: owner = 1 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl vfile: Global ACL directory: /adminstore/configs/dovecot-acls dovecot: Aug 09 11:04:28 Info: IMAP(testuser): acl vfile: reading file /adminstore/configs/dovecot-acls/Junk dovecot: Aug 09 11:04:28 Info: IMAP(testuser): acl vfile: file /mailstore/testuser/Maildir/.Junk/dovecot-acl not found dovecot: Aug 09 11:04:41 Info: IMAP(testuser): acl vfile: reading file /adminstore/configs/dovecot-acls/Junk dovecot: Aug 09 11:04:41 Info: IMAP(testuser): acl vfile: file /mailstore/testuser/Expunged/.Junk/dovecot-acl not found dovecot: Aug 09 11:04:41 Error: IMAP(testuser): file mailbox-list-maildir.c: line 161 (maildir_list_get_path): assertion failed: (mailbox_list_is_valid_existing_name(_list, name)) dovecot: Aug 09 11:04:41 Error: IMAP(testuser): Raw backtrace: imap [0x80c5df1] -> imap [0x80c5d0c] -> imap [0x806ba2d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x46cfab] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_init_from_name+0x1d) [0x46b93d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_rebuild+0x1c7) [0x46d627] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_refresh+0x1fd) [0x46db5d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_verify+0x1f) [0x46dcdf] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x46cf13] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_have_right+0x2d) [0x46bc6d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_storage_rights_ctx_have_right+0x5a) [0x4703aa] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x470466] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x4707d8] -> /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so [0xf5ad3a] -> /usr/local/lib/dovecot/imap/lib10_q dovecot: Aug 09 11:04:41 Error: IMAP(testuser): uota_plugin.so [0x51b92a] -> imap(mailbox_open+0x46) [0x80b6ff6] -> /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so [0xf5b092] -> /usr/local/lib/dovecot/imap/lib10_quota_plugin.so [0x51b0e8] -> imap(imap_expunge+0xb4) [0x8060034] -> imap(cmd_expunge+0x43) [0x805a4d3] -> imap [0x805e649] -> imap [0x805e6e3] -> imap(_client_input+0x65) [0x805ecb5] -> imap(io_loop_handler_run+0x10f) [0x80cba3f] -> imap(io_loop_run+0x28) [0x80cb3a8] -> imap(main+0x4ec) [0x806637c] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x707dec] -> imap [0x8058e41] dovecot: Aug 09 11:04:41 Error: child 8596 (imap) killed with signal 6

1 0

[Dovecot] UW-IMAP style mbox snarfing from /var/mail/ to ~/mbox
by Timo Sirainen 09 Aug '07

09 Aug '07

http://dovecot.org/patches/mbox-snarf-plugin.c Also committed to CVS HEAD. Usage: mail_location = mbox:~/mail:INBOX=/var/mail/%u protocol imap { mail_plugins = mbox_snarf } protocol pop3 { mail_plugins = mbox_snarf } plugin { mbox_snarf = ~/mbox } If ~/mbox doesn't exist, nothing special is done. If ~/mbox exists, it's treated as INBOX and mails are moved from /var/mail/%u whenever the mailbox is synchronized. If all the messages couldn't be copied, for example because of out of quota, then none of the messages are copied. I suppose that could be a problem. It might be possible to fix that by changing: if (mailbox_copy(dest_trans, mail, 0, NULL, NULL) < 0) { if (!mail->expunged) { ret = -1; break; } } to just: if (mailbox_copy(dest_trans, mail, 0, NULL, NULL) < 0) { if (!mail->expunged) break; } But I'm not sure about that. Try and tell me. :)

2 18

Re: [Dovecot] assertion failed with KMail 3.5.6 and dovecot 1.0.0
by Timo Sirainen 09 Aug '07

09 Aug '07

On Mon, 2007-07-30 at 15:07 +0200, Sylvain Joyeux wrote: > > > IMAP(doudou): file ostream-crlf.c: line 339 (_send_istream): assertion > > > failed: ((size_t)ret <= iov.iov_len) > > Hmm. Can you get Dovecot to dump a core file? > > Probably easiest way to get this fixed would be then if you sent me > > the core file and also the imap binary and I'll debug it further. Or > > I could also send you several gdb commands you could run. > > Here are the imap executable and core dump files (compressed). They are > generated on a powerpc machine, so I'm not sure it will be useful to you. > Moreover, Debian strips its executables, so no line numbers ... Debugging information would have been really useful, but I did fix one bug and added some more asserts: http://hg.dovecot.org/dovecot-1.0/rev/bd113e9fe67b If it still wasn't fixed, maybe with this change it gives another assert.

1 0

[Dovecot] Outlook 2000/2003 frequent disconnect issue
by Jeff Ramsey 09 Aug '07

09 Aug '07

I have been using Dovecot for an IMAP server for a few years now, with no hitch. Even using Outlook 2K/2K3 as a client. Yesterday, I had a user experience the 'Negative UIDs' issue spoken of here: http://wiki.dovecot.org/Clients/NegativeUIDs I performed all of the steps mentioned in this article, and it seemed like it would work properly the first time the user checked their email, and then after that, they would get this error again. I checked to see what the latest stable version of Dovecot was, and decided to upgrade. I was at 0.99.11-8 and the latest stable rpm for my distro was 1.0.2-2. The upgrade went fine. Or so I thought. I am now getting the following message on all Outlook Clients: "Your IMAP Server closed the connection....this can occur if the connection is idle for too long" I have scoured the Internet for this error and have come up with many suggestions, none of which have worked. I have increased Outlook's timeout period to the full 10 minutes, and I have disabled SELinux. None of this seems to have worked. Is there anyone out there who has actually had this issue and resolved it? Can you please help? Thanks, Jeff Ramsey MIS Administrator TMI Forest Products, Inc. jefframsey(a)tubafor.com 360.477.0738 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 12

[Dovecot] Database server failure causes endless loop
by Andy Shellam 09 Aug '07

09 Aug '07

Hi, I've just started setting up Dovecot 1.0.1, and made an error in my configuration, which I think has found a potential problem in Dovecot. I'm using PostgreSQL authentication, and set the database host to "localhost", which PostgreSQL doesn't listen on, so libpq is throwing the standard "is the server running?" message. The problem, however, is Dovecot isn't seeming to understand this, and is endlessly looping, trying to query it every 5 seconds. My client (telnet during testing) is simply sitting there waiting for a response, which it's never going to get. After about 5 minutes, Dovecot killed the connection, saying "* BYE Disconnected for inactivity." If this was from an IMAP client, I'm guessing the client would time-out after so long when it doesn't get a response back. Wouldn't it be more sensible for Dovecot to try PostgreSQL, say, 3 times. If unsuccessful, send the client an "internal server error" or something similar? Otherwise if the database server failed, and the client tries to connect, it'd be waiting for at least a minute (or whatever the standard time-out interval is) before failing, whereas it'd be better to see almost instantly if the server's down. Regards, Andy. Log output: dovecot: Jul 01 11:31:03 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:03 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:03 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:08 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:08 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:08 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:13 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:13 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:13 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:18 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:18 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:18 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:23 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:23 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:23 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:28 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:28 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:28 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:33 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:33 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:33 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:38 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:38 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:38 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:43 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:43 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:43 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:48 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:48 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:48 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:53 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:53 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:53 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:58 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:58 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:58 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:03 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:03 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:03 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:08 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:08 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:08 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:13 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:13 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:13 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:18 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:18 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:18 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:23 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:23 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:23 Error: auth(default): TCP/IP connections on port 5432?

2 1

[Dovecot] Moving mboxes around
by tomas＠tuxteam.de 09 Aug '07

09 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dovecot gurus, I have a couple of questions for which I haven't found answers in the docs (which may be well more a limitation of my capabilities than anything else). Here they go: - Is it OK to move mailboxes around from under Dovecot? Case in point: I'm using procmail to pass incoming mail through bogofilter (the standard recipe mentioned in their manpage, which more or less funnels spam into a "spam" mailbox, unsure into an "unsure" and non-spam into "inbox"). From time to time I'd like to clear the spam and unsure mailboxes, using logrotate. Dovecot seems to cope with it. Am I tempting my luck? - Is there a way to tell an external application when mail has been moved by a client? Again: dovecot+bogofilter: from time to time a client checks incoming, unsure and sometimes spam and decides to move --say-- a mail from unsure to spam (deciding it's spam, after all) or similar. This is of course important for the training of bogofilter, so I'd like to trigger a backend action. I see basically two possibilities: - create two more mailboxes, say "spam-indeed" and "ham-indeed". User is told to move mail into these. Ham-indeed gets re-funneled to inbox (or something like that). Manual and error prone. - Use the mail_log plugin (seems more attractive). I still have (distro-provided) dovecot 0.99.14, but this would be a good reason to upgrade. (I still don't see where I get the source mailbox in the mail_log messages from, but that's details now). You get the idea, I think. Anyway, I am interested in any ways to combine dovecot and bogofilter in the backend in a way that I can route user feedback to the filter without putting too much burden on the user. Ideas? Thanks - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGtuS4Bcgs9XrR2kYRAkiXAJoDJYZC8DYIxFqCw+HEIn0CCNssQwCfaZjh z533XFMH36c4Lemv/+gSn9A= =s87z -----END PGP SIGNATURE-----

2 2

[Dovecot] dotlock file was deleted error
by Joe Wong 09 Aug '07

09 Aug '07

Hello, under what situation the error: dovecot-uidlist.lock was deleted (kept it 0 seconds ) will happen? I saw quite some of these in dovecot log. Thanks, - Joe

4 6

[Dovecot] passdb/userdb restart
by Thomas Hummel 09 Aug '07

09 Aug '07

Hello Timo, I've noticed that when slapd which I'm using as the passdb and the prefetched userdb is restarted I have to restart dovecot. As a matter of fact, if I don't, I get the following error : -- Jul 2 16:38:39 xxxx dovecot: imap-login: Internal login failure: user=<xxxx>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Jul 2 16:38:46 xxxx dovecot: auth(default): prefetch(xxx,xxx.xxx.xxx.xxx): passdb didn't return userdb entries Jul 2 16:38:46 xxxx dovecot: auth(default): userdb(xxx,xxx.xxx.xxx.xxx): user not found from userdb -- I'm using dovecot-1.0.1 on FreeBSD 6.2-STABLE with openldap-server-2.3.35_1 (bdb backend). Would some cache-related parameters allow to fix that or will restarting dovecot be always mandatory after an ldap restart ? Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1