- dovecot - dovecot.org

[Dovecot] Failed to create storage with data
by Tim Middleton 01 Apr '04

01 Apr '04

Switched from UW-IMAP to dovecot a little while ago. Worked through the namespace hell with current users. But now I've hit another problem I can't seem to figure out. Some webmail (squirrelmail) users noticed that when they tried to login they would jus get this error: ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY I discovered in the mail logs the real error was like this: Apr 1 04:28:38 smaug imap(mcfletch): Invalid mbox file /var/mail/mcfletch: No such file or directory Apr 1 04:28:38 smaug imap(mcfletch): Failed to create storage with data: mbox:/var/mail/mcfletch And the error seems to be quite accurate. These are new logins seeing this error, which do not yet have an mbox file. So the question is, why is dovecot not able to deal with this situation? Searching google i saw the suggestoin to one preson that it was actually the ~/mail directory unable to be created, but this is not the case in my test above, as ~/mail already existed for that account. Directory permissions seem okay. /usr/mail is drwxrwxrwt (note: /var/mail is a symlink to /usr/mail on this system). The dovecot setup is fairly default. Platform is FreeBSD 4.9. Authentication is done via system password file. There's no problem accessing/modifying existing mailboxes. I put in a chron job to touch into existance any non-existing mailboxes for everyone in the passwd file periodically, which mostly eliminates the problem. But I'd still like to know why the server is having the problem, if anyone can make any suggestions. -- Tim Middleton | Cain Gang Ltd | "Are the gods not just?" "Oh no, child. x(a)veX.net | www.Vex.Net | What would become of us if they were?" (CSL)

1 0

[Dovecot] Mulberry problem
by Rick Jones 01 Apr '04

01 Apr '04

I've been chasing a problem with Mulberry which now actually seems to be a Dovecot server bug. The problem manifests itself when manipulating embedded rfc822 messages, and the analysis comes down to the fact that a FETCH BODY[2] command returns the same thing as FETCH BODY[2.1]. Both return just the text of the embedded message, whereas FETCH BODY[2] should return everything including the headers (this is what Cyrus Daboo came up with after looking at the Mulberry log). I'm not sure exactly what version of Dovecot I'm running, it's what comes with SME Server 6.0. Has this by any chance been fixed? I have another Mulberry problem which might be related, but I'll save that for another post :) -- Regards Rick Jones

1 0

[Dovecot] Rogue child imap processes when using Mac imap clients
by darren david 31 Mar '04

31 Mar '04

hi all- I am currently running dovecot 0.99.10p2 on OpenBSD-3.4-snapshot. It has been very stable, but I have recently noticed that I am having problems when checking IMAP-SSL mail with Mac OS X clients. There are not problems using Mozilla or Outlook on Windows, but Mac clients (Thunderbird, Mozilla, Mail.app) all exhibit the same behavior - they can check and send mail, but I end up with a single, rogue child imap process on the server that pins the cpu that i have to 'kill -9' to clear out. Is this a Mac problem or a Dovecot problem? I'm not even sure what to look for in the logs... Thanks, Darren David

6 9

[Dovecot] New indexing code
by Timo Sirainen 31 Mar '04

31 Mar '04

