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

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: It's really 3873 bvtes long, uncompressed ].
> ..
> > Package: dovecot-imapd
> > Version: 1:2.2.13-11
> > Severity: serious
> 
> I can't reproduce with latest Dovecot hg.
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.
> But just in case it's still not fixed, there are two important things:
> 
> 1) Send your doveconf -n output, since there are some settings that can
affect this
Nothing special. The default configuration from the Debian package.
The bug may be reproduced without touching any file in /etc at all.
This is the result of "doveconf -n":

# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.0 
mail_location = mbox:~/mail:INBOX=/var/mail/%u
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
    special_use = \Drafts
  }
  mailbox Junk {
    special_use = \Junk
  }
  mailbox Sent {
    special_use = \Sent
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }
  mailbox Trash {
    special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
protocols = " imap"
ssl = no
userdb {
  driver = passwd
}

> 2) rm -rf ~/mail/.imap/inbox-b before testing to make sure indexes
don't cause this problem.
Yes, I did that. In fact, I checked that this happens on a freshly installed
virtual machine,
i.e. no ~/mail/.imap at all.

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 for MINOR release.

Major releases/updates, sure, I understand completely, but minor
releases? It is far too much pain for far too little gain imnsho...

Am 20.02.2015 um 15:03 schrieb Charles Marcus:
> 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 for MINOR release.
>
> Major releases/updates, sure, I understand completely, but minor
> releases? It is far too much pain for far too little gain imnsho...
that's a political decision to not break workarounds because someone 
removes a bug you worked around or even not break stupid software rely 
on the bahvior of bugs :-)

and to make web-developers lifes harder because params in PHP which help 
to prepare upgrade to >= 5.4 and are present for many years in 5.3.x are 
not available on Debian systems

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20150220/d53aab74/attachment.sig>

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 latest released version (2.2.16).

Would anyone here please tell which commit exactly fixed this issue?

If it's not fixed yet, I would love to provide a patch, but I'm not a
programmer myself.

However, I provided a very precise and detailed explanation about how
to reproduce this bug, which you will still find in the Debian BTS:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776094

Really, it should not be so much difficult to reproduce it. Try on a
Debian 8 system. I'm sure that if you follow the steps exactly as I
described, you will find the problem the same way as I did.

Thanks.

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, having this fixed in hg does not help very
> much if the bug is still present in the latest released version (2.2.16).
> 
> Would anyone here please tell which commit exactly fixed this issue?
> 
> If it's not fixed yet, I would love to provide a patch, but I'm not
a
> programmer myself.
> 
> However, I provided a very precise and detailed explanation about how
> to reproduce this bug, which you will still find in the Debian BTS:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776094
> 
> Really, it should not be so much difficult to reproduce it. Try on a
> Debian 8 system. I'm sure that if you follow the steps exactly as I
> described, you will find the problem the same way as I did.
> 
> Thanks.
> 
Boh fetchmail .... did you verified with getmail ?

http://pyropus.ca/software/getmail/

dig you tried fetchmail with

bad-header accept ?

what are dovecot verbose logs tell


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstra?e 15, 81669 M?nchen

Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein