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 335687 - Moving messages also deletes them
Moving messages also deletes them
Status: RESOLVED DUPLICATE of bug 329946
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-03-23 15:31 UTC by søren hauberg
Modified: 2006-03-23 16:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description søren hauberg 2006-03-23 15:31:53 UTC 
Please describe the problem:
I have message filters that moves certain incoming messages to subfolders on my
IMAP account. If a message gets moved by such a filter it will both be in the
folder I want it to AND in the Trash folder. I don't know if this is an IMAP
"feature" but it sure is annoying.

Steps to reproduce:
1. Create a filter that moves messages to a subfolder (let's call the subfolder X).
2. Wait for a message that triggers the filter.
3. See that the message is in subfolder X.
4. See that the message ALSO is in the trash folder.


Actual results:
Described above

Expected results:
The message shouldn't appear in the trash folder.

Does this happen every time?
Yes

Other information:
I'm using IMAP on Ubuntu dapper.
Comment 1 Karsten Bräckelmann 2006-03-23 16:51:19 UTC 
This indeed is the way how it has to be done in IMAP, and how Evo does a move. Basically, moving a mail is "copy and delete (the original)" for security and/or implementation/protocol reasons. Please see bug 329946 comment 1 for more details.

Thanks for taking the time to report this issue.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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