- dovecot - dovecot.org

[Dovecot] chained SSL certificates
by Cor Bosman 06 Dec '04

06 Dec '04

Hi all, anyone got dovecot to work with chained SSL certificates? Cor

1 0

[Dovecot] IMAP - many folders?
by piotr＠mallorn.ii.uj.edu.pl 05 Dec '04

05 Dec '04

Hi, I've been reading the list and it seems the answer to my (soon to be asked question) is no, at least with 0.99, but I'll ask to be sure. I have following setup: new mail goes to ~/Mail/Maildir, except for mailing lists which are moved by procmail to ~/Mail/mailing_lists/name, spam which goes to ~/Mail/spam. Read mail is moved by mutt to ~/Mail/read. Everything is in maildir format. Is it possibile to configure dovecot in such a way to allow user to access all those mail folders thorough imap/pop? User can access ~/Mail/Maildir by setting default_mail_env, but so far nothing else. -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!

9 17

[Dovecot] (_send_istream): assertion failed:
by Kim Culhan 05 Dec '04

05 Dec '04

This is on FreeBSD 5.3, is this fixed in -test or CVS ? Log message is below.. dovecot: Dec 05 07:48:08 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Dec 05 07:48:08 Error: child 42086 (imap) killed with signal 6 -kim __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

[Dovecot] 0.99.12-rc1
by Timo Sirainen 05 Dec '04

05 Dec '04

http://dovecot.org/rc/ Just gathered the patches in dovecot.org/patches/ and a few more that I think have been sent to this list before. If there's anything missing, please tell. - Fix memory leaks in LDAP, MySQL and PGSQL userdb/passdb - Fix hanging when parsing mails that have over 4096 bytes in one line (SMTP servers normally don't allow over 1000 bytes so it shouldn't be much of a problem) - FETCH BODYSTRUCTURE sometimes giving a wrong reply (eg. with FETCH (BODYSTRUCTURE RFC822.SIZE) if it wasn't cached) - Never return more than one INBOX in LIST even if there are such files. They don't work anyway and it just confuses clients. - mbox: Don't allow creating INBOX directory by creating/renaming mailboxes under it. They just wouldn't work. - POP3: Don't return PLAIN in SASL list. We don't support initial SASL responses, so it only breaks with most clients that try to use it.

3 6

AW: [Dovecot] newbie question
by Grammes, Carsten 03 Dec '04

03 Dec '04

> If you really want to use maildir, you can have procmail deliver to > maildirs: > (in .procmailrc): > DEFAULT=$HOME/Maildir/ > > Note the trailing slash - that's the kicker. > > Then tell Dovecot to use maildir. > > If you want to mix and match mailbox formats per user, then you'll > need to use an auth database that allows setting this (passwd-file, or > maybe ldap or sql). Thanks, Jon! I think now I get the picture. I will start playing around with procmail and the with dovecot auth options. Carsten

1 0

[Dovecot] newbie question
by Grammes, Carsten 03 Dec '04

03 Dec '04

Hello all, just managed to install dovecot as imap server on a Suse Linux box. Now running fine with mbox format. A question regarding maildir or mbox. The MDA (in my case sendmail, Mlocal = procmail) stores mbox format. Do have to modify the local mailer to store maildir format or does dovecot convert automatically from mbox when I tell dovecot to use maildir format? Thanks, for any hint. Carsten

2 1

[Dovecot] Maildir/mbox on a per-user basis
by Jon Nathan 03 Dec '04

03 Dec '04

Hello, The Wiki indicates that Dovecot can do either mbox or Maildir on a per-user basis: default_mail_env can be overridden in userdb for each user. This works with userdbs supporting the "mail" attribute (eg. passwd-file, SQL, LDAP). How exactly does one do this for passwd-file? Thanks, -Jon -- Jon Nathan jon(a)rupture.net

9 8

[Dovecot] master or client
by Kirill Miazine 03 Dec '04

03 Dec '04

Hello, Dovecot auth protocol 1.0 defines differend command sets for client and master. How can a daemon distinguish a master connection from a client connection? Clients do send CPID and master does not. I have following auth configuration: auth external { socket connect { master { path = /var/state/dovecot/login/master-auth } } } I try to learn my authentication daemon to learn to speak with Dovecot. I fire up my master.py and try to login via pop3 as foo:bar. Below is what my master.py receives from Dovecot (master and client), VERSION commands are not shown: km@thinkpad:/home/km > ./krot/sbin/master.py CPID : ['11915'] CPID : ['11915'] CPID : ['16652'] CPID : ['11915'] AUTH : ['1', 'PLAIN', 'service=POP3', 'secured', 'lip=127.0.0.1', 'rip=127.0.0.1', 'resp=AGZvbwBiYXI='] REQUEST : ['9', '11915', '1'] CPID : ['16652'] (In the above output command and parameters are parsed.) The protocol specification is mentioning a separate SERVICE command in the client's greeting. I can't let my daemon die if the master issues DIE. Why should a server exit when it receives DIE? Can anybody provide an example dialog of an authentication request that is successful and a reques that fails because of a bad password. Thanks, Kirill -- They make a desert and call it peace. -- Tacitus

