similar to: Maildir syncing rewrite

0.99.9 should really be released soon. There's been quite a lot of important fixes since 0.99.8.1. There's still some recent counter strangeness, but it wasn't perfect before either. mbox still doesn't necessarily notice flag changes unless they're written into index file (ie. non-Dovecots and Dovecot without index files). But it wasn't perfect before either.

Expunging messages caused those "Corrupted index file" errors. That's fixed now. There's probably still some problems, at least this fix didn't fix any crashes.. test3 available from http://dovecot.procontrol.fi/test/

Helo all, I'm working on a migration from qmail+courier+maildrop to postfix +dovecot1.1+lda and today the logs has too many strange messages like this: Jun 12 10:51:22 mailserver03 dovecot: IMAP(xxxxl at xxxx.com.br): Broken file /data/services/dominios/xx.com.br/m/ma/mapel//Maildir/.Sent/dovecot-uidlist line 29: UID larger than next_uid (535 >= 535) Jun 12 10:51:26 mailserver03 dovecot:

http://dovecot.procontrol.fi/test/ Maildir syncing now works pretty much as described in my earlier mail. It was quite a large change, so please test this :) So the new and great features: - It's faster. - If someone renames maildir file just before we try to use it, we now resync the maildir and try to find it again. Before we just failed. It's also possible that the filename changed

Hi- I was able to get a coredump out of the new pop3 (from 0.99.9-test4) by attempting to simulate the execution environment and simply running the pop3 program. Running the older pop3 from 0.99.8.1 works fine, repeatedly: % /usr/local/libexec/dovecot/pop3 quit +OK Logging out. However running the new one: % /usr/local/libexec/dovecot/pop3.new pop3(user9): Error: Corrupted index file

Hi, guys. I'm attempting to transition between Courier IMAP and Dovecot. I may not be able to transition all the courierimapuiddb files instantly or even transition all my servers at the same time. Ideally, it wouldn't matter. Users can login and get to a Courier IMAP machine or a Dovecot machine and read their email (all mounted via NFS). My question is: is there any reason I can't

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas

Hi, I'm testing migration from courier to courier-0.57.0 to dovecot-imap-1.1.12 on a debian/sid box. When running the migration script, non of the active users' "courierimapsubscribed" and "courierimapuiddb" files seem to be detected: ZENON:~# ./courier-dovecot-migrate.pl --to-dovecot --recursive /home Testing conversion to Dovecot format Finding maildirs under

Hi, we use a current Debian etch distribution as basis for our servers, which are running within a vmware server environment. Our current configuration consists of a dovecot server with imap enabled and a ldap based authentication. Mails are stored using the Maildir format on a central nfs store. We do not use any virtual mailboxes. Since upgrading from dovecot version 1.0.rc15 (debian

Hello Gang, I am new to dovecot and the only reason (so far) I would like to use dovecot, and in production with 12k+ users, is the fact that it's supposed to be faster and less of a resource hog. Now, sometimes I am really good at reading the documentations but it sometimes happens that one overlooks something. I did read the migration notes three times! My users are in /etc/passwd and I

This was ment for the list :) Sorry Stuart, for the double email... Regards, Maikel. > -----Original Message----- > From: Maikel Verheijen > Sent: Friday, July 25, 2003 3:40 PM > To: 'Stuart Henderson' > Subject: RE: [Dovecot] Is dovecot NFS safe? > > > Hi, > > Be aware that also your .subscriptions file and .customflags > are not nfs safe (yet)

Hi- Tried 0.99.9-test2 -- had to go back. Various problems in the log. Here's one: Apr 10 08:56:25 mercury mem[10754]: imap(user0): msync() failed with index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Cannot allocate memory Apr 10 08:56:25 mercury mem[10754]: imap(user0): Corrupted index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Missing location field

We recently upgraded to version 2.2.10-8 on Centos 7 (from 2.2.10-7) and immediately started experiencing errors in the log file that look like this: Error: Broken file /mail/user/Maildir/dovecot-uidlist line 891: Invalid data: Error: Timeout (180s) while waiting for lock for transaction log file /mail/user/Maildir/dovecot.index.log Error: /mail/user/Maildir/.Trash/dovecot-uidlist: next_uid was

I performed a hg pull today for 1.0.1 and after recompilation my log was flooded with: Jul 12 10:29:21 postamt dovecot: IMAP(kxx4): UID larger than next_uid in file /home/k/j/kxx4/Maildir/dovecot-uidlist (6 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(rexxxes): UID larger than next_uid in file /home/r/e/rexxxes/Maildir/dovecot-uidlist (1 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(sxxkim):

Hi There A while ago I posted here about a crash of dovecot, that had to do with nfs and was quite certainly due to bad luck. But still one problem persists: We have a Mailbox, that is accessed from multiple users using IMAP. Occasionally all the Emails in the mailbox seem to be missing, when accessing the Mailbox through IMAP, although they're still there on the server. This seems to

http://dovecot.org/test/ I have very high hopes that mbox support is finally stable in this version. I've been running some stress tests for an hour now without it breaking (well, there are two potential problems but I think they were just fixing previous breakages). Before it took only a few minutes at most to break. - fixes several mbox syncing problems, especially expunges

I'm having the following problem and would appreciate any help or tips on how to fix it. None of my users can send email via pop3 or imap clients the only consistent thing that i keep seeing in the logs are the following 2 messages: UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist sync: UID inserted in the middle of mailbox After searching the web all I can find is this

Hi all, This is probably a silly question, but I have a problem. I've had to move my users maildirs from: maildir:/home/%u/.Maildir To maildir:/data/mail/%u I've updated the MTA to put mail to the correct place and it's working fine. I've also changed the dovecot.conf file and restarted dovecot and I thought that would be all I needed to do. However, the users are getting

> On Oct 12, 2017, at 8:56 AM, Bill Shirley <bill at KnoxvilleChristian.org> wrote: > > Is everyone's email going to /mail/user/Maildir ? > > What's the output of 'dovecot -n' ? > > Bill > > On 10/12/2017 9:47 AM, List wrote: >> We recently upgraded to version 2.2.10-8 on Centos 7 (from 2.2.10-7) and immediately started experiencing errors

Hi, Currently we support Courier POP and IMAP for all our users (users can use IMAP as well as POP at the same time). We are thinking about moving to Dovecot; but first moving away from Courier IMAP to Dovecot IMAP (and maybe later also move to Dovecot POP). This would create a mixed environment; after some research I have the following questions. To not break POP3 Courier and still be