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 637642 - "Move to Folder..." function doesn't work properly with Gmail IMAP functionality
"Move to Folder..." function doesn't work properly with Gmail IMAP functionality
Status: RESOLVED DUPLICATE of bug 634743
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imap] evolution[google]
Depends on:
Blocks:
 
 
Reported: 2010-12-20 08:54 UTC by Milan Crha
Modified: 2011-02-11 10:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2010-12-20 08:54:04 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=664076

Description of problem:

I have Gmail setup for IMAP access, and have configured Evolution to download
my mail from Gmail's IMAP server (imap.googlemail.com).  When in evolution and
viewing my Gmail inbox, if I right-click an email message, and select "Move to
Folder...", the email appears to be moved to the folder specified.  However,
changing to the specified folder briefly shows the email and then it
disappears.

Going to the Gmail "trash" folder, shows the moved email is in the trash.

Accessing Gmail through a Firefox browser, and going to the Gmail "trash"
folder shows the moved email in the trash with a label  that matches the folder
specified in evolution.

Therefore, it appears Evolution is correctly labelling the email and removing
the email from the Gmail inbox, when the "Move to Folder..." is performed. 
However, Evolution is additionally moving the email to the trash folder, which
is incorrect behaviour.

Version-Release number of selected component (if applicable):


How reproducible:
Every time.

Steps to Reproduce:
     Gmail Setup (for IMAP access):
1. Login to Gmail
2. Click "Settings" (Upper right)
3. Click "Forwarding and POP/IMAP"
4. Under "IMAP Access:", select "Enable IMAP"
5. Click "Save Changes"
6. Create a label called "multi/level/testFolder" (labels appear as folders in
Evolution.)

     Evolution Setup:
1. Setup Evolution to receive email from "imap.googlemail.com"
2. Enable email receiving option "Automatically synchronize remote mail
locally"
3. For folder defaults set:
     a) "Drafts Folder" to "[Gmail]/Drafts"
     b) "Sent Messages Folder" to "[Gmail]/Sent Mail"
     c) "Trash Folder" to "[Gmail]/Trash"
     d) "Junk Folder" to "[Gmail]/Spam"

    Move email:
1. Start evolution, and go to your Gmail account's Inbox (authenticate as
needed)
2. Right click on one of the emails, and from the pop-up menu select "Move to
Folder..."
3. In the "Move to Folder" window, select the Gmail Account
"multi/level/testFolder", and click "Move"
4. View the contents of the folders: "multi/level/testFolder" and
"[Gmail]/trash"
5. To see labels on emails in the trash folder:
      a) Start firefox (or another browser)
      b) Login to the Gmail Account
      c) View the contents of the "trash folder" (labels appear before the
subject, typically in green.)


Actual results:
The moved email is:
 1. Removed from Gmail's inbox (archived)
 2. Given the "[Gmail]/trash" label (i.e. moved to the "trash" folder)
 3. Given the "multi/level/testFolder" label 
    a) However, due to the email also having a "[Gmail]/trash" label it doesn't
appear in evolution's "multi/level/testFolder" folder.  This is probably the
correct behavior because if Gmail's trash is emptied, the email will be removed
from all folders.

Expected results:
The moved email is only:
 1. Removed from Gmail's inbox (archived)
 2. Given the "multi/level/testFolder" label
Comment 1 Akhil Laddha 2011-02-08 07:54:20 UTC
mostly fixed in bug 637642
Comment 2 Milan Crha 2011-02-11 10:25:44 UTC
Thanks for the bug report. 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 bug 634743 ***