2 2

[Dovecot] pop3 with lmos results in multiple downloads
by Juerd 03 Dec '04

03 Dec '04

One of our users wants to use POP3 with leave-mail-on-server (LMOS). That's great and works well for most people. But for some reason, they MUA (outlook) downloads messages more than once. As the MUA asks for messages, I'm sure it's Outlook's fault, but I was wondering if there is anything that can be done about this on the servern side, or if anyone knows how to fix Outlook. I'm sending this here, because they report that with non-dovecot servers it does work correctly. They do not want IMAP, because they want to use Outlook, which cannot support both Exchange and IMAP simultaneously. This user has multiple accounts, and only for some of them things go wrong. A temporary fix is to remove the mail from the server once, but after a few more messages arrive, the problem starts all over again. Please help. Regards, Juerd

3 3

[Dovecot] imap: assertion failed
by Kim Culhan 03 Dec '04

03 Dec '04

This error is returned when reading a certain message using Squirrelmail. Any help on tracing the cause of this is greatly appreciated. >From the logs: dovecot: Nov 20 13:00:29 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Nov 20 13:00:29 Error: child 27873 (imap) killed with signal6 -kim __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com

2 1

[Dovecot] Problem getting incoming mail to IMAP inbox
by Jeff Sutherland 03 Dec '04

03 Dec '04

I have dovecot-0.99.10.5 on Fedora Core 2 installed and otherwise operating using Maildir format for the folders, Kmail as the email client. Got through all the ssl and other security configuration fine, but have one last problem: I can't read the incoming mail from /var/spool/mail/%u. Tried several 'default_mail_env' settings, including none at all, to no avail. When I try to check in new mail to the inbox, the only messages are "Transmission Complete, no new messages" Tried this setting for example: default_mail_env = maildir:~/Maildir/:INBOX=/var/spool/mail/%u but to no avail. Is something getting cocked up because the folders are all in maildir format and the incoming mail spool is in mbox format? I checked permissions, they seem ok. Kmail can pull the messages in just fine to its local folder inbox, it just seems that dovecot can't read the mail spool file for some reason. All the other maildir folders work fine. ????????? Regards, -Jeff -- Secure your email with Gnu Privacy Guard and Mozilla, the open source cross platform solution for Windows, Linux, and Mac OS X. See http://enigmail.mozdev.org/

2 1

[Dovecot] Cannot list mailbox
by Fawad Halim 03 Dec '04

03 Dec '04

Hi, I have dovecot 0.99.11 on a Linux machine running against a maildir based mailbox. I am getting the following errors in the maillog: Nov 27 23:08:14 fawad3 imap(fawad): file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Nov 27 23:08:14 fawad3 dovecot: child 14202 (imap) killed with signal 6 This happens when the mail reader tries to enumerate the messages in the INBOX. I am able to read the messages whose headers have already been cached by the mail reader. It is also able to read others folders without any problem. This problem has occured before, and I was able to get rid of it by identifying the junk mail message it was dying on. In this case, however, I'm not able to figure out which message is causing it to crash. I am able to read the same maildir in mutt, and Courier IMAP doesn't seem to have trouble with it either. I'd really appreciate if someone could tell me what I can do to get around this problem. Regards -fawad

2 1

[Dovecot] 1.0-test CVS HEAD index problems
by Jim Lawson 03 Dec '04

03 Dec '04

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:42:39 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:42:39 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:42:39 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:43:59 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:43:59 Error: IMAP(jtl): Corrupted index cache file /users/j/t/jtl/.i map/INBOX/dovecot.index.cache: indexid changed dovecot: Dec 01 13:47:24 Error: IMAP(jtl): file mbox-lock.c: line 493 (mbox_lock): asse rtion failed: (lock_type == F_RDLCK || ibox->mbox_lock_type != F_RDLCK) dovecot: Dec 01 13:47:25 Error: child 17528 (imap) killed with signal 6 dovecot: Dec 01 13:47:41 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:50:49 Error: IMAP(jtl): UIDVALIDITY changed (1101926435 -> 110192703 6) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:55:27 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:55:27 Error: IMAP(jtl): UIDVALIDITY changed (1101926435 -> 110192703 6) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:56:15 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:56:15 Error: IMAP(jtl): UIDVALIDITY changed (1101926435 -> 110192703 6) in mbox file /var/spool/mail/j/t/jtl Using Thunderbird-0.9. Dovecot is running on RHEL 3, on top of Redhat/Sistina GFS (clustered filesystem.) Currently I'm keeping it on one node to avoid possible GFS locking issues. I'm running with mmap_disabled=yes, mbox format. Most of the 1.0-test builds I have done eventually corrupt their index files, and show strange behavior (click on a message in the folder view, and an entirely different message opens... delete three or four messages and expunge, the messages instantly reappear as unseen.). I typically wipe the .imap directories between different builds of Dovecot. I've been following the -test code for a couple of months now, just to see how it does, because we're running UW IMAPd and are excited to have a way to increase the performance of our mail cluster (indexes) without having to move away from mbox. Let me know if there's more information I could provide that would be helpful. Jim

