similar to: Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)

On 14 Feb 2015, at 16:23, Santiago Vila <sanvila at unex.es> wrote: > I wrote about this three weeks ago but got no answer. I'm going to > officially "forward" the Debian bug this time, with all the details. > > The test case is just 840 bytes long. Please give it a try. .. > Package: dovecot-imapd > Version: 1:2.2.13-11 > Severity: serious I can't

On Sun, 15 Feb 2015, Timo Sirainen wrote: > On 14 Feb 2015, at 16:23, Santiago Vila <sanvila at unex.es> wrote: > > > I wrote about this three weeks ago but got no answer. I'm going to > > officially "forward" the Debian bug this time, with all the details. > > > > The test case is just 840 bytes long. Please give it a try. [ Small correction:

Am 04.05.2015 um 21:04 schrieb Santiago Vila: > Greetings. > > Thanks to Jelmer Vernooij, who has just uploaded version 2.2.16 for > Debian unstable, I can confirm that this bug may still be reproduced > in version 2.2.16, so it has *not* been fixed yet. > > Several months ago I was told "I can't reproduce it in dovecot hg", or > something like that. Well,

Am 05.05.2015 um 16:26 schrieb Santiago Vila: > I have just verified with IMAP commands. This is the procedure: > > telnet localhost 143 > > and then type this: > > A0001 CAPABILITY > A0002 LOGIN "bluser" "bluser" > A0003 SELECT "inbox-b" > A0004 EXPUNGE > A0005 FETCH 1:12 RFC822.SIZE > A0006 FETCH 1 RFC822.HEADER > A0007

On 2/19/2015 4:34 PM, Santiago Vila <sanvila at unex.es> wrote: > In such case we would love to know what is the commit that fixed this, > so that we can apply it to the 2.2.13 version in Debian. We have > frozen the distribution as we are about to release jessie as Debian 8, > so no new upstream releases are allowed anymore. I have NEVER understood the rationale for doing this

On 05/06/2015 09:57 AM, Teemu Huovila wrote: > On 05/05/2015 05:26 PM, Santiago Vila wrote: >> I have just verified with IMAP commands. This is the procedure: >> >> telnet localhost 143 >> >> and then type this: >> >> A0001 CAPABILITY >> A0002 LOGIN "bluser" "bluser" >> A0003 SELECT "inbox-b" >> A0004

On 05/05/2015 05:26 PM, Santiago Vila wrote: > I have just verified with IMAP commands. This is the procedure: > > telnet localhost 143 > > and then type this: > > A0001 CAPABILITY > A0002 LOGIN "bluser" "bluser" > A0003 SELECT "inbox-b" > A0004 EXPUNGE > A0005 FETCH 1:12 RFC822.SIZE > A0006 FETCH 1 RFC822.HEADER > A0007 FETCH

Am 04.05.2015 um 22:13 schrieb Santiago Vila: > On Mon, May 04, 2015 at 09:23:57PM +0200, Robert Schetterer wrote: >> Boh fetchmail .... did you verified with getmail ? > > No, I didn't. The client should be irrelevant. Nobody should be able > to corrupt a remote mailbox only by issuing imap commands. > > BTW: Does getmail have an option doing the same as fetchmail

I have just verified with IMAP commands. This is the procedure: telnet localhost 143 and then type this: A0001 CAPABILITY A0002 LOGIN "bluser" "bluser" A0003 SELECT "inbox-b" A0004 EXPUNGE A0005 FETCH 1:12 RFC822.SIZE A0006 FETCH 1 RFC822.HEADER A0007 FETCH 1 BODY.PEEK[TEXT] A0008 STORE 1 +FLAGS (\Seen \Deleted) A0009 EXPUNGE A0010 FETCH 1 RFC822.HEADER A0011 FETCH

Am 07.05.2015 um 01:45 schrieb Santiago Vila: > On Thu, May 07, 2015 at 12:02:12AM +0300, Timo Sirainen wrote: >> Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/94bd895721d8 > > Unfortunately, I applied single changeset 94bd895721d8 over Debian > version 2.2.16-1 to create an updated Debian package and I can still > reproduce the problem when using the updated package.

Am 05.05.2015 um 19:22 schrieb Santiago Vila: > On Tue, May 05, 2015 at 05:15:16PM +0200, Robert Schetterer wrote: >> is this related to mbox only ? > > I don't know. The bug happens as I explained, and current documentation > says mbox is still supported (I really hope documentation is correct here). yeah but it may be a mbox only bug > >> i have no mbox install

Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/94bd895721d8

On Mon, May 04, 2015 at 09:23:57PM +0200, Robert Schetterer wrote: > Boh fetchmail .... did you verified with getmail ? No, I didn't. The client should be irrelevant. Nobody should be able to corrupt a remote mailbox only by issuing imap commands. BTW: Does getmail have an option doing the same as fetchmail --folder option at all? > dig you tried fetchmail with > > bad-header

Greetings. Thanks to Jelmer Vernooij, who has just uploaded version 2.2.16 for Debian unstable, I can confirm that this bug may still be reproduced in version 2.2.16, so it has *not* been fixed yet. Several months ago I was told "I can't reproduce it in dovecot hg", or something like that. Well, having this fixed in hg does not help very much if the bug is still present in the

On Tue, May 05, 2015 at 05:15:16PM +0200, Robert Schetterer wrote: > is this related to mbox only ? I don't know. The bug happens as I explained, and current documentation says mbox is still supported (I really hope documentation is correct here). > i have no mbox install online to test A local virtual machine is more than enough to reproduce this. It does not need to be online.

For reference, this is the "dovecot -n" output matching the previous debug output: # 2.2.16: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian stretch/sid mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = mail_log notify namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk {

On Thu, May 07, 2015 at 12:02:12AM +0300, Timo Sirainen wrote: > Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/94bd895721d8 Unfortunately, I applied single changeset 94bd895721d8 over Debian version 2.2.16-1 to create an updated Debian package and I can still reproduce the problem when using the updated package. This is a little bit surprising considering that the patch applies cleanly

Debug output: May 6 11:23:42 qemu-sid dovecot: master: Dovecot v2.2.16 starting up for imap (core dumps disabled) May 6 11:24:06 qemu-sid dovecot: imap-login: Login: user=<bluser>, method=PLAIN, rip=192.168.122.8, lip=192.168.122.8, mpid=441, secured, session=<HtpSW2YVaQDAqHoI> May 6 11:24:06 qemu-sid dovecot: imap(bluser): Debug: Loading modules from directory:

Package: logcheck Version: 1.2.20a Severity: serious Tags: patch On a system where sh points to dash and LANG=es_ES, I get this: # apt-get -y --reinstall install logcheck Leyendo lista de paquetes... 0% Leyendo lista de paquetes... 0% Leyendo lista de paquetes... 23% Leyendo lista de paquetes... Hecho Creando ?rbol de dependencias... 0% Creando ?rbol de dependencias... 0% Creando ?rbol de

On 13 May 2015, at 01:15, Santiago Vila <sanvila at unex.es> wrote: > > On Wed, May 13, 2015 at 12:25:44AM +0300, Timo Sirainen wrote: >> - mbox: Fixed crash/corruption in some situations when the first mail >> was expunged. > > Once again: This is *not* fixed! One bug was fixed, but looks like there was another one. I tried after the fix that your test case