Displaying 20 results from an estimated 40000 matches similar to: "Listing expunged messages"
2020 Aug 26
0
Expuning & Purging doesn't fully remove emails?
?I managed to figure this out.
Just wanted to follow up if anyone in the future encounters the same issue.
I am using HAProxy along with dovecot replication. When an email comes in... it is round robin'd to each of the 2 dovecot/postfix servers. I have postfix running on each server and it uses the local dovecot LMTP service for storing the mails.
We sometimes get surges of emails(hundreds
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:
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:
2010 Sep 23
1
Expunged GUID mismatch for UID error
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
2019 Jul 15
0
broken mdboxes
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/07/2019 09:00 Mike via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
</div>
<div>
2019 Jul 15
1
broken mdboxes
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/07/2019 09:22 Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
2019 Jul 27
0
corrupt mdbox index / zero mails showing in imap
On 25 Jul 2019, at 20.55, Mike via dovecot <dovecot at dovecot.org> wrote:
>
> Hi,
>
>
> I have recently migrated (under emergency conditions) a dovecot imap/pop
> based server to a new instance. The mailboxes used mdbox format and due
> to various screwups I had corrupt indexes. I thought I'd cleaned this up
> but then I found that this new instance hadn't
2019 Jul 25
2
corrupt mdbox index / zero mails showing in imap
Hi,
I have recently migrated (under emergency conditions) a dovecot imap/pop
based server to a new instance. The mailboxes used mdbox format and due
to various screwups I had corrupt indexes. I thought I'd cleaned this up
but then I found that this new instance hadn't been set up correctly for
nfs. Long story short, I still get users with new cases of corrupt
indexes. The symptom is imap
2020 Nov 10
0
Recovering expunged but not purged e-mails from mdbox with zlib compression
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
2017 Mar 04
0
mdbox Inconsistency in map index
After a (power)crash two accounts have been corrupted.
I tried to rescue things by running force-resync multiple times, but
that didn't work out.
Searching the archives, I found a recent suggestion (by Timo) to delete
the index files, but I'm not sure which files to delete and what the
consequences will be.
When I deleted ``storage/dovecot.map.index'' in an unimportant account
2012 Jan 31
1
force-resync fails to recover all messages in mdbox
To my understanding, when using mdbox, doveadm force-resync
should be able to recover all the messages from the storage files
alone, though of course losing all metadata except the initial
delivery folder.
However, this does not seem to be the case. For me, force-resync
creates only partial indices that lose messages. The message
contents are of course still in the storage files, but dovecot
just
2006 Aug 24
2
Messages not expunged
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
2010 Aug 30
1
Lazy expunge plugin - delete folder result error.
Hello
Is it a bug in lazy expunge plugin or am I missing something?
Dovecot v2.0.1 (c5111fb65b0b)
home = /mail/%Ld/%Ln
mail_location = mdbox:/mail/%Ld/%Ln/mdbox
sources.list - debian (squeeze)
..
deb http://xi.rename-it.nl/debian testing-auto/dovecot-2.0 main
Config changes
- - -
plugin {
lazy_expunge = .EXPUNGED/
}
namespace {
type = private
separator = /
prefix =
inbox = yes
2012 Aug 15
1
Mdbox corruption
Hi,
I have a "ubuntu10.04 + ext4-filesystem + dovecot-2.0.13 +mdbox"
configuration in my server. It works fine with ~50k accounts.
Recently happened a filesystem corruption in a device of StMailLocation
and I fix with fsck.ext4.
After this crash, one account began to show access timeout and errors
like this on force-resync:
# doveadm force-resync -u account INBOX
doveadm(account):
2007 Nov 03
3
Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged
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
2019 Jul 15
2
broken mdboxes
Hello,
I was forced to do an emergency server migration with about 3000
mailboxes and I botched it somewhat. Hoping to find some help here.
My symptoms are, users showing apparently deleted mail messages, some
replicated mail, and a time period of mail that is just 'missing'.
The source server is centos 6.10 with dovecot 2.2.5, and the destination
is ubuntu 16 / dovecot 2.2.22. User
2020 Nov 10
2
Recovering expunged but not purged e-mails from mdbox with zlib compression
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
2020 Nov 10
2
Recovering expunged but not purged e-mails from mdbox with zlib compression
> On 10/11/2020 20:07 Daniel Sch?tze <dms at cwa.uk.com> wrote:
>
>
> Dear Aki
> Thank you. Unfortunately I'm struggling to get the right syntax for this as it looks like someone else was here too
> https://dovecot.org/pipermail/dovecot/2018-July/112441.html
> The location in my dovecot.conf is
>
>
2013 Mar 07
1
[dovecot-2.1.15] mdbox corruption, doveadm force-resync can't repair it (throws segfault)
Hi Timo, hi all!
Today i noticed imap throws segmentation faults and dumps cores. I
looked into logs I can see:
2013-03-07T12:12:52.257986+01:00 meteor dovecot:
imap(marcinxxx at kolekcja.mejor.pl) <7sRXtFPXYAA+eX93>: Error: Corrupted
dbox file
/dane/domeny/mejor.pl/mail/marcin//.mdbox/mailinglists/storage/m.75
(around offset=2779212): EOF reading msg header (got 0/30 bytes)
2018 Jun 22
1
lazy expunge folder delete bug
There's a bug in "folder delete" for lazy expunge, type "1 namespace", as descibed on https://wiki2.dovecot.org/Plugins/Lazyexpunge
When trying to delete a mailbox that still has messages in it, but that has no EXPUNGED/<name> counterpart, the process hangs after the imap "DELETE" command, and the following appears in the log file after a 60s timeout:
Jun