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 616823 - Evolution allows moving IMAP Inbox to other folders
Evolution allows moving IMAP Inbox to other folders
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
2.30.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 430881 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-04-26 06:58 UTC by Ruchir Brahmbhatt
Modified: 2011-08-23 15:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
evo patch (1.91 KB, patch)
2010-05-10 17:03 UTC, Milan Crha 		committed Details | Review

Description Ruchir Brahmbhatt 2010-04-26 06:58:44 UTC 
OS: opensuse 11.2
Evolution: 2.30.0.1
Account: Gmail IMAP

Steps:
1. Drag inbox and drop to some folder.(This happened mistakenly though because of auto click and drag by touchpad somehow)

Results:
It moves the inbox to other folder. Inbox icon changes to normal  folder icon folder. There is no inbox in account now. Gmail shows blank inbox. There is new folder inbox created in that folder where inbox was moved and all inbox mails show up there in gmail and evo. After reboot, evo shows inbox blank now. New emails are delivered to this inbox folder. I had to move mails from that old inbox folder to new inbox and delete old inbox folder. 

Expected results: I think it shouldn't allow moving inbox folder.
Comment 1 Milan Crha 2010-05-10 17:03:48 UTC 
Created attachment 160742 [details] [review]
evo patch

for evolution;

Allow only copy of the Inbox and other system folders.
Comment 2 Milan Crha 2010-05-10 17:07:10 UTC 
Created commit 3c40a61 in evo master (2.31.2+)
Created commit ae66b7f in evo gnome-2-30 (2.30.2+)
Comment 3 Milan Crha 2011-08-23 15:53:07 UTC 
*** Bug 430881 has been marked as a duplicate of this bug. ***