erver in replica (version 2.3.4.1),
I use LDAP/AD for /userdb, /replica is working, but sometimes I
get these errors into log:
Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251>:
Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged
message reappeared, giving a new UID (old uid=
(xxx)<28251>:
Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged
message reappeared, giving a new UID (old uid=233140,
file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,)
The user delete the message and then the message reappears into
mail client after one second.
Does anyb
dovecot: imap(xxx)<28251>:
Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged
message reappeared, giving a new UID (old uid=233140,
file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,)
The user delete the message and then the message reappears into
mail client after one seco
:
Hi,
I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I
use LDAP/AD for /userdb, /replica is working, but sometimes I get
these errors into log:
Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251>:
Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged
message rea
arning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged
message reappeared, giving a new UID (old uid=233140,
file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,)
The user delete the message and then the message reappears into mail
client after one second.
Does anybody knows how can I
Hi,
I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I use
LDAP/AD for /userdb, /replica is working, but sometimes I get these
errors into log:
Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251>:
Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged message
reap
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-al...@example.com which delivers emails to user1@ and user2@
If
* I send an email to
On Wed, Mar 1, 2017 at 3:40 PM, Γιώργος Δημακόπουλος
wrote:
> 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
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
Please help.
How to stop email replication is on going.
dsync-server : Warning Expunged message reappeared, giving a new UID
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?
On Sun, 2013-09-22 at 00:13 +0300, Timo Sirainen wrote:
> > One side has uidnext=23 and the other side has uidnext=24. You're
> deleting the last message with uid=22, so the uidnext=23 is correct.
> The other side however thinks that the same mail's uid is 23. There
> must be something wrong with
On 22.9.2013, at 0.02, Timo Sirainen wrote:
> The A and B node logs are exactly the same. I think you sent the same ones
> for both? Anyway, one of the sides is enough. The interesting parts are:
>
> 1375808883.299424 O: NINBOX y 0314c806e3fa0052d26a736ac1b0
> 1375795939
On 8.8.2013, at 11.21, Simon Fraser wrote:
> I ran two tests: one using 'doveadm expunge' and one deleting the
> message using mutt. Since the hosts mentioned so far have a copy of my
> full mailbox on, I re-ran the tests (with the same results) on a test
> server with a fresh mailbox on, so ther
Time marches on, and I need to continue the service migration. I'd still
like to use Dovecot (we're migrating away from Cyrus). I'm assuming the
only other alternative without existing shared storage is to use DRBD
and a cluster file system to provide the replication, and to ensure
Director is en
On Mon, 2013-08-19 at 12:08 +0100, Simon Fraser wrote:
> Are there any more tests I can run for this?
I've tried an ssh-based replication configuration, and still experience
the same symptoms. Going through a director proxy also doesn't help (as
expected, that one, since I was already only connec
Are there any more tests I can run for this?
Thanks,
Simon.
On Thu, 2013-08-08 at 09:21 +0100, Simon Fraser wrote:
> On Tue, 2013-08-06 at 19:15 +0300, Timo Sirainen wrote:
>
> > > Presumably it's thinking the "-r /tmp/dsync-rawlog" is a mail location?
> > > I've tried changing its location in
On Tue, 2013-08-06 at 19:15 +0300, Timo Sirainen wrote:
> > Presumably it's thinking the "-r /tmp/dsync-rawlog" is a mail location?
> > I've tried changing its location in the appends, but it doesn't make a
> > difference.
>
> Oops, I messed up the parameter order. It was supposed to have -s sta
On 6.8.2013, at 18.58, Simon Fraser wrote:
> On Tue, 2013-08-06 at 16:45 +0300, Timo Sirainen wrote:
>
>>>
>>> Weird, I was sure that would have worked. Well, maybe rawlogs would
>> show something interesting. I should probably add a proper option for
>> them, but attached a patch to enable for
On Tue, 2013-08-06 at 16:45 +0300, Timo Sirainen wrote:
> >
> > Weird, I was sure that would have worked. Well, maybe rawlogs would
> show something interesting. I should probably add a proper option for
> them, but attached a patch to enable for now. Be sure to
> mkdir /tmp/dsync-rawlogs with en
On 6.8.2013, at 16.42, Timo Sirainen wrote:
> On 6.8.2013, at 15.59, Simon Fraser wrote:
>
>>> Try disabling replicator plugin from only one side, so there's not
>>> possibility of two dsyncs running at the same time. That should be
>>> prevented already by locking though.
>>
>> I disabled t
On 6.8.2013, at 15.59, Simon Fraser wrote:
>> Try disabling replicator plugin from only one side, so there's not
>> possibility of two dsyncs running at the same time. That should be prevented
>> already by locking though.
>
> I disabled the replication on node b, restarted both, and connected
On Tue, 2013-08-06 at 14:30 +0300, Timo Sirainen wrote:
> Here's another idea:
>
Thank you for still looking into this
> Try disabling replicator plugin from only one side, so there's not
> possibility of two dsyncs running at the same time. That should be prevented
> already by locking thoug
On 6.8.2013, at 14.30, Timo Sirainen wrote:
> Here's another idea:
>
> Try disabling replicator plugin from only one side, so there's not
> possibility of two dsyncs running at the same time. That should be prevented
> already by locking though.
>
> The servers have different hostnames, right
On 1.8.2013, at 17.02, Simon Fraser wrote:
>>> Connect with a mail client, and delete the message - without delayed
>>> expunge. So, for example, mutt (press 'd' then '$' to sync the mailbox),
>>> or Evolution set to immediately delete.
>>
>> Can you reproduce this by disabling automatic replica
Hello,
For what it's worth, still experiencing these symptoms with 2.2.5.
Thanks,
Simon.
On Thu, 2013-08-01 at 15:02 +0100, Simon Fraser wrote:
> On Thu, 2013-08-01 at 15:09 +0300, Timo Sirainen wrote:
> > On Fri, 2013-07-26 at 11:28 +0100, Simon Fraser wrote:
> >
> > > I am running dovecot 2.
On Thu, 2013-08-01 at 15:09 +0300, Timo Sirainen wrote:
> On Fri, 2013-07-26 at 11:28 +0100, Simon Fraser wrote:
>
> > I am running dovecot 2.2.2 with tcp based replication, and experiencing
> > some duplicated emails. `doveconf -n` output is below.
>
> Are both of the servers using the same mail
il3a,S=1289,W=1321 (uid
> 733481 -> 733482) - retrying by re-reading from beginning
> Jul 26 10:40:55 intmail3a dovecot: imap(srf): Warning:
> Maildir /mail/spool/s/srf/mail/INBOX: Expunged message reappeared,
> giving a new UID (old uid=733481,
> file=1374831638.M830754P11591.intma
Hi, is there anything I can do to help debug this - any tools I should
run to discover where the cause might be?
Simon.
On Mon, 2013-07-29 at 10:05 +0100, Simon Fraser wrote:
> On Fri, 2013-07-26 at 20:26 +0200, Daniel Parthey wrote:
> > Hi Simon,
> >
> > Version 2.2.2 is not current any more.
On Fri, 2013-07-26 at 20:26 +0200, Daniel Parthey wrote:
> Hi Simon,
>
> Version 2.2.2 is not current any more. I would try to update to the
> latest stable version 2.2.4 first, since some dsync bugs have been
> fixed between 2.2.2 and 2.2.4:
I've now upgraded to 2.2.4 (and pigeonhole 0.4.1 from
Hi Simon,
Version 2.2.2 is not current any more. I would try to update to the latest
stable version 2.2.4 first, since some dsync bugs have been fixed between 2.2.2
and 2.2.4:
http://www.dovecot.org/doc/NEWS-2.2
Regards
Daniel
On Fri, 2013-07-26 at 17:47 +0200, Reindl Harald wrote:
>
> Am 26.07.2013 17:41, schrieb Simon Fraser:
> > I've just converted the mailboxes to mdbox, so mail_location now looks
> > like this:
> >
> > mail_location = mdbox:~/mail
> >
> > The log entry about messages reappearing no longer happens
Am 26.07.2013 17:41, schrieb Simon Fraser:
> I've just converted the mailboxes to mdbox, so mail_location now looks
> like this:
>
> mail_location = mdbox:~/mail
>
> The log entry about messages reappearing no longer happens, but the
> symptoms are the same - if I delete a message, it instantly
82) - retrying by re-reading from beginning
> Jul 26 10:40:55 intmail3a dovecot: imap(srf): Warning:
> Maildir /mail/spool/s/srf/mail/INBOX: Expunged message reappeared,
> giving a new UID (old uid=733481,
> file=1374831638.M830754P11591.intmail3a,S=1289,W=1321)
>
> The email reapp
/spool/s/srf/mail/INBOX: Expunged message reappeared,
giving a new UID (old uid=733481,
file=1374831638.M830754P11591.intmail3a,S=1289,W=1321)
The email reappears in the mailbox, although this time it is in
INBOX/new on one node and INBOX/cur on the other. As best I can tell
it's always in '
On Wed, 2011-03-30 at 10:35 +0200, Stanisław Findeisen wrote:
> 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=, method=...
>
On 2011-03-30 4:35 AM, Stanisław Findeisen wrote:
> $ dovecot --version
> 1.0.15
Very old... upgrading will very likely magically solve many problems
--
Best regards,
Charles
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=, method=...
Mar 29 10:57:03 k8ux dovecot: POP3(stf): mbox sync: UID inserted in the
middle of mail
38 matches
Mail list logo
