Hello Apollon, On Thu, 6 Apr 2017 12:17:10 +0300 Apollon Oikonomopoulos wrote:
> Control: tags -1 moreinfo > > Hi Christian, > > Thanks for the report. > > On 15:48 Thu 06 Apr , Christian Balzer wrote: > > I've been seeing a few of these since starting this cluster (see > > previous > > mail), they all follow the same pattern, a user who accesses their mailbox > > with both POP3 and IMAP deletes mails with POP3 and the IMAP > > (imap-hibernate really) is getting confused and upset about this: > > > > --- > > Apr 6 09:55:49 mbx11 dovecot: imap-login: Login: user=<redac...@gol.com>, > > method=PLAIN, rip=xxx.xxx.x.46, lip=xxx.xxx.x.113, mpid=951561, secured, > > session=<2jBV+HRM1Pbc9w8u> > > Apr 6 10:01:06 mbx11 dovecot: pop3-login: Login: user=<redac...@gol.com>, > > method=PLAIN, rip=xxx.xxx.x.46, lip=xxx.xxx.x.41, mpid=35447, secured, > > session=<uZw7C3VM9vfc9w8u> > > Apr 6 10:01:07 mbx11 dovecot: pop3(redac...@gol.com): Disconnected: Logged > > out top=0/0, retr=0/0, del=1/1, size=20674 session=<uZw7C3VM9vfc9w8u> > > Apr 6 10:01:07 mbx11 dovecot: imap(redac...@gol.com): Error: imap-master: > > Failed to import client state: Message count mismatch after handling > > expunges (0 != 1) > > Apr 6 10:01:07 mbx11 dovecot: imap(redac...@gol.com): Client state > > initialization failed in=0 out=0 head=<0> del=<0> exp=<0> trash=<0> > > session=<2jBV+HRM1Pbc9w8u> > > Apr 6 10:01:15 mbx11 dovecot: imap-login: Login: user=<redac...@gol.com>, > > method=PLAIN, rip=xxx.xxx.x.46, lip=xxx.xxx.x.113, mpid=993303, secured, > > session=<6QC6C3VMF/jc9w8u> > > Apr 6 10:07:42 mbx11 dovecot: imap-hibernate(redac...@gol.com): Connection > > closed in=85 out=1066 head=<0> del=<0> exp=<0> trash=<0> > > session=<6QC6C3VMF/jc9w8u> > > --- > > > > According to the dovecot ML, this is fixed in 2.2.28, so getting this into > > Debian and backports would be much appreciated. > > Unfortunately we are in the middle of the freeze for next stable, and > updating to 2.2.28 itself is not an option at this time I'm afraid. If > we pinpoint the fix however, we can always backport it to 2.2.27 and > have it released with Stretch. > Nods, I think I saw that freeze bit when glancing over the new package tracker. Would love to have that fixed, even though it seems to be (thankfully) mostly transparent to the actual (and few) users that are affected by it. > > > > See also: > > https://www.dovecot.org/pipermail/dovecot/2017-April/107668.html > > According to the message by Aki in the dovecot ML, this is fixed in > 1fd44e0634. However, 1fd44e0634 is already part of 2.2.26 (and 2.2.27 > of course), which complicates things a bit more: > > $ git describe --contains 1fd44e0634ac312d0960f39f9518b71e08248b65 > 2.2.26~318 > > So either the fix is incomplete, or you have some old processes lying > around. I can't think of anything else :) > I vote for the first option, since this is a fresh install that never saw anything but 2.2.27 from backports. Also so the .26, .27 bits in the git excerpt but didn't check it in detail, though why did Aki suggest .28 when I stated that it's already .27 here? Will point the folks on the dovecot ML to this bug report, maybe Timo can make sense of it. Thanks, Christian > Regards, > Apollon > -- Christian Balzer Network/Systems Engineer ch...@gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/
