February 2005 - dovecot

[Dovecot] Problems with dovecot using Maildir on JFS.
by Jacob Robert Wilkins 12 Feb '05

12 Feb '05

Howdy, I have dovecot installed on CentOS (rhel3 clone), and I'm using Dag's dovecot package. I have postfix setup to deliver to Maildir, in /home. The /home volume was formatted with JFS. In this setup, both Outlook and Thunderbird would not show any new mail unless they were completely shutdown and restarted. I have moved /home to an ext3 formatted and all is well. Anyone have any insight on this? Thanks, jrw

4 6

[Dovecot] can i get a list about the describtion of all sources of dovecot?
by bigbox＠mails.de 12 Feb '05

12 Feb '05

I want to control, which user, when and what modify in their mailbox done. which sourcecode must i modify? Please

2 1

[Dovecot] Trouble with Dovecot
by Paul A. Novojeeloff 11 Feb '05

11 Feb '05

Hello! I'm trying the Dovecot as IMAP server, so I have one problem: I can log in to server, but nothing appears in mailclient and following message appears in log: imap(user): Feb 08 20:36:34 Fatal: We couldn't drop root group privileges dovecot: Feb 08 20:36:34 Error: child 21356 (imap) returned error 89 What could be wrong? Thanks for your answer. WBR, Paul.

4 8

[Dovecot] PoP3 AutoDeletion
by Cheema, Ravi 10 Feb '05

10 Feb '05

Qpopper has a compile time option '--enable-auto-delete Automatically delete downloaded msgs' Is there anything similar in dovecot. I'm trying to migrate from qpopper to dovecot any help is appreciated.

4 3

Re: [Dovecot] Corrupted index file
by Tero Ripattila 10 Feb '05

10 Feb '05

Hello guys, --On 9. helmikuuta 2005 15:25 -0300 Edgardo Pezoa <epezoa(a)safp.cl> wrote: > We have almost same problem: both using Postfix, Dovecot and Procmail > in different OS and with different MUA. For me, the key is > Dovecot+Procmail. I I've seen this too on OpenBSD 3.6-current. I' running Postfix w/ Dovecot. My users uses Mulberry, Mutt, Pine, Thunderbird, Outlook, Outlook Express, The Bat! as their MUA. > The question is: someone have a real fix? I'd love to hear about this too :-) Thanks, Tero -- Tero Ripattila -- Tero Ripattila Leenankuja 2 G 67 FI-02230 Espoo, Finland Telephone: +358-45-638 0242 Fax: +358-45-689 0743 E-mail: tero(a)ripattila.com WWW: http://www.ripattila.com

2 2

[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