Your message dated Tue, 9 Jun 2015 19:52:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#652111: icedove: Excessive disk space usage in file in
ImapMail due to corrupt data
has caused the Debian Bug report #652111,
regarding icedove: Excessive disk space usage in file in ImapMail due to
corrupt data
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
652111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652111
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 3.1.16-1
Severity: minor
Email stored on a Debian server using dovecot (1:1.2.15-7) was accessed using
icedove over Imap4, synchronisation is set to keep a copy of all messages
locally.
On occasions unexplained file growth was seen with these lines (date varies and
is current system date):
>From - Wed Dec 14 20:33:05 2011
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
v6Yqg87rI6MylCnyPn5oyT1A6Gvdh...
.... lots of encoded data follows...
Were concatenated onto the end of the file in the
{profile}/ImapMail/mail.technocool-1.net/Personal repeatedly. This led to rapid
file growth and disk space exhaustion if Icedove was left running.
Compacting the corresponding folder caused the repeated copies of the data to
be removed.
On inspection a file simply consisting off this Base64 encrypted data without
normal mail headers nor any other content was to be found in the corresponding
"cur" directory of the maildir.
-rw------- 1 vmail vmail 1951884 Feb 13 2010
1266162801.P32330Q207.lintel.vm.bytemark.co.uk:2,S
A copy of this file has been retained, the origin of the corrupt file is
unclear.
I would have hoped that the situation would have been handled more gracefully,
I was able to identify the issue and take action only because I have access to
the maildir on the Imap server, otherwise the end user is left with a file that
grows out of control and no indication other than the repeated content as to
origin.
I've assumed since dovecot has only one copy of the file that it is probably
doing the right thing and that the issue lies with Icedove.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages icedove depends on:
ii debianutils 4.0.4
ii fontconfig 2.8.0-3
ii libasound2 1.0.24.1-4
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libdbus-1-3 1.4.16-1
ii libffi5 3.0.10-3
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.7-2
ii libgcc1 1:4.6.1-4
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.6-1
ii libgtk2.0-0 2.24.7-1
ii libhunspell-1.3-0 1.3.2-4
ii libjpeg8 8c-2
ii libnspr4-0d 4.8.9-1
ii libnss3-1d 3.12.11-3
ii libpango1.0-0 1.29.4-2
ii libpixman-1-0 0.22.2-1
ii libpng12-0 1.2.46-3
ii libsqlite3-0 3.7.7-2
ii libstartup-notification0 0.12-1
ii libstdc++6 4.6.1-4
ii libx11-6 2:1.4.4-2
ii libxrender1 1:0.9.6-2
ii libxt6 1:1.1.1-2
ii psmisc 22.13-1
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages icedove recommends:
ii myspell-en-gb [myspell-dictionary] 1:3.3.0-3
ii myspell-en-us [myspell-dictionary] 1:3.3.0-3
Versions of packages icedove suggests:
ii libdbus-glib-1-2 0.98-1
ii libgconf2-4 2.32.4-1
ii libgnomevfs2-0 1:2.24.4-1
ii libgssapi-krb5-2 1.9.1+dfsg-3
ii libnotify4 0.7.4-1
ii ttf-lyx 2.0.1-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Simon,
On Wed, Dec 14, 2011 at 09:42:18PM +0000, Simon Waters wrote:
> Package: icedove
> Version: 3.1.16-1
> Severity: minor
>
> Email stored on a Debian server using dovecot (1:1.2.15-7) was
> accessed using icedove over Imap4, synchronisation is set to keep a
> copy of all messages locally.
>
> On occasions unexplained file growth was seen with these lines (date
> varies and is current system date):
>
> >>From - Wed Dec 14 20:33:05 2011
> X-Mozilla-Status: 0001
> X-Mozilla-Status2: 00000000
> v6Yqg87rI6MylCnyPn5oyT1A6Gvdh...
> .... lots of encoded data follows...
>
> Were concatenated onto the end of the file in the
> {profile}/ImapMail/mail.technocool-1.net/Personal repeatedly. This led
> to rapid file growth and disk space exhaustion if Icedove was left
> running.
>
> Compacting the corresponding folder caused the repeated copies of the
> data to be removed.
>
> On inspection a file simply consisting off this Base64 encrypted data
> without normal mail headers nor any other content was to be found in
> the corresponding "cur" directory of the maildir.
>
> -rw------- 1 vmail vmail 1951884 Feb 13 2010
> 1266162801.P32330Q207.lintel.vm.bytemark.co.uk:2,S
>
> A copy of this file has been retained, the origin of the corrupt file
> is unclear.
>
> I would have hoped that the situation would have been handled more
> gracefully, I was able to identify the issue and take action only
> because I have access to the maildir on the Imap server, otherwise the
> end user is left with a file that grows out of control and no
> indication other than the repeated content as to origin.
>
> I've assumed since dovecot has only one copy of the file that it is
> probably doing the right thing and that the issue lies with Icedove.
this report belongs to a long outdated version of Icedove and no one
else was reporting such issues with newer versions.
I will close this report now. Please reopen if there still are issues
left with a current report of the problem.
Regards
Carsten
--- End Message ---
