- dovecot - dovecot.org

[Dovecot] nfs and pop3
by Marten Lehmann 27 Jan '06

27 Jan '06

Hi, I'm working with dovecot 1.0.beta2 for pop3 only and have set index=memory, so no indizes are created on the disk. pop3_uidl_format is set to %f. The maildirs are located on an nfs-share. So generally, this setup is very similar to what qmail-popup and qmail-pop3d does. However, everytime I'm switching from qmail-pop3d to dovecot, the system load increases from less than 2 to more than 30 (and later up to 60 and more). The problem is I/O, probably caused by nfs-access. But what is causing this accesses? qmail-pop3d just takes filenames as UIDL, and moves the mails from new to cur, reads them to send them to the client or deletes them. This is working fine. But what is dovecot doing? There must be a lot more things that cause that high I/O load. Indizes are disabled, so they cannot be the cause any longer. Any ideas? I just want to switch to dovecot at some point finally without having qmail-pop3d as backup. Regards Marten

4 7

[Dovecot] gcc 2.95 compile errors
by Chris Wakelin 27 Jan '06

27 Jan '06

Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real PATH environment variable (which didn't include the gcc3 location). Should I be worried? Chris ostream-file.c: In function `o_stream_writev': ostream-file.c:126: warning: `ret' might be used uninitialized in this function ostream-file.c: In function `_send_istream': ostream-file.c:671: warning: assignment from incompatible pointer type mail-cache.c: In function `mail_cache_lock': mail-cache.c:374: warning: `ret' might be used uninitialized in this function mail-index-transaction.c: In function `mail_index_update_header_ext': mail-index-transaction.c:710: warning: unused parameter `t' mail-index-transaction.c:711: warning: unused parameter `ext_id' mail-index-transaction.c:711: warning: unused parameter `offset' mail-index-transaction.c:712: warning: unused parameter `data' mail-index-transaction.c:712: warning: unused parameter `size' maildir-storage.c:891: warning: missing initializer maildir-storage.c:891: warning: (near initialization for `maildir_storage.pool') maildir-storage.c:926: warning: missing initializer maildir-storage.c:926: warning: (near initialization for `maildir_mailbox.pool') mbox-sync.c: In function `mbox_sync_seek_to_uid': mbox-sync.c:921: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_handle_eof_updates': mbox-sync.c:1228: warning: assignment from incompatible pointer type mbox-sync.c:1287: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_update_index_header': mbox-sync.c:1330: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_do': mbox-sync.c:1418: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_has_changed': mbox-sync.c:1496: warning: assignment from incompatible pointer type mbox-storage.c:1045: warning: missing initializer mbox-storage.c:1045: warning: (near initialization for `mbox_storage.pool') mbox-storage.c:1080: warning: missing initializer mbox-storage.c:1080: warning: (near initialization for `mbox_mailbox.pool') dbox-storage.c:630: warning: missing initializer dbox-storage.c:630: warning: (near initialization for `dbox_storage.pool') dbox-storage.c:665: warning: missing initializer dbox-storage.c:665: warning: (near initialization for `dbox_mailbox.pool') dbox-transaction.c: In function `dbox_transaction_commit': dbox-transaction.c:20: warning: unused parameter `flags' dbox-transaction.c: In function `dbox_transaction_rollback': dbox-transaction.c:77: warning: unused variable `dbox' auth-server-connection.c: In function `auth_server_connection_new': auth-server-connection.c:200: warning: `fd' might be used uninitialized in this function auth-master-connection.c: In function `master_input_die': auth-master-connection.c:145: warning: unused parameter `conn' main.c: In function `create_unix_listener': main.c:101: warning: `fd' might be used uninitialized in this function dict-process.c:96: warning: `dict_process_listen' defined but not used master-settings.c:360: warning: missing initializer master-settings.c:360: warning: (near initialization for `default_settings.listen_ip') quota-storage.c: In function `quota_save_init': quota-storage.c:165: warning: assignment from incompatible pointer type -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 1

[Dovecot] chained ssl cert not working
by harryp＠dmsnev.com 27 Jan '06

27 Jan '06

I am running a production server with 40 pop3 users using dovecot 0.99.14. I am trying to get a chained certificate installed that I purchased through godaddy.com. I need some clarification on how to do this. I found some really vague instructions on the dovecot wiki http://wiki.dovecot.org/ChainedSSLCertificates?highlight=%28chained%29 Unfortunately these instructions are very confusing for me. I also found someone else who asked a similar question http://dovecot.org/list/dovecot/2005-June/007528.html I have tried to get this to work, but have failed. Could someone please explain this better. I don't understand if all of these keys/certificates go into 1 file or what. I need an example if someone could be so kind as to take a moment of their time. Thanks for any help.

3 3

[Dovecot] out of memory error
by Pavel Volkovitskiy 27 Jan '06

27 Jan '06

Hello I have this errors in my dovecot.log every day or two: ============================================= ... dovecot: Jan 24 10:28:56 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:01 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:41 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:56 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:36 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:38 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:39 Error: auth-worker(default): Out of memory (Needed 52 bytes) dovecot: Jan 24 10:30:41 Error: auth-worker(default): pool_system_malloc(): Out of memory dovecot: Jan 24 10:30:41 Error: child 3576 (auth-worker) returned error 83 (Out of memory) ============================================= I use dovecot 1.0-beta1 login_process_size = 128 login_process_per_connection = no login_processes_count = 5 login_max_processes_count = 128 login_max_logging_users = 256 -- Pavel

3 6

[Dovecot] How to make pops
by mickael.choisnard＠free.fr 27 Jan '06

27 Jan '06

Hi, I use dovecot (pop) with gentoo but it's not securize. I would like to use pops but i don't how to do this. I think i have to use certificates... This my dovecot.conf : protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * ssl_disable = no login = imap login = pop3 default_mail_env = maildir:%h/.maildir mbox_locks = fcntl dotlock auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam dovecot auth_user = root auth_verbose = yes auth_debug = yes Thanks for your help

2 1

[Dovecot] Dovecot don't recognise new messages in maildir /new
by Tim Wagner 27 Jan '06

27 Jan '06

Hi, i'm google for it and i searched the archives, but i can't find the problem i have or a hint for a solution. I'm using Postfix as MTA, the new messages deliver by postfix to the maildir: /mail/domain.tld/userpart/new/ Dovecot sometimes show the new mails directly (it's very unusual) but mostly it needs for an hour that dovecot recognize the new messages. Reconnecting of the client don't help. Tested with Thunderbird, Sylpheed-Claws, mutt and muttng. Is there a bug known or do i something wrong?

