similar to: Expunged message reappeared to mailbox

Displaying 20 results from an estimated 4000 matches similar to: "Expunged message reappeared to mailbox"

2015 Aug 15
1
IMAP folder separator issue
Hi, I'm using dovecot-2.2.18 on fedora22 and having a problem with Thunderbird. I reported this problem some time ago, and received some tips, but no solution that's worked. I'm now trying to fix this in earnest, and having problems. The problem is sub-folders are created with a caret in them, instead of a new folder below the parent folder. So instead of folder/sub-folder,
2006 Nov 03
1
mbox sync: Expunged message reappeared in mailbox
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
2011 Mar 30
2
mbox sync: Expunged message reappeared in mailbox
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:
2015 Jul 19
2
IMAP Folder Mail Separator
Hi, >> I have a fedora21 install with dovecot-2.2.18, and when creating a new >> subfolder with thunderbird, the actual folder name is >> "Folder1^Folder2" with a carat as a separator, instead of creating >> Folder2 in the Folder1 directory. >> >> Is this a thunderbird problem? I don't recall having this problem >> prior to upgrading to
2015 Jul 19
0
IMAP Folder Mail Separator
On 07/18/15 20:41, Alex wrote: > Hi, > >>> I have a fedora21 install with dovecot-2.2.18, and when creating a new >>> subfolder with thunderbird, the actual folder name is >>> "Folder1^Folder2" with a carat as a separator, instead of creating >>> Folder2 in the Folder1 directory. >>> >>> Is this a thunderbird problem? I
2017 Mar 01
0
Expunged message reappeared, giving a new UID
Please help. How to stop email replication is on going. dsync-server : Warning Expunged message reappeared, giving a new UID
2020 Aug 01
0
Warning: Expunged message reappeared, giving a new UID with FTS enabled
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
2017 Mar 01
1
Expunged message reappeared, giving a new UID
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
2008 Mar 21
2
Question about log entry?
dovecot: POP3(knute): mbox sync: Expunged message reappeared in mailbox /var/mail/knute (UID 585 < 379664, seq=2, idx_msgs=0): 1 Time(s) dovecot: POP3(knute): mbox sync: UID inserted in the middle of mailbox /var/mail/knute (379664 > 585, seq=2, idx_msgs=1): 1 Time(s) I've been getting these lately. Any idea what causes them? Should I worry about it? Thanks, --
2013 Jul 26
3
Expunged message reappeared, giving a new UID
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
2011 Jan 10
1
Urgent problem: Dovecot fetches the same mails multiple times per POP
I have a problem since a couple of hours: I manage several mboxes on a virtual server using Dovecot (over POP3). Until a few hours ago, it worked well, but since 11:50, the e-mail clients which access Dovecot's mailboxes, receive all e-mails new each time the mailbox is queried. For example: 15:40 fetches 22 new mails 15:41 fetches the same 22 mails again as new 15:42 fetches the same 22
2015 Aug 30
0
CPU feature 'svm' not reported inside guest without 'host-passthrough'
Hi, I am confused by the behaviour of the CPU description in my VM. I have a host with an AMD CPU with SVM feature and I want to try nested virtualization on a Fedora22 guest. The host is Fedora22 as well. libvirtd (libvirt) 1.2.13.1 kernel 4.1.6-200.fc22.x86_64 1. I tried 'custom' mode with model qemu64 with required feature 'SVM' but '/proc/cpuinfo' in the guest
2009 Mar 24
1
Making changes to dovecot log levels
Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file
2006 Jan 24
1
dovecot 1.0alpha5 not deleting messages from mbox
Hi, I have had some problem with duplicate emails using dovecot1.0alpha5using the prebuilt testing binaries on a debian stable/testing 3.1system. I am running both pop3d and imap, but all users are just usingpop3d. I am using mbox format. Users are using Thunderbird 1.5 to access emails. Dotlocks are used,postfix is the email agent. Note that dovecot/[postfix are running in avserver. In
2008 Apr 04
2
Leave mail on server leads to dup messages
Hi. I'm a dovecot newbie. I've set my pop client to leave messages on the server for 7 days. I'm downloading the same messages over and over as dovecot appears to be overwriting X-UID's in the mbox's. I can't think of any other program on the system that might write to the mbox other than postfix (and that program doesn't appear to be writing X-UID). My setup has one
2008 Apr 12
2
Mailbox locking issue?
Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.
2005 Nov 21
0
Assertion Failure
Here's an assertion failure that just happened. Unfortunately, I don't have a core file so this may be useless... This is with CVS version from 2005-11-03. It looks like he expunges all of his mail. dovecot: Nov 21 17:37:20 Error: 13261 imap(username): mbox sync: Expunged message reappeared in mailbox /mailhome/new/b/n/username/mbox (UID 1008 < 1606, seq=816, idx_msgs=1238)
2020 Nov 24
1
Error: Mailbox INBOX: Sync failed
Just saw in my logfile this line appeared: imap(xxxxxx)<56614><CMMJw9i0aoBSsH9H>: Error: Mailbox INBOX: Sync failed for mbox: Expunged message reappeared to mailbox (UID 174550 < 174552, seq=11, idx_msgs=9) Looks like messages' UIDs are mixed up? I thought that if Dovecot sees broken X-UID headers for "new" messages, they're silently fixed? Can you tell how I
2007 Mar 10
4
pre-1.0.rc27: Index and mbox fixes
I've been doing some stress testing in the last few days and fixing all the errors I saw. I'm hoping that I've finally really fixed all the index/mbox problems. So, again I think the only thing left for v1.0 is the documentation. Please test this nightly snapshot before I'll release rc27 tomorrow: http://dovecot.org/nightly/dovecot-latest.tar.gz If you've seen any of the
2004 Jul 23
2
"Duplicate workgroup names in browse list" problem reappeared in 3.0.5
Starting from version 3.0.2 (or .3?) there were a misfeature that caused workgroup names to show up as duplicates in workstations' browse lists. Fix for this didn't reach into 3.0.5-pre1, but rc1 had this fixed. Today I upgraded 3.0.5-rc1 to 3.0.5-2 (FC2 binary rpm from samba.org) and the problem reappeared. To be more spesific, the problem appears when there are more that one workgroup