Sorry about the lack of replies to questions in this list. Work on the new indexing code has taken way too long, but it's finally beginning to be get near usable state. After it's fully working, I'll start being more active here again. If you're interested (as a developer, normal users shouldn't even try playing with it yet), you can checkout "newdove" module from Dovecot CVS. Many things are still broken, but basic maildir support is almost working with the exception of expunges (which probably break badly) and custom flags (not implemented). And the maildir syncing code isn't optimized yet. Don't try it with any of your real maildirs, it might lose your mails. Some of the new great things in it: - Mailbox API which is a lot more easier to use than before, allowing a lot of things that previously were difficult to implement - Less IMAP-specific than before - Should work extremely well with shared mailboxes with tons of users I'm hoping to get a usable alpha release out of it within few weeks.

2 1

[Dovecot] Fatal: RAND_bytes() failed
by Anders Nielsen 30 Mar '04

30 Mar '04

This morning dovecot died with the following messages in the errorlog. Any solution to this problem? I am using Fedora Core 1 on a SMP i686 box. imap-login: Mar 30 08:08:00 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded dovecot: Mar 30 08:08:00 Error: Login process died too early - shutting down dovecot: Mar 30 08:08:00 Error: child 21354 (login) returned error 89 Best regards Anders Nielsen -- Anders Nielsen <anielsen(a)diku.dk>

2 1

[Dovecot] (no subject)
by tom＠replic8.net 30 Mar '04

30 Mar '04

hello, suddenly, dovecot stopped working. login succeeds, then no mail is displayed to the user. i upgraded to latest nightly, no change. ==snip== Mar 30 10:17:31 commbox imap-login: Login: user [192.168.99.66] Mar 30 10:17:31 commbox imap(user): Buffer full (49) Mar 30 10:17:31 commbox dovecot: child 745 (imap) killed with signal 6 ==snap== some minutes later i tried another client - i was using php-based horde/imp webmail system first (php uses cclient2000 for imap which is based on uw-imap afaik) - using syslphed-0.99 things work fine. strange. any hints on how to debug this more? -- thanks, TOM

1 0

[Dovecot] error starting dovecot
by Avery Day 30 Mar '04

30 Mar '04

I am running redhat 9.0. I have been using uw-imap for some time now and wanted to try our dovecot. After installing dovecot and trying to start it up I am getting an error ------------------- Starting IMAP daemon (dovecot): Fatal: Can't use SSL certificate /usr/share/ssl/certs/dovecot.pem: No such file or directory ------------------- Thanks for any help.

2 2

[Dovecot] UW-IMAP -> Dovecot : patch to remove nasty "internal messages" from UW-IMAP ?
by Xavier Beaudouin 29 Mar '04

29 Mar '04

Hello there, We want to move from UW-IMAP to Dovecot (mbox format), works like a charm, but UW-IMAP has that bloody habbit to make a stupid message in all his mailbox files : From MAILER-DAEMON Thu Apr 19 10:30:01 2001 Date: 19 Apr 2001 10:30:01 +0200 From: Mail System Internal Data <MAILER-DAEMON(a)mailhub2-vil.isdnet.net> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <987669001(a)mailhub2-vil.isdnet.net> X-IMAP: 0987630138 0000000001 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. Is there any patch / trick / whatever to avoid that such "stupid" message to be not served by dovecot ? Thanks, /Xavier

5 7

[Dovecot] IMAP error with squirrelmail - how to debug?
by Raymond Scholz 29 Mar '04

29 Mar '04

When moving messages with squirrelmail (or kmail), I get the following error: ERROR : Could not complete request. Query: COPY 3 "INBOX" Reason Given: Unexpected EOF According to the config I switched on rawlog: # This would write rawlogs into ~/dovecot.rawlog/ directory: mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap rawlog.c was altered in order to have /tmp as HOME. But I see no logfiles being generated. Environment: lastest dovecot from CVS, vpopmail and local users (error with both types). Another issue: Ocassionally the auth process dies: Feb 26 21:08:49 servername dovecot: child 28641 (auth) killed with signal 11 Cheers, Ray -- Raymond Scholz - rscholz(a)zonix.de - GnuPG/PGP - http://www.zonix.de/

3 4

[Dovecot] dovecot tls configuration
by Johannes Berg 29 Mar '04

29 Mar '04

Hi, I looked through the web and the list archives, but couldn't find how to set up the following: - dovecot with ssl/tls enabled - login from localhost allowed with and without tls - login from remote hosts only allowed via tls Is that possible at all? I'm using debian/unstable so its version 0.99.10.4-3. Thanks, johannes -- http://www.sipsolutions.de/ Key-ID: 9AB78CA5 Johannes Martin Berg <johannes(a)sipsolutions.de>

4 4