[Bug 15445] New: evolution won't clear its cache

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15445
Ubuntu | evolution

           Summary: evolution won't clear its cache
           Product: Ubuntu
           Version: unspecified
          Platform: Other
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: evolution
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: dooglus at gmail.com
         QAContact: desktop-bugs at lists.ubuntu.com


I just tried using evolution.  Usually I just use gmail on the web, but thought
it would be good to have a copy of my email locally as well.

I set up the gmail account in evolution and started POP'ing the email onto my
PC.  At first it was popping 284 messages each time I did a "send and receive"
which was OK, but after the first 4 or 5 batches, it started downloading just 3
or 5 messages each time.  This was going to take far too long, and I was still
only on June's messages.  I decided to give up, deleted all the messages from
the folders on my PC, deleted the folders I had made, emptied the trash and then
deleted the account from evolution.  Then I quit evolution.

Imagine my surprise when I found that ~/.evolution is still using over 200Mb of
disk space:

  $ du -hs ~/.evolution
  202M	/home/chris/.evolution

It turns out that all the big files are here:

  201M	/home/chris/.evolution/mail/pop/dooglus at gmail.com@pop.gmail.com/cache

Why didn't it delete that directory when I deleted the account from evolution? 
Or when I exited evolution?  I don't see any option anywhere to "empty cache".

I would just zap the whole ~/.evolution directory, but I use the task list
occasionally.  Is it safe to delete the cache directory?

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.