3 5

[Dovecot] 1.0beta2 build error
by Peter Lindgren 27 Jan '06

27 Jan '06

Hi! I received the following error (I ran ./configure and make without options) when running make install: Making all in auth make: don't know how to make db-ldap.h. Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2/src/auth. *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2/src (line 284 of Makefile). *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2 (line 340 of Makefile). *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2 (line 224 of Makefile). This is what I found: # ls src/auth/db-ldap.* src/auth/db-ldap.c src/auth/db-ldap.o # find . -name 'db-ldap.*' -print ./src/auth/db-ldap.c ./src/auth/.deps/db-ldap.Po ./src/auth/db-ldap.o I didn't find a db-ldap.h anywhere in /usr either. Any hints? I run OpenBSD 3.7 on sparc. /Peter -- Peter Lindgren, dataingenjör E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

2 2

[Dovecot] Fwd: Weird problem opening mbox in beta1/2
by Chris Wakelin 27 Jan '06

27 Jan '06

Hmm, this is peculiar! This mailbox has been unchanged on my test server since September. I've been using it to test each new version of Dovecot just after I've compiled it. When beta1 was released, I opened this mbox with no problems. However, when I upgraded to beta2, I got "file size unexpectedly shrinked in mbox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)". Reverting to beta1, it also failed with the same error! I've deleted indexes, restored the mbox from a backup made in October (no changes) and I still get the error. It *does* open OK in 1.0-stable. I've put it through mboxcrypt.pl, deleted the UW-IMAP pseudo-message (which wasn't converted properly by mboxcrypt) and it still fails to open with a similar error, so I've sent it to Timo (gzipped, of course!) I've e-mailed this to the list minus the attachment as sending unsolicited 1MB attachments is unfriendly! However, if anybody wants to look at it, please let me know. Best Wishes, Chris P.S. The past participle of "shrink" is "shrunk" not "shrinked" - it's yet another irregular English verb :) -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 4

[Dovecot] Hang in 1.0.alpha4
by Mark Plaksin 26 Jan '06

26 Jan '06

