- dovecot - dovecot.org

[Dovecot] outstanding issues with 0.99.13
by sean finney 10 Feb '05

10 Feb '05

hi list, i'm in the process of testing dovecot before a hopeful switchover from uw-imap/qpopper to dovecot, primarily to get off of the uw-imap/mbox combo and moved to Maildir. i think we've worked out the logistics to avoid any service downtime, with only a short window of a few minutes per user for when we convert from mbox to maildir format. however, during testing a few issues have come up, some of which i've been able to work around, others which i haven't. for those that i have been able to work around, i'll include my solution so that fellow googlers may profit, and for those that i haven't i'd really appreciate your feedback. logistical problems: 1 - automagic detection and uw-imap inbox in ~/mbox. i'm not sure if this is a default characteristic or if it's specific to us, but our spool is in /var/mail/foo and inbox in ~/mbox. the automagic Maildir/mbox detection doesn't find the "mbox", and i can't tell it where it is because then it doesn't look for the Maildir. solution: i wrote a small patch to dovecot's autodetect code to help it find the location of our mailboxes. if anyone would like a copy of said patch i can send it off list. 2 - uw-imap's spool/inbox message moving. i read from the wiki that this isn't a feature currently being worked on. solution: deliver all mail to the same place. since we use procmail as our MDA, this isn't too hard of a problem. basically we redirect mail to the inbox and redeliver everything in the spool. 3 - supporting multi-homed services + ssl. for historical reasons we provide services from multiple hostnames (mail.foo, imap.foo, etc). with ssl, that means a different cert for each, otherwise some clients will break. solution: we're spawning off three seperate dovecot instances, each using a different config file. not the most graceful, but it works... application problems: 4 - dovecot imap + ms lookout 2002 + deleting messages. i'm not sure if this is an app or server side problem. basically, a user will delete a message, only to have it reappear in the mailbox a short time (few minutes) later. if i monitor the state of the mbox file, no changes are made to it until the user selects "empty trash", after which point they are expunged. looking at a protocol dump, i see the client setting the deleted flag on the message when they originally delete it. here's an excerpt: <snip> tg7i OK Idle completed. 6gzd UID STORE 30021 +FLAGS (\Deleted \Seen) * 51 FETCH (FLAGS (\Deleted \Seen \Recent) UID 30021) 6gzd OK Store completed. stpw IDLE <snip> i'm not too familiar with imap, but it looks like the server is caching the deletion request and then forgetting later forgetting about it? i have all the "client workarounds" enabled, fwiw. solution: ??? 5 - mac os x + eudora + deleting mail. a different problem alltogether. in eudora deleting a mail seems to immediately move it to the "trash" mailbox, so the above problem does not occur. what *does* happen is that if a user rapidly deletes messages one-by-one, an error message pops up about UID's not existing. i haven't gotten a full description of this problem, but here's an excerpt from what i think is the symptom: <snip> A00109 UID COPY 30002 Trash A00109 OK Copy completed. A00110 UID STORE 30002 +Flags.silent (\Deleted) A00110 OK Store completed. A00111 EXPUNGE * 31 EXPUNGE A00111 OK Expunge completed. <snip> and later: <snip> A00040 UID FETCH 30002 (UID BODYSTRUCTURE) A00040 NO Some of the requested messages no longer exist. A00041 UID FETCH 30002 RFC822.SIZE A00041 NO Some of the requested messages no longer exist. A00042 UID FETCH 30002 (BODY.PEEK[]) A00042 NO Some of the requested messages no longer exist. <snip> which i suppose is correct that it doesn't exist (since it was moved out of the inbox). however, eudora does not have this problem with uw-imap, and i'm wondering what might be causing it? solution: ??? okay, i think that's everything that i've ran into. we're still pushing ahead with this because we need to get the hell off of uw-imap/mbox, but i don't think we'll be able to stick with dovecot if these are unresolvable issues. in that case, we'll probably use dovecot with these minor nuisances while we transition, and then perhaps use courier in the long run. hopefully that won't have to be the case though :) if anyone has any experience specifically with "5" and "5", i'd really, really like to hear about it. in the meantime, i'll continue to test other things, and also see if the problem also persists when mail is stored in Maildir format. anyway, thanks for your time! sean

