similar to: Panic: Message unexpectedly expunged from index

Nevermind. I figured it out. I left off the INDEX command. Sorry to spam the mail list :( Here is my mail_location for future reference / searches: mail_location = mbox:/var/spool/mail:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u -----Original Message----- From: dovecot-bounces+chayes=afo.net at dovecot.org [mailto:dovecot-bounces+chayes=afo.net at dovecot.org]On Behalf Of Cliff Hayes

Hi I am using dovecot 2.0.9 on CentOS 6.4 The following error appears in the logs when users connect to the imap server using MACs. All other clients that I tested work fine. ###### BEGIN ERROR ###### Jan 5 18:04:25 mail dovecot: imap(jcf): Panic: file mailbox-list-maildir.c: line 133: unreached Jan 5 18:04:25 mail dovecot: imap(user): Error: Raw backtrace:

Mar 29 10:57:02 k8ux dovecot: POP3(stf): mbox sync: Expunged message reappeared in mailbox /var/mail/stf (UID 123 < 60016, seq=2, idx_msgs=0) Mar 29 10:57:02 k8ux dovecot: pop3-login: Login: user=<stf>, method=... Mar 29 10:57:03 k8ux dovecot: POP3(stf): mbox sync: UID inserted in the middle of mailbox /var/mail/stf (60016 > 123, seq=2, idx_msgs=1) Mar 29 10:57:03 k8ux dovecot:

Hi, we have upgraded from v2.0.1 to v2.0.3 yesterday, trying to solve the "dovecot-uidlist: Duplicate file entry" errors. Now, at the moment, we don't get these errors, but when I try to expunge mails from my trash folder I get a lot of errors: Sep 23 14:24:51 imap1 dovecot: imap(user): Error: Mailbox Trash: Expunged GUID mismatch for UID 20193: 442b5ef0c3d3bf3cf4cb619944dce8e4

Hi Timo and Everyone.... There is a way to know when a folder it's been deleted ? And if this folder is empty ? Let's explain why... I intercept the expunge function, to treat my files expunged, but when i expunge a folder, this function it's not called, and my emails don't get my treatment to be expunged. Basically i need to do something like this: It's empty ? No -->

Hy Everyone...and Timo ! There is a way to know if a email was expunged (deleted from hard disk) inside a plugin ? I rewrite the expunge function, but the real expunge function is void, i can't know if was really expunged. There is a way to know this ?

Hi, I'm using dovecot-2.2.18 on fedora22 and receiving the following messages: Sep 26 11:07:52 orion dovecot: imap(dave): Error: Sync failed for mbox file /var/spool/mail/alex: Expunged message reappeared to mailbox (UID 267101 < 267175, seq=2, idx_msgs=0) How do I troubleshoot this? Any idea what could be causing it? I've included my doveconf below. # 2.2.18:

Please help. How to stop email replication is on going. dsync-server : Warning Expunged message reappeared, giving a new UID

Hello, Following on my last question about broken mdboxes, removing dovecot.map.log and force-resync does work. My last problem now however is that after doing this, messages which were 'deleted' previously, come back in the inbox as new messages. I have the original mailboxes and can subscribe to the expunged folders and everything in EXPUNGED/INBOX on the original, is appearing in

You can use mdbox_deleted driver to access mails with refcount 0. See https://wiki2.dovecot.org/MailboxFormat/dbox Aki On 10.11.2020 12.42, Daniel Sch?tze wrote: > > Yesterday I had to recover an e-mail which a user had deleted.? If I > understand this correctly the message was expunged but not purged > (doveadm purge had not been run). > > This e-mail was clearly still in the

Hello, In some conditions with FTS enabled I get this warning: Warning: Expunged message reappeared, giving a new UID Here is how I can reproduce it: I have a test setup with a (postfix) virtual alias multi-alias at example.com which delivers emails to user1@ and user2@ If * I send an email to multi-alias@ * expunge user1@ mailbox with doveadm expunge -u user1 at example.com mailbox Inbox

Hi all, I'm doing some testing between U of Washington IMAP server (which we currently run) and Dovecot on a IBM AIX system. I created a 50M mailbox, made up of 262 msgs. I'm using a Perl Script with the imap::client module to fetch each message and then flag it for deletion. At the end of the test, I run an expunge to delete all the messages. UofW imap server ran fine, messages

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

Upon upgrading from 1.0.2 to 1.1rc4 I see this error for many of our users: Getting size of message UID=1 failed Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged Logging in with IMAP I would see a bunch of messages with no subject or time and blank bodies (usine horde/imp). Removing dovecot.index.log, dovecot.index.log.2, or dovecot-uidlist fixes the problem

Dovecot 2.2.27 dsync-server(account_name): Warning: Maildir /usr/local/vhosts/mail/*******/info/Sent: Expunged message reappeared, giving a new UID (old uid=29787, file=*******) What triggers this replication for ever ?? Thank you George

Hello, So i had this email in my inbox, i moved it to Folder1/tickets/ folder, then i decided to move the same email back to my inbox and when i went to the inbox it wasnt there nor in Folder1/tickets/ folder... I opened a SSH session to the mail server and went to /srv/mail/ vmail/DOMAIN.COM/rventura/Maildir There i did "ll expunged/.INBOX/cur" and it showed me 300+ emails

Hello List, with dovecot version 2.2.13.9, I actually have a problem using lazy_expunge and acl together. Shared/Public Folders work fine with lazy_expunge disabled. If lazy_expunge is enabled and userA got a shared folder form userB, then there is the error shown in subject. My test case to reproduce the error. doveadm mailbox list -u userA at domain --> Output Fine. doveadm acl set -u

Starting at 05:32 this morning, one user on my dovecot server is receiving hundreds of copies of old email. This is a short excerpt from my dovecot.log showing the problem: > dovecot: Nov 03 05:27:02 Info: pop3-login: Login: > user=<howard at obfusca.ted>, method=PLAIN, rip=::ffff:81.44.31.210, > lip=::ffff:zz.zz.zz.zz, TLS > dovecot: Nov 03 05:27:02 Info: POP3(howard at

Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u

I am running dovecot 2.2.2 with tcp based replication, and experiencing some duplicated emails. `doveconf -n` output is below. I have narrowed it down to the following scenario: An email arrives, and is successfully replicated to both nodes. It is in INBOX/new/ at this point on both servers. Connect with a mail client, and delete the message - without delayed expunge. So, for example, mutt