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 476282 - fails to "expunge" unwanted messages
fails to "expunge" unwanted messages
Status: RESOLVED DUPLICATE of bug 445439
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[pop]
Depends on:
Blocks:
 
 
Reported: 2007-09-12 17:37 UTC by sheywood
Modified: 2011-10-14 07:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description sheywood 2007-09-12 17:37:25 UTC 
The Evolution Mail program fails to truly "expunge" unwanted messages.
Instead of truly "expunging" them it just moves them to an obscure 
subdirectory.  If I want to truly expunge them I have to do that manually.
This is a hassle.  Problem ought to be fixed.


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1
Comment 1 André Klapper 2007-09-13 09:18:39 UTC 
what is "truly"? what is the obscure subdirectory? is this about POP, or IMAP? what is "manually"? please be much more explicit if the problem "ought to be fixed". thanks.
Comment 2 sheywood 2007-09-13 16:15:03 UTC 
This is about POP, not IMAP.  I don't know what it does in IMAP.

It doesn't "truly" expunge them, as in "rm".  What it does is that it
just moves them, as in "mv".  It moves them to an obscure subdirectory,
which in my case is 

~/.evolution/mail/pop/sheywood@pop.shentel.net/cache/08

or to various other subdirectories under
~/.evolution/mail/pop/sheywood@pop.shentel.net/cache/

By removing them "manually" I mean doing that by getting into the
command line and to cd to the obscure directory(s) where they are 
located and then and running the "rm" command.
Comment 3 Akhil Laddha 2011-10-14 07:21:29 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 445439 ***