similar to: Dovecot 1.0-stable mbox performance and disconnections

I've been struggling with an odd bug in the latest 1.0-stable (20050427) release. Sometimes Dovecot seems to forget that a message has been read or deleted and marks it unread (or not deleted). As far as I've been able to determine, it seems to happen when 1) There have been several recent deliveries 2) Possibly some of those deliveries are of multiple messages 3) Possibly they are read

I've tried turning on mbox_very_dirty_syncs for myself (and a few other brave souls running 1.0-alpha3 rather than 1.0-stable) again to see what perfomance gain it gives (see thread http://www.dovecot.org/list/dovecot/2005-July/007956.html). Now we aren't running UW-IMAP at all, how safe is mbox_very_dirty_syncs assuming the only other process writing to mailboxes is our MTA (exim) which

With 1.2.11 and mbox storage, the delay time in pulling new mail headers to the client from imap folders seems to be directly proportional to mailbox size, regardless of the number of new messages. At present, if the mailbox is large, pulling new headers is rather painfully slow. Is this expected behavior? Especially given that the client already has all the "old" mails in the folder

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18

I'm still collecting user feedback after moving from uw-imap to dovecot development release 1.1.rc3. What said in the subject seems the obvious result of an improper configuration. Office emails are configured and accessed on multiple clients with the same automatic filters, and sometimes the filtered emails get duplicated on the destination folder. The fact is that this was perfectly

Hi, We are using mbox and UW IMAP, and are having issues because UW IMAP does not support multiple client access when you use NFS for the mail files. I've done some research (see the comments after my 2 questions below), and most of the other major IMAP servers simply don't support it (courier is about the only one that has a positive comment). How much testing have you done

Hmm, this is peculiar! This mailbox has been unchanged on my test server since September. I've been using it to test each new version of Dovecot just after I've compiled it. When beta1 was released, I opened this mbox with no problems. However, when I upgraded to beta2, I got "file size unexpectedly shrinked in mbox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)".

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

Hi, We're trying out Dovecot to see if it's a good replacement for UW-imapd. It seems to be very slow in opening an mbox file, even after it's been indexed. (I mean way slower than UW) Here's some info on the system: Dovecot-1.0-test61 SuSE 8.1, Linux kernel 2.4 Using NFS to access mail. I've tried turning off mmap, using dotlocking, using fcntl locking (lockd, etc. are

Hi all, Sorry for the longish post! I've been looking at using rsync to mirror our mailstore (BSD/mbox format, i.e. flat files consisting of concatenated plaintext messages) to a NetApp Nearstore (basically a filer with SATA rather than FC disk) mounted over NFS. I want to do this in such a way that the NetApp automatic snapshots are kept as small as possible, so hopefully several versions

I just upgraded my Ubuntu server from 11.10 to 12.04.1 and that upgraded Dovecot to 2.0.19. For some reason I'm getting a lot more (5 times) disconnect in IDLE and inactivity time outs. I'm using only IMAP with two users. Both users access the server from multiple devices, phone, tablet and desktop computer. I had previously set the max_userip_connections to 20 and rarely got the

Hi, there! Well, I am new to dovecot, so please be patient with me: I have a virtual server and want to setup simple mail delivery. postfix, saslauthd and dovecot basically work fine. The only open issue is, that (I guess) dovecot doesn't remove the mail when it's retrieved via pop3 from the server. It keeps sending me the same emails again and again. (The mail client (Thunderbird) is

Hi, I am using dovecot: 1.0.rc15 I was upgrading Debian and installed new versions of lots of things. My mail came fine and I though there was not problem until a user called and said it was not working through webmail. I tried, it it worked fine and I realized the problem was with dovecot. I have created new users, tried different UIDs. Removed any protections but when I telnet to the

I've tried this on both Solaris 8 and SuSE Enterprise 9 (64-bit). I get a assert-crash when using a gzipped mbox folder . OK Logged in. . SELECT test.gz * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Label4 $Label2 $Label1 $Label3 $Label5) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 167 EXISTS * 0 RECENT * OK [UNSEEN 2] First unseen. * OK [UIDVALIDITY 1096038620] UIDs valid * OK

... Version from April 26, gives me the following errors in the imap log file : dovecot: May 04 09:56:58 Error: IMAP(m6933192-4): file mbox-sync.c: line 1262 (mbox_sync_do): assertion failed: (sync_ctx->ibox->mbox_sync_dirty) dovecot: May 04 09:56:58 Error: child 10721 (imap) killed with signal 6 This occurs sporadically and vanishes after some time. Is this something to worry about or

Hi Timo, Just a quick question: do index files still need removing when upgrading from 1.0-stable (as in the testXX series) or will Dovecot regenerate them automatically? I'm expecting to go with 1.0-stable on Tuesday for my 20,000 users (as that's what I've been testing), but if we see lots of index issues, I may want to upgrade to alpha1 (or later) fairly soon afterwards and it

On 12 Jun 2017, at 2.09, M. Balridge <dovecot at r.paypc.com> wrote: > >> I think it's just doing a lot of work on the mbox file itself >> (reading/writing/rewriting). Would be nice of course if it logged >> more information, but mbox format is a bit too legacy to spend >> much time on improving. > > I suspect the (heavy) use of procmail on Herr

Hi all, I'm using dovecot v2.0.11 on fedora14 with postfix. This system was migrated from an old UW mbox system, so users already have ~/mail/INBOX.* files. Now for some reason, dovecot is creating ~/mail/mail/INBOX.* files and somehow not seeing the mail_location properly. I've set mail_location to "mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u", which has worked on a

Hi, I was wondering whether anybody has managed to get Dovecot 1.0 to store INBOX as Maildir and folders as mbox. I've tried something like default_mail_env = mbox:/folders/user/mail:INBOX=maildir:/inboxes/maildir/user:INDEX=/indexes/user but it doesn't seem to work (treats INBOX as mbox). I'm hoping to move some INBOXes from mbox on local disk to Maildir on nicely-mirrored NetApp

I've got several users testing Dovecot IMAP at the moment, but some of them are also accessing their mail via UW-IMAP at other times. (I've warned them about accessing the same folder simultaneously via UW-IMAP and Dovecot!) In addition, we have special folders "AutoSpam" and "Trash" that pruned using Washington's "mailutil" automatically every so