My IMAP client hangs intermittently. When it does, Dovecot has prematurely stopped sending a response and entered the poll loop. My client is waiting for more data and Dovecot is waiting for an IMAP command. This problem seems to occur when I connect to the dovecot process over the network and when I run the imap binary directly via an SSH tunnel. Below is truss output from the imap process for one of the hangs. It is responding to a FETCH, gets EAGAIN, and then seems to give up sending the rest of the message and enters the poll loop. Below that is the log from my IMAP client to show its side of the story. Nothing shows up in the normal Dovecot log. I haven't caught it in the act recently when running with rawlog. But rawlog output from before I was running with truss shows that Dovecot does not think it has finished sending its response. truss output: 12951: stat64("/home/happy/Mail/banner-ss", 0xFFBFF200) = 0 12951: fstat64(12, 0xFFBFF388) = 0 12951: stat64("/home/happy/Mail/.imap/banner-ss/dovecot.index", 0xFFBFF2F0) = 0 12951: fstat64(18, 0xFFBFF388) = 0 12951: pread64(18, "\n F r o m b e v e r l".., 4096, 1592560) = 4096 12951: pread64(18, " S u n G a r d * S C".., 4094, 1596656) = 4094 12951: pread64(18, " M i c r o s o f t S a".., 4094, 1600750) = 4094 12951: pread64(18, " r g a r e t . d i l l a".., 4094, 1604844) = 3720 12951: pread64(18, 0x0025EEA2, 374, 1608564) = 0 12951: pread64(18, 0x0025EEA2, 374, 1608564) = 0 12951: pread64(18, " R e t u r n - P a t h :".., 4096, 1592616) = 4096 12951: write(1, " * 2 5 0 F E T C H ".., 4073) = 4073 12951: pread64(18, " a l v e r n , P A ".., 4095, 1596712) = 4095 12951: write(1, "\n W i l l i a m B . ".., 4060) = 4060 12951: pread64(18, " l ( i n c l u d i n g".., 4095, 1600807) = 4095 12951: write(1, "\n & # 8 2 2 6 ; < / b".., 4069) = 4069 12951: pread64(18, " m o z - t x t - l i n k".., 4095, 1604902) = 3662 12951: write(1, "\n ".., 4079) Err#11 EAGAIN 12951: write(1, "\n ".., 4096) Err#11 EAGAIN 12951: poll(0x000A0AD0, 3, 533) = 1 12951: write(1, "\n ".., 4096) = 4096 12951: poll(0x000A0AD0, 2, 532) = 0 12951: poll(0x000A0AD0, 2, 0) = 0 12951: poll(0x000A0AD0, 2, 999) (sleeping...) 12951: poll(0x000A0AD0, 2, 999) = 0 Here's the log from my IMAP client. I removed email addresses and most of the body of the message to protect the innocent. The "BYE" was caused by me running 'kill $PID' on the imap process. 3551 OK Fetch completed.! 3552 UID FETCH 252 BODY.PEEK[] * 250 FETCH (UID 252 BODY[] {16341}! Return-Path: <abc(a)usg.edu>! Received: from usg.edu (abc.usg.edu [1.2.8.1])! by abc.usg.edu (8.12.11/8.12.11) with ESMTP id j9KFqoga012884! for <abc(a)USG.EDU>; Thu, 20 Oct 2005 11:52:50 -0400 (EDT)! Message-ID: <4357BD52.1020506(a)usg.edu>! Date: Thu, 20 Oct 2005 11:52:50 -0400! From: abc <abc(a)usg.edu>! User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)! X-Accept-Language: en-us, en! MIME-Version: 1.0! To: abc(a)usg.edu! Subject: [Fwd: [Fwd: Fw: Java Library Problem]] - URGENT, I'm sorry...! Content-Type: multipart/mixed;! boundary="------------010604070704040405060605"! X-USG-MailScanner: Found to be clean! X-USG-MailScanner-SpamCheck: ! X-MailScanner-From: abc(a)usg.edu! ! This is a multi-part message in MIME format.! --------------010604070704040405060605! Content-Type: multipart/alternative;! boundary="------------040009050704020209010709"! ! ! --------------040009050704020209010709! Content-Type: text/plain; charset=us-ascii; format=flowed! Content-Transfer-Encoding: 7bit! ! Guys,! Please create a ssh login on... from ! 24 hours now) with testing. His account should look like Patrick ! I've requested a static IP from Dan.! ! ...! </pre>! </body>! </html>! ! --------------040009050704020209010709--! ! --------------010604070704040405060605! Content-Type: text/x-vcard;! Content-Transfer-Encoding: 7bit! Content-Disposition: attachment;! ! begin:vcard! ...! tel;work:(xxx) xxx-2000! tel;fax:(xxx) xxx-xxxx! url:http://www.u* BYE Server shutting down.! imap(happy): Warning: Killed with signal 15 ------------------------------------------------------------------------------ The mail message in question actually ends like this: tel;work:(xxx) xxx-2000 tel;fax:(xxx) 583xxx-xxxx url:http://www.usg.edu version:2.1 end:vcard --------------010604070704040405060605--

4 12

[Dovecot] dovecot.index.log.2 needed?
by Jeff A. Earickson 26 Jan '06

26 Jan '06

Hi, I just discovered a whole lot of dovecot.index.log.2 files in people's .imap folders? Are these files needed in the long term? Or can they be zapped if they are more than X days old? Jeff Earickson Colby College

2 1