3 4

[Dovecot] Excessive imap_login processes
by Keith Edmunds 02 Dec '04

02 Dec '04

I'm running Dovecot on a very small mail server (never more than six users accessing IMAP, often fewer). I'm seeing the number of imap_login processes grow over time, and right now there are 23. All the "login_process_*" settings in dovecot.conf are commented (ie, at their defaults). Is this a known or expected issue? The version of Dovecot is 0.99.10.8, which I accept is perhaps a little old. Thanks, Keith

2 1

[Dovecot] 1.0-test55
by Timo Sirainen 30 Nov '04

30 Nov '04

http://dovecot.org/test/ Sorry :) The last fix I made a few minutes before test54 release didn't turn out to be exactly correct.

4 4

[Dovecot] big troubel - damaged mailboxfolders
by Götz Reinicke 30 Nov '04

30 Nov '04

Hi, because the fedora project switcht from wu imap to dovecot, i followed this step. Today I'm very unhappy about this step, because there are more problems for me than advantages... But today the biggest problem is, that a lot!!! of mailboxes are damaged. within three year no mailbox was damaged using wu imap. The errormessage is: imap(cstrang): File isn't in mbox format: /var/mail/cstrang the server is fedora core 1, dovecot-0.99.11. May be I have something misconfigured, but where to look at? Any ideas, what causes the damage? And installing the test-version isnt an alternativ for my production server vor 500 users. Regards Götz Reinicke -- Götz Reinicke IT Koordinator - IT OfficeNet Tel. +49 (0) 7141 - 969 420 Fax +49 (0) 7141 - 969 55 420 goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg Mathildenstr. 20 71638 Ludwigsburg www.filmakademie.de

2 3

[Dovecot] 1.0-test55, threading does not include new messages
by Nicolas.Kowalski＠imag.fr 30 Nov '04

30 Nov '04

Hello. The dovecot server is 1.0-test55, with maildir storage. The MUA is pine 4.61, using thread sort. When I open a folder containing new messages (delivered through procmail), the threads do not include these messages. I have to close the folder, then open it again to make the threads complete. Thanks in advance. -- Nicolas

1 0

[Dovecot] 1.0-test53 and 'Junk in start of group' messages
by Nicolas.Kowalski＠imag.fr 30 Nov '04

30 Nov '04

Hello. I am using dovecot-1.0-test53 with Maildir mailstore, with pine 4.61 as MUA. I have several folders which cause error messages like 'Junk in start of group' in Pine when I read them. I googled a bit for this, and found that removing the index file should do the trick, but unfortunately, it does not. What can I do to make these annoying messages disappear ? Thanks in advance. -- Nicolas

3 5

[Dovecot] dovecot only answers to imap connections
by Mitch Pirtle 30 Nov '04

30 Nov '04

Hey list, Finally got up and running, and now am trying to figure out why dovecot would only accept imap connections - I have people that are happy with pop, but they can only authenticate when they use imap. Is there a conf setting for this somewhere that I am missing? -- Mitch

4 4

[Dovecot] 1.0-test54
by Timo Sirainen 30 Nov '04

30 Nov '04

http://dovecot.org/test/ Fixing crashes and other index problems with test53.

1 0

[Dovecot] Entourage on Dovecot 09.11, is 1.0-test the answer?
by Michael Maggard 30 Nov '04

30 Nov '04