4 4

[Dovecot] oh, and status of 1.0?
by sean finney 09 Feb '05

09 Feb '05

sorry for splitting this off into a second message :) is there a roadmap/schedule for the release of 1.0? ever curious, sean

2 1

[Dovecot] Dovecot Maildir to read /var/spool/mail
by Ben Halicki 09 Feb '05

09 Feb '05

Hi all, Does anyone know how to configure dovecot to read /var/spool/mail as the inbox using maildir format? Thanks in advance, Ben Halicki

2 2

Re: [Dovecot] Corrupted index file
by Frank Hart 09 Feb '05

09 Feb '05

On Wed, Feb 09, 2005 at 02:55:51PM -0500, Michael Baird wrote: > Frank, exactly the same thing happened to me. Last week I tried to > migrate over to dovecot, from courier-imap for all the reasons you > mentioned, I ran into the Corrupted index file issue and had to cut back > to courier-imap. I am using dovecot for maildir as it appears you are, > however I specified an outside directory for index files (/var/indexes). > I have a few thousand people using my webmail/imap system so this issue > quickly became a big issue after the cutover. > > Regards > Michale Baird It was probably my own fault. Timo Sirainen noticed Edgardo Pezoa was using MH style filenames. And I did the same thing. My main inbox configured in procmail was $HOME/Maildir/new and it should be $HOME/Maildir/ (notice the slash at the end). Now, new mails have filenames such as 1107960126.14681_2.hive:2, instead of msg.uC:2,S. I never had this problem with courier so I didn't thought it could be a configuration error. Thanks everyone for the help. Timo's mail: http://dovecot.org/list/dovecot/2005-February/006215.html -- make install, not war

1 0

[Dovecot] Corrupted index file w/Procmail in FC2
by Edgardo Pezoa 09 Feb '05

09 Feb '05

Hello: We have a Fedora Core 2 (FC2) server with Dovecot and Procmail. Versions are: dovecot-0.99.13-4.FC2 procmail-3.22-13 We use "maildir" below home directory like: /users/operaciones/epezoa/maildir, where "epezoa" is my account. If I receive an e-mail, is stored at "new" folder. When I try to get e-mail from server, message is transfered from "new" folder to "cur" folder, but I can't see my e-mail and Dovecot generates a "Corrupted index file" in log file: Feb 8 14:02:34 dlp1 pop3(epezoa): Corrupted index file /users/operaciones/epezoa/maildir/.INBOX/.imap.index: index.next_uid (14836) > uid_rec.uid (14825) But, If I receive another e-mail (at "new" folder) and I try to get messages, I get both. My clients are Mozilla (with "pop3") and Squirrel (from another server with "imaps"). Both have same behavior, so I think client is not involved in this problem. MTA is Postfix, but all accounts works well, except who use Procmail. I read about locking in Procmail and Dovecot and I think locking may produce this problem, but I can't find what's wrong. I upgraded dovecot from dovecot-0.99.10-5 to try fix this. Thanks in advance, -- Edgardo Pezoa

2 4

[Dovecot] 0.99.14-rc2
by Timo Sirainen 09 Feb '05

09 Feb '05

http://dovecot.org/rc/ I should have released 0.99.14 already, but I've been way too busy lately. Among other things I started working half-time at Movial (www.movial.fi) I had forgotten 8 hour work days at office could take so much time :) Anyway.. There has been a few changes since RC1 so I'll still make RC2 before the final. Changes since RC1: - passwd-file userdb wasn't working - PAM crashed with 64bit systems - non-SSL inetd startup wasn't working - upgraded setuid/setgid initialization code from 1.0-tests

1 0

