After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 527729 - Evolution re-downloads all messages when disk is full
Evolution re-downloads all messages when disk is full
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 544138 566378 (view as bug list)
Depends on:
Blocks: 529842 670071
 
 
Reported: 2008-04-12 16:10 UTC by Anthony de Almeida Lopes
Modified: 2021-05-19 11:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Anthony de Almeida Lopes 2008-04-12 16:10:39 UTC
Please describe the problem:
When the disk that evolution uses to store it's data on becomes full and I attempt to get new mail, instead of failing or reporting a problem it proceedes to attempt to download all messages.
The messages are still considered "not downloaded" even after the disk space issue is fixed.
I am using a POP3 for two different accounts and it happens for both of them.

Steps to reproduce:
1. Set up a POP3 account to not delete messages on server
2. Fill up disk
3. Press Send/Receive


Actual results:
It re-downloads all messages as if they are new.

Expected results:
Nothing or an error message of some sort

Does this happen every time?
Yes

Other information:
Comment 1 Sylwester Prozowski 2008-04-25 07:37:40 UTC
it looks like old thing for I have it in 2.12.1 as well.
Comment 2 Jeffrey Stedfast 2008-04-25 14:38:21 UTC
I've seen this myself... usually after beagled goes nuts and fills my /home partition with error log spew.


my /guess/ as to what is happening here is that evolution fails to write ~/.evolution/mail/pop/<account>/uid-cache and so it somehow gets clobbered.


1. need to prevent it from ever getting clobbered... if it fails to write out a new version of this file, at worst it should leave the old one in place.

2. if it can't write out the new cache, try clearing the ~/.evolution/mail/pop/<account>/cache/* directories and then retrying?
Comment 3 Matthijs 2008-07-01 07:50:16 UTC
I can confirm this bug on Evolution 2.22.2 (Ubuntu Hardy). Very annoying, also because Gnome doesn't give me any notice that my disk is running out of space. By the time I notice this myself, it's too late and all I can do is wait until Evolution has re-downloaded several thousands of emails, after which I can spend a couple of hours removing those again.
Comment 4 Jeremy G 2008-09-15 16:34:56 UTC
I confirm the bug on Evolution 2.22.3.1 + Hardy... And I don't know if it's secure to clean the cache (uid-cache), to let Evolution create a new one...
Comment 5 Oleksandr 2008-10-16 11:53:53 UTC
I confirm this bug in  Evolution 2.22.3.1 Fedora Core 9.
Comment 6 André Klapper 2009-01-07 21:42:20 UTC
*** Bug 566378 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2009-01-07 21:44:22 UTC
Note that bug 382403 and bug 554552 are similar.
Comment 8 Akhil Laddha 2009-08-26 12:16:24 UTC
*** Bug 544138 has been marked as a duplicate of this bug. ***
Comment 9 David Booth 2009-11-25 02:18:27 UTC
I wrote a perl script called cleanemail.perl for deleting duplicate 
or previously moved or deleted messages from your Evolution or Eudora
email files.  It is especially useful for cases like this in which your 
email client loses track of which messages it has downloaded from your 
mail server, and consequently downloads all messages again, thus creating
thousands of duplicate messages in your Inbox.  

The source code is available
at http://dbooth.org/2009/cleanemail/
and the opening comment explains its usage.
Comment 10 André Klapper 2021-05-19 11:55:59 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.