similar to: mailbox.auto ignores dovecot-uidlist.lock

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

Is there a way to force Dovecot to rebuild dovecot-uidlist from zero? It seems deleting all indexes and dovecot-* files followed by "doveadm force-resync" is not enough? It just gets the same UIDs? Perhaps from Maildir filenames? But I would like to reset the uid of all mails. Thanks -- Tom

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve ->

hi: sometimes i can't use imap command to get mails, when this problem appear i find out the file dovecot-uidlist.lock appear at the same time . I don't know Why is this happening ? can you help me ? thanks !

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

Hello. As stated in my previous message, we have some old compressed maildir messages with incorrect sizes in the filename. These messages cause dovecot 2.x problems. I'm trying to write a script to crawl all our messages, check the actual message size and if necessary, fix the filename. However, when I do this, dovecot gives the message a new UID on next login. If I change the filename

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

Hi all, I've a dovecot server setup and occassionally clients cannot get mails from their inbox. When I inspect the maildir for that user, there is stale dovecot-uidlist.lock file, and imap process keeps waiting for release of the lock. Is there any other method to perform locking on dovecot-uidlist instead of using dotlock mechanism? It is creating maintenance problems if I need to remove

If I read the code correctly, only dotlocks are supported for locking of dovecot-uidlist. And I don't see any settings in the config file for it. As it turns out, dotlocks are very slow on my system, due to their implementation via hardlinks. Would it be possible to support other locking mechanisms for locking of the uidlist file? -jdb

Hi, I'm wondering if someone already implemented a compression script (and would like to share it) based on the step-by-step provided on wiki page of Zlib module. I can already do some find|xargs gzip .... but couldnt implement it completly as described on the wiki page. I know the suggested step-by-step is very detailed and probably a must simplier will be enough for almost

Hello, In what situations will Dovecot 1.2.11 rebuild its uidlist? I am using the maildir storage format, and I am also modifying the uidlist manually (so it's possible I could jack* things up). I have found some related code in maildir-uidlist.c: maildir_uidlist_next. 1) Blank filename or UID 0 2) Any UID not being greater than the proceeding UID 3) Any UID being greater than ~4 billion. 4)

https://bugzilla.samba.org/show_bug.cgi?id=5022 Summary: FreeBSD 4.11 - Compilation Fails - uidlist.c - gcc2 / gcc3 Product: rsync Version: 3.0.0 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

>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 >

After updating Dovecot, one of my servers keep spamming these errors in the log: dovecot: Nov 03 14:14:18 Error: POP3(foo at bar.com): Getting size of message UID=4402 failed dovecot: Nov 03 14:14:18 Error: POP3(foo at bar.com): Getting size of message UID=4402 failed dovecot: Nov 03 14:14:18 Error: POP3(foo at bar.com): Couldn't init INBOX: Can't sync mailbox: Messages keep getting

Hi, ?Am using dovecot-2.2.10-8 on Centos-7 and everything seemed to be totally fine for many years. Now am trying to migrate our on-premises mail server to the cloud and I had to get some statistics. I was doing that using the doveadm utility. Unfortunately I found that the numbers don't match if I check the real messages in my Maildirs. For some account doveadm was reporting number of

Tried that. It rebuilds index based on dovecot-uidlist. But not the dovecot-uidlist based on actual mail data. :( Fil On March 21, 2018 11:58:21 PM EDT, "@lbutlr" <kremels at kreme.com> wrote: >On 2018-03-21 (17:15 MDT), Dmitry Filonov ><filonovd at enders.tch.harvard.edu> wrote: >> Now the question is if there's any way to tell dovecot to rebuild

Hi all, Lets say I have a maildir which doesn't contain any dovecot files but has some emails lying around in it. If I add a message to this mailbox using deliver, dovecot creates the uidlist file with a single entry (the message that was just delivered). When I then log in to the mailbox, all the other messages are added into the uidlist file in the normal order (directory list order I

My dovecot server seems to randomly begin giving errors to pop3 users who try to fetch their email. Once this begins, they see no more new mail, though the mail is in cur. Running: dovecot-stable 20050501, Mac OS X 10.3.9 Log entries like this: May 2 19:35:18 caddy dovecot: pop3-login: Login: kim [24.22.16.169] May 2 19:35:18 caddy dovecot: POP3(kim): rename(/Users/kim/Maildir/

Hi, I have some problems with my own mail-client. To fix the problem I want to know if my dovecot-uidlist is correct. Here it is: cat dovecot-uidlist 3 V1207893082 N522 519 :1231251810.M890065P5870.SERVER,W=2188,S=2124:2,DS 520 :1231750443.M221593P17335.SERVER,W=2260,S=2211:2,S 522 :1231773105.M510336P24592.SERVER,W=2278,S=2229:2,S 523 :1231773105.M510337P24592.SERVER,W=2280,S=2231:2,S 524

How to lock dovecot-uidlist file before reading by an external program? [perl script]