similar to: RE: Lock problem - take 2

I have a scenario where I have two users, one account (user1) with it's own Maildir account, and another account (user2) (which I wish to see the same messages) with a symlinked Maildir to user1's Maildir.? I.E.: /home/user1/Maildir /home/user2/Maildir (where this Maildir is symlinked to /home/user1/Maildir) Both users are in a group together (usergroup), and so all of the permissions

On 2016-05-18 11:52, Aki Tuomi wrote: > On 18.05.2016 12:44, Tom Sommer wrote: >> I'm trying to lock down a maildir from modifications using >> dovecot-uidlist.lock, but when a user with mailbox.auto = create logs >> in, then the folder is created regardless of dovecot-uidlist.lock >> existing or not. >> >> Is there no way to prevent dovecot from

I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not. Is there no way to prevent dovecot from touching anything in a maildir folder? -- Tom

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

> 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 We've been using dovecot successufly for few month. Previous setup : solaris 8, postfix+LDA, mbox + index on NFS (Netapp), 2500 accounts Everything shared overs NFS, multiple servers connect to index, mbox. mail_location = mbox:/var/mail/mbox/%u:INBOX=/var/mail/%u:INDEX=/var/mail/indexes_dovecot/%u We had at first some issue with mbox locking, using lock_method = dotlock solve the issue.

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 in the log file that look like this: > > Error: Broken file /mail/user/Maildir/dovecot-uidlist line 891: Invalid data: > Error:

doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf line 27: Invalid size: $default_vsz_limit Have you though about fixing the configuration error? Bill On 10/12/2017 10:05 AM, List wrote: >> On Oct 12, 2017, at 8:56 AM, Bill Shirley <bill at KnoxvilleChristian.org> wrote: >> >> Is everyone's email going to /mail/user/Maildir ? >>

Hi, Up until yesterday, our environment which consists an NFS maildir file store with multiple front end servers, was working fine. We've verified that the server clocks and machines clocks are in sync. Starting yesterday afternoon, We are getting ~850 log entries of the form 'Timeout while waiting for lock for transaction log files' or 'Our dotlock file was modified,

Hello, We have recently implemented dovecot directors to resolve an ongoing NFS lock/corruption issue. Everything was working great! So we updated our servers from centos 7.3 to 7.7 and dovecot 2.2.10 to 2.3.8 This was a bit of a failure and we were getting spammed with corrupt index files and logs. After we clear the index files with rm rf/mail/d/e/username/Maildir/dovecot*, they just come back

I've been getting the following error fairly often, which tends to result in a corrupted dovecot-uidlist. dovecot: IMAP(example at example.com): file maildir-uidlist.c: line 1009 (maildir_uidlist_recreate): assertion failed: (file_size == (uoff_t)st.st_size) dovecot: IMAP(example at example.com): Raw backtrace: imap [0x80cb740] -> imap [0x80cb64a] -> imap [0x8070e58] -> imap(maildir

Hi I'm trying to build a cluster of two servers with dsync replication (based on http://wiki2.dovecot.org/Replication). My test setup works fine for very simple tests, I can log in to both servers, copy a message to one of the servers and it successfully apperars in the other account. But, if I try to copy a large amount of messages at once to one of the accounts, my maillogs get flodded with

Hi. That's my first post. it's driving me crazy. I'm trying to get dovecot working with vpopmail on Openwrt, an embedded linux-like OS for some routers . So actually my aim looks like get dovecot working with little hardware resources (32 MB of Ram, 8 MB of disk mem.) I've cross compiled it well(it looks like). the login against vpopmail works. using mmap it cannot even select

Hi, Whitbox Linux 3 (RHEL) Dovecot 1.0.rc29 Using NFS From time to time does all mail get re-downloaded to Thunderbird. I would believe this has something to do with an index problem. I upgraded to 1.0 a few months ago but that didn't work well so I installed version 1.0.rc29 which worked better but we still get this problem from time to time. DOes anyone know if it is a good idea to

I am trying to sync a set of maildir folders from a dovecot server and a different imap server on a different host. Using a perl tool called imapsync. The tool says the following about the two servers capabilities: >From capability : IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED To capability : IMAP4rev1 UIDPLUS CHILDREN NAMESPACE

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.

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the

Two nights ago I took a leap and extended my testing of dovecot 1.1 by replacing 1.0 for the approx 15 users I had on 1.0. At that time I also for the first time tried dovecot 1.1 in a load balanced 2 server configuration with indexes on NFS. I was hoping I did this right, using the mail_nfs params and 1.1 so fchown etc would flush the access cache, but I am getting a number of messages and

>From http://www.dovecot.org/list/dovecot/2008-June/031235.html: > > I have noticed that the entries in the dovecot-uidlist files don't seem > > to get updated when an email is deleted or moved to .Trash. It appears > > that this list list would just keep growing over time, being full of no > > longer used filenames, and must tend to increase its processing >

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