- dovecot - dovecot.org

[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 02 Dec '04

02 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 02 Dec '04

02 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 02 Dec '04

02 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 02 Dec '04

02 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