search for: uidvaliditys

After installing a new server with dovecot 1.2.4, I found there is some new dovecot-uidvalidity* files in user's Maildir directory. However, I did not see such files in other servers with dovecot 1.1.2 (around 2008/07). What is function of those files? What will happen if I delete that files? I am curious why need to keep 2 files: dovecot-uidvalidity dovecot-uidvalidity.4aa4fa4c since the

Hello, I'm running dovecot-1.1.8/Maildir/ACL plugin. I sucessfully set up a Maildir shared between users of the unix group 'doveshared' via a public namespace, unix permissions and ACL files. The location of my public namespace is /path/to/public. I tried 2 sub-setups : First setup ---------- drwxrws--- 4 root doveshared 4096 Jan 30 13:39 public -rw-r----- 1 root doveshared

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, I can't? locate the dovecot.index in my ~/Maildir [root at fedora-p24 Maildir]# ls cur????????????????? dovecot-uidlist?????????????? new dovecot.index.cache? dovecot-uidvalidity?????????? subscriptions dovecot.index.log??? dovecot-uidvalidity.4b1e77ef? tmp Where is the dovecot.index ? This tutorial http://wiki.dovecot.org/IndexFiles tells that I should find it where the other

...remained empty (i.e. no pseudo-message written to them), no uidvalidity-related helper file seems to have been created and no uidvalidity-related function seems to have been called. And clearly, both mailboxes "new1" and "new2" have received the same UIDVALIDITY. Those UIDVALIDITYs appear to be persistent; messages may be added to and deleted from those mailboxes, those mailboxes may be renamed... their UIDVALIDITY remain unchanged and equal to 1. In fact, any additional mailbox is created with that unique and persistent UIDVALIDITY of 1. Is this supposed to behave tha...

On Thu, 2020-04-09 at 13:48 +0300, Sami Ketola wrote: > > > > > On 31 Mar 2020, at 23.18, Ben Mulvihill <ben.mulvihill at gmail.com> > > wrote: > > > > Hello again, > > > > I am still stuck I'm afraid. > > > > I now have doveadm backup working perfectly from > > a small gmail mailbox (a few hundred messages), but >

Should I be considered with this log entry? rename(/home/vmail/jeff/dovecot-uidvalidity, /home/vmail/jeff/dovecot-uidvalidity) failed: No such file or directory

> On 31 Mar 2020, at 23.18, Ben Mulvihill <ben.mulvihill at gmail.com> wrote: > > Hello again, > > I am still stuck I'm afraid. > > I now have doveadm backup working perfectly from > a small gmail mailbox (a few hundred messages), but > when I try the same configuration (apart from usernames > and passwords obviously) with a large gmail mailbox >

Hi, the latest HG of Dovecot 2.0 throws a warning when creating a new mailbox inside an INBOX with 'mdbox' format. It does however create the mailbox correctly. ==> /var/log/dovecot.log <== Apr 24 14:35:09 spectre dovecot: imap(tlx at leuxner.net): rename(/var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity, /var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity) failed: No such

Running 2.0.beta5 on Mac OS X with HFS+J, I often see this error in the log: Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Error: mdbox /var/spool/imap/dovecot/mail/mailboxes/INBOX/Foobar/dbox-Mails: map uidvalidity mismatch (1273852899 vs 1273853949) Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Disconnected: Internal error occurred. Refer to server log

After the LOGIN do STATUS "User/somemailbox": a0007 STATUS "INBOX/Rechnung" (UIDNEXT UIDVALIDITY UNSEEN RECENT) a0008 STATUS "User/lists at example.com/Announce" (UIDNEXT UIDVALIDITY UNSEEN RECENT) a0009 STATUS "User/system at example.com/INBOX-root" (UIDNEXT UIDVALIDITY UNSEEN RECENT) a0010 STATUS "User/test at example.com/Shared" (UIDNEXT

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

Hello, I have an usual isshere we are using thunderbird for client. The version of dovecot is as followed: # dovecot --version 2.2.22 (fe789d2) The dovecot service is runnon on VERSION="16.04.6 LTS (Xenial Xerus)" Thunderbird version 68.3.1 (32 bit) version. What happening when managing subscription there seems to be folders that are missing. They were not purged nor did anything

Hi everyone I'm using isync 1.0.5 patched to do recursive folder listing and mirroring mail from an external party's IMAP server to a local Maildir, which will be accessed by Dovecot 2.0.9. In order to prevent IMAP clients from re-downloading their mail, when connecting to Dovecot, I'm busy writing a script to generate appropriate dovecot-uidlist and dovecot-uidvalidity files, per

Hey to all, is it possible to get rid of the "dbox-Mails"-folder when using sdbox? Currently my folder structure looks like this (I hope the output from tree would be formatted well): /srv/mail/ ??? example.com ??? ??? user ??????? ??? dovecot-acl-list ??????? ??? dovecot-attributes ??????? ??? dovecot.list.index.log ??????? ??? dovecot.mailbox.log ??????? ???

I tried to disable courier-pop3 today in favour of dovecot pop3. Prior to that I ran: find /home -maxdepth 1 -type d | xargs --replace /usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive --convert {} ( /home is hashed two levels deep: /home/a/a/aanton/Maildir/ ) After that, I got lots of errors like: Aug 9 13:02:40 postamt dovecot: IMAP(azenclu): Maildir

Regarding the dovecot-uidlist header (first line) - I've tried to search for and figure out what exactly is meant by the "mailbox global uid" and once I do, how to manually generate the 128 bit hex variation of it? Could someone elaborate on this, please. How would omitting the global uid field, beginning with G, affect remote clients' syncing of mail? Is this field mandatory?

Still not quite got my head around what you are expecting to see. Presumably folders for other dates in September. Depending on how and why those folders were created they may not exist. I do note that you used an ls to show the folders, and I'm assuming from the config below you are using Maildir, so try an ls -a to show the hidden folders too (those starting with a .). This should show you

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in

Package: dovecot-imapd Version: 0.99.14-1 Severity: important Hi, I think I've identified a bug in Dovecot 0.99.14 as packaged and distributed by Debian Sarge. I believe the bug lies in the original Dovecot source, not with any modifications made by Debian. Specifically, this bug deals with Dovecot's handling of message unique identifiers (UIDs) for IMAP clients when using the mbox