Background: I'm running a RH9 box with Dovecot 0.99.11. Dovecot was installed using yum and the rpm found on http://dag.wieers.com/packages/dovecot/. With two exceptions I've been enormously happy with Dovecot. I'm even happier having recently successfully installed pop-before-smtp sop one exception down. However the other problem I've experienced is becoming critical. I've an ongoing issue with MS Entourage clients, a MS for Mac product, unable to authenticate to Dovecot. This had been attributed to MacOS 9/MS Entourage 2001 but with new systems in place I'm having the same issue with MacOS X/MS Entourage 2004 being unable to authenticate to Dovecot. MS acknowledges the issue in http://support.microsoft.com/kb/871016 with the errata: > 5 Known issues > 5.1 NTLM v1 authentication support > Entourage no longer supports NTLM v1 authentication. Entourage does support NTLM v2. Where I am now: There has been previous references to an Entourage authentication issue on the mailing list but it was resolved by "after I tried everything else with no success, upgrading from Dovecot 0.99.10.2 to 0.99.10.4 solved the problem." Well, I'm at 0.99.11 so apparently this is back, or something else is going on. >From several hours going over the mailing list it appears that Dovecot 1.0-test is the solution with it's extended NTLM support. However I'm not a very sophisticated sysadmin and so it was with trepidation I downloaded dovecot-1.0-test52 and started following the instructions. After a quick "yum install openssl-development" I thought I was good to go but alas "./configure --with-ssl=openssl" resulted in: > ./configure: line 26374: pkg-config: command not found > checking for SSL_read in -lssl... yes > checking openssl/ssl.h usability... no > checking openssl/ssl.h presence... no > checking for openssl/ssl.h... no > checking openssl/err.h usability... yes > checking openssl/err.h presence... yes > checking for openssl/err.h... Yes and make failed with a cascade of errors after: > In file included from /usr/include/openssl/ssl.h:179, > from ssl-proxy-openssl.c:14: > /usr/include/openssl/kssl.h:72:18: krb5.h: No such file or directory Why I'm posting: So, hoping I've given enough detail to be useful, here are my questions: * Am I correct that MS Entourage 2004 can't authenticate with Dovecot .99.11? Are there folks it does work for (how)? * Am I correct that Dovecot-1.0-test has support for NTLMv2 and would thus authenticate MS Entourage 2004? * Does anyone have a prebuilt (yum suitable) rpm of a recent Dovecot 1.0-test for RH9? Dag appears to only carry released versions, is there a source for -test ones? * Is there something trivial I'm overlooking in trying to build dovecot-1.0-test52? I'm assuming I'm missing /usr/include/openssl/kssl.h, is this correct? Any assistance is greatly appreciated. I was pushing my skillset getting pop-before-smtp working. While I'm good at following directions and learning from them I'm just that; learning. -- Michael <michael(a)michaelmaggard.com>

3 2

[Dovecot] 1.0-test53, sig11 when sorting by thread
by Nicolas.Kowalski＠imag.fr 30 Nov '04

30 Nov '04

Hello. When trying to sort a folder by thread (with pine4.61), I get a sig11. The mailstore is Maildir, indexes stored in /var/indexes/%u. The syslog on the server shows this: Nov 29 11:37:55 olan dovecot: IMAP(kowalski): Corrupted index cache file /var/indexes/kowalski/.INBOX/dovecot.index.cache: record points outside file Nov 29 11:37:56 olan dovecot: child 14344 (imap) killed with signal 11 A backtrace of the core is attached. Thanks. PS: I tried with mbox mailstore, and got the same sig11. -- Nicolas

4 11

[Dovecot] test53 and signal 11 errors
by Sean Porter 30 Nov '04

30 Nov '04

I installed test53 tonight, and I've begun to see the following error in my maillog every time I attempt to retrieve mail from an imap client: dovecot: child 46128 (imap) killed with signal 11 I built from source on FreeBSD 4.9 with the following: ./configure --with-mysql --with-storages=maildir --with-ssl=openssl A little bit of Googling seems to indicate that this is a hardware issue(http://www.bitwizard.nl/sig11/), but I've not had this error under any other circumstances. What other information would be helpful to sort this out?

4 4

[Dovecot] 1.0-test53
by Timo Sirainen 29 Nov '04

29 Nov '04

http://dovecot.org/test/ Sorry for not answering any questions for past two weeks, I'll try to get around answering them in next few days. I've also been thinking about if I should switch from CVS to Darcs. It seems to be exactly the kind of reversion control tool I had wanted to use. Anyone have comments for or against it? I'd still have read-only CVS repository generated from it, although I couldn't yet find a way to do it. Anyway, test53: - Recent flag counters should finally be correct - dovecot-shared file actually works correctly now - Cache file works with mmap_disable = yes (still some small issues though) - Lots of internal changes in indexing code, especially for mmap_disable = yes - DIGEST-MD5 authentication works again - etc. It's been running with me for 45mins without breaking. Guess it should work. :)

5 6

AW: Re: [Dovecot] [OT] Apple Mail.app access to localhost imap whe n nonetwork
by valo＠valo.at 29 Nov '04

29 Nov '04

> This script is what I use -- note that you need to have it on the > server, and then call ssh to execute that script (on the server) > immediately. > #!/bin/sh > # arch-tag: dbfe44f6-0d80-40c4-948a-bac05a804bf5 > > export MAIL=/home/johannes/Maildir > export MAILBOX_CHECK_INTERVAL=60 > exec /usr/lib/dovecot/imap Hi. IIRC you should exec dovecot as a whole, to use it properly. Also edit your dovecot.conf to only serve imap. christian

3 3