[Dovecot] New user Q: dovecot-0.99-13 / UnixWare 7.1.0
by Steven Palm 09 Feb '05

09 Feb '05

Trying to get dovecot up and running. I managed to get everything compiled and linked correctly, but there seems to be some problem with either the auth process or communication between the main process and the auth process. When I try to login, I get: * OK dovecot ready. 1 login n9yty testing * OK Waiting for authentication process to respond.. And I keep getting the same message over and over until eventually it dies if I let it sit: * BYE Disconnected for inactivity. In the log, all I see is: dovecot: Feb 05 02:24:46 Info: Dovecot starting up imap-login: Feb 05 02:32:46 Info: Disconnected: Inactivity [127.0.0.1] I have this in my config, but yet that is all the logging I see: auth_userdb = passwd auth_passdb = shadow auth_verbose = yes auth_debug = yes I then tried to do ./configure with --enable-debug, but if I do that I get this in the log when trying to run dovecot: dovecot: Feb 05 02:08:01 Info: Dovecot starting up dovecot: Feb 05 02:08:03 Error: Auth process died too early - shutting down dovecot: Feb 05 02:08:03 Error: child 8441 (login) killed with signal 6 dovecot: Feb 05 02:08:03 Error: child 8440 (auth) killed with signal 6 (sometimes the (login) line is not send, but always (auth)) Any thoughts on where to next start tracking this down? I tried to use test62, but get this (haven't dug much further into this one since I'd like a stable release for this application): main.c: In function `listen_protocols': main.c:284: error: structure has no member named `_listen' main.c: At top level:

2 2

[Dovecot] possible bug in 1.0-test62
by Dominik 'Rathann' Mierzejewski 09 Feb '05

09 Feb '05

When connecting with mutt via IMAPS, I get "connection to server closed" and this appears in logs: dovecot: Feb 04 12:48:30 Error: IMAP(rathann): file mail-index-sync-ext.c: line 118: assertion failed: (size <= synch_size) The problem goes away after deleting the index from ~/Mail/.imap/INBOX. We're running 1.0-test62 on Solaris 9. -- Dominik 'Rathann' Mierzejewski <rathann*at*icm.edu.pl> Interdisciplinary Centre for Mathematical and Computational Modelling Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810

2 1

[Dovecot] File isn't in mbox format - Couldn't open INBOX
by Girish Patangay 09 Feb '05

09 Feb '05

I cannot reproduce this error everytime, but it seems to happen when Outlook tries to delete the first message (the first message in the file, message on top) in the /var/mail/user file. I tried looking through the mailing list but came up blank. Is this a known problem? I can fix this problem by editing the file manually and fixing the file. If I delete the first 2 lines (in the example below) and make sure the Inbox file starts at "From ..." it works fine again. Here is the log: ---------------------------------------------- Feb 2 09:23:45 angel pop3-login: Login: sathyan [127.0.0.1] Feb 2 09:23:45 angel pop3(sathyan): File isn't in mbox format: /var/mail/sathyan Feb 2 09:23:45 angel pop3(sathyan): File isn't in mbox format: /var/mail/sathyan Feb 2 09:23:45 angel pop3(sathyan): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-02-02 09:23:45] ---------------------------------------------- The inbox file for this user looks like this: ---------------------------------------------- [root@angel mail]# head sathyan zenxoI6Jdi_xPyRoBhrhf-- >From caecelius(a)payaway.every1.net Wed Feb 2 07:03:36 2005 Return-Path: <caecelius(a)payaway.every1.net> ---------------------------------------------- -- ------------------------- Girish Patangay <girish(a)intoto.com> Intoto Inc <www.intoto.com> Phone: 408.844.0480x304 Fax: 408.844.0488 PG ID: 0x74D3A118

2 1

[Dovecot] assertion failed in imap-bodystructure.c
by Martin Preen 09 Feb '05

09 Feb '05

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird) and that seemed to cause this error. What does that mean ? Should I worry about ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee, Geb.52, Zi.00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 1