similar to: purge causing reappearing mails?

Displaying 20 results from an estimated 700 matches similar to: "purge causing reappearing mails?"

2019 Sep 02
1
purge causing reappearing mails?
Any idea what?pid 7584 is? Aki On 2.9.2019 14.08, telsch via dovecot wrote: > Hello, > > today i got reappearing mails again, but not from purging. In the logs i > only found this. I've got massive problems by many users because > reappearing mails. If you need more information, i could provide. > > > Sep 02 12:58:43 doveadm: Warning: Transaction log file >
2019 Sep 02
0
purge causing reappearing mails?
Hello, today i got reappearing mails again, but not from purging. In the logs i only found this. I've got massive problems by many users because reappearing mails. If you need more information, i could provide. Sep 02 12:58:43 doveadm: Warning: Transaction log file /var/spool/mail/<user>/storage/dovecot.map.index.log was locked for 43 second s (mdbox storage rebuild) Sep 02 12:58:43
2013 Nov 13
1
Deleted messages reappearing
Hi all, in the last days, probably since I upgraded to 2.2.7, I'm seeing lots of deleted messages reappearing in my folders. This is after this error in the log: Nov 13 14:55:16 buzones2 dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=source_ip, lip=dest_ip, mpid=15510, TLS, session=<2bmiUA/rZACe4wQZ> Nov 13 14:55:16 buzones2 dovecot: imap(username): Error: mdbox
2013 Jul 14
2
constant Log synchronization error's
Hi, I am seeing constant "Log synchronization error"s in my logs. See later for an example. This is dovecot 2.2.4, pigeonhole 0.4.1, and postfix 2.10.1 (with mailbox_command = /usr/libexec/dovecot/deliver) on a Fedora 19 system. I am using packages from Atrpms so there are some patches applied - ask for details. The mailboxes have resently been moved from a i386 system. I have
2017 Aug 22
1
Error: mdbox .../storage: Duplicate GUID
Hi! When I force-resync a mailbox of mine, I see following output: # doveadm force-resync -u $USER $PATH doveadm($USER): Warning: mdbox .../storage: Inconsistency in map index ($X,$Y2 != $X,$Y2) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: mdbox .../storage: rebuilding indexes doveadm($USER): Error: mdbox .../storage: Duplicate GUID $G in
2017 Sep 18
2
sieve stopped working and doveadm mailbox list without -s shows less folders then with
Hi Aki, Am 18.09.17 um 11:13 schrieb Aki Tuomi: > On 18.09.2017 12:10, Ralf Becker wrote: >> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >>>> Dovecot 2.2.31 with mailboxes in mdbox format. >>>> >>>> Since a couple of days some mailboxes have the problem, that sieve
2020 Aug 20
2
Expuning & Purging doesn't fully remove emails?
Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated.??I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error:
2007 Nov 06
3
Various uidlist and index errors with 1.1 on NFS
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
2017 Jun 05
2
corrupted indexes rebuilding over and over
Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I
2017 Sep 18
1
sieve stopped working and doveadm mailbox list without -s shows less folders then with
Hi Aki, Am 18.09.17 um 11:22 schrieb Aki Tuomi: > On 18.09.2017 12:20, Ralf Becker wrote: >> Hi Aki, >> >> Am 18.09.17 um 11:13 schrieb Aki Tuomi: >>> On 18.09.2017 12:10, Ralf Becker wrote: >>>> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>>>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote:
2020 Aug 27
1
Expuning & Purging doesn't fully remove emails?
But is that not adviced in the manual[1]? I am also in the process of setting up dovecot behind a haproxy. Still testing with this. I was wondering why one would choose haproxy and not eg dovecot proxy (with director) [1] https://wiki2.dovecot.org/HAProxy -----Original Message----- From: Zelic Bojan [mailto:bojan.zelic at kudelskisecurity.com] Sent: woensdag 26 augustus 2020 23:39 To:
2008 Feb 27
4
Index corruption with squirrelmail.
Hi. I don't know if the problem is related with squirrelmail or not, but I started to have index corruption when I started to try squirrelmail. Some informaton about my instalation: dovecot 1.0.5-1 debian package with maildir squirrelmail 1.4.9a-2 debian package Some log information: dovecot: 2008-02-27 08:39:39 Warning: IMAP(<please don't send spam to me>): fscking index file
2015 Jan 21
2
Corruption of index files
Hi All, after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index". I tried flock and even dotlock, but the problems persist. The system is a VPS with an overlay filesystem which did work flawlessly with the old dovecot
2017 Jan 17
1
Reappearing emails
The dovecot version (2.2.10) we were running had a timing window problem in the context of replication (we use maildir on CentOS 7). After doing elaborate tests to isolate the problem, we wound up upgrading to 2.2.23. That fixed it, and that version has been very reliable. >> Recently we received a report from an Android IMAP user that emails that >> he deleted without reading
2015 Jan 25
2
Corruption of index files
Oliver Welter: > >after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of > >messages about corrupted index files in the syslog ("Error: Corrupted > >transaction log" and "Warning: fscking index file .. dovecot.index". > > > Some more debugging - I did a "fuser" on a broken dovecot.index file > and see a lot of stale
2012 Mar 06
2
Fscking warnings
Google tells me that these "should go away" but they don't. Seems to happen continuously while a user is viewing email. Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Archive/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Davies/dovecot.index Mar 7 09:29:52
2020 Sep 01
3
Deleted mail reappearing
Recently I upgraded dovecot quite a few major versions. Since then some mailboxes are experiencing deleted mail reappearing. It seems to be happening roughly once a day, but not for every mail client or mailbox, I have at least two clients with this issue: Thunderbird and Outlook. Storage is local under two partitions, one as alternative storage. # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
2012 Mar 09
1
dovecot Digest, Vol 107, Issue 20 Fscking warnings
Yes that is the google thread that I saw. I don't see the relevance of your reference to dsync. As I read the man pages for dsync it is used to sync separate servers, to make backups or to convert mailbox formats. When I upgraded from 1.2.15 to 2.1.1 I saw nothing in the doco to suggest that dsync was relevant to my scenario. In a previous thread here (Log sync errors), Timo suggested
2017 Aug 18
3
Inconsistency in map index
Hello, The following errors are constantly popping up for 2 accounts. I can't get it fixed, I did doveadm backup to another account, the same happens in the new account. I did doveadm force-resync, the problem persists. I'm using dovecot 2.2. 2017-08-18T11:46:12.472821881Z Aug 18 11:46:12 lmtp(ramon.lacerda at alliar.com): Warning: mdbox
2011 Mar 24
3
fstat no such file or directory error
Periodically, we will have users IMAP sessions get hung. Their client sees a message like: The server responded: 'SERVERBUG] Internal error occurred. Refer to server log for more information On the server, we see the following in the logs: IMAP(<username>): Transaction log dovecot.index.log: duplicate transaction log sequence (37) IMAP(<username>): fscking index file