Bug 146975 - Evolution IMAP - cant transfer messages between accounts
Summary: Evolution IMAP - cant transfer messages between accounts
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-03 07:25 UTC by Carl Gherardi
Modified: 2007-11-30 22:10 UTC (History)
0 users

Clone Of:
Last Closed: 2005-03-04 22:49:19 UTC

Attachments (Terms of Use)

Description Carl Gherardi 2005-02-03 07:25:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041228 Firefox/1.0 Fedora/1.0-8

Description of problem:
When dragging a message from my personal mailbox (on exchange 2003
IMAP server) to my helpdesk mail account (on same server), I get the
following error dialog.
Error while Moving messages into folder INBOX/Done 2005 02.

Cannot append message to folder `INBOX/Done 2005 02': Bad command.

Worked fine in 2.0.x series.

Version-Release number of selected component (if applicable):
evolution-2.1.4-1 evolution-data-server-

How reproducible:

Steps to Reproduce:
1. Set up two IMAP accounts
2. Attempt to drag a message from a folder in one account to another
3. Get error message

Expected Results:  Mail to be marked as deleted, and a copy to appear
in the new folder (I manually expunge IMAP folders)

Additional info:

Comment 1 Carl Gherardi 2005-02-03 07:27:51 UTC
Forgot to mention, the drag and drop work fine from within the same


Comment 2 Dave Malcolm 2005-03-04 22:49:19 UTC
Thanks for the bug report; sorry it's taken so long to respond.

Looks like this one should really be refiled upstream here:

Please make sure the bug isn't already in the upstream bug tracker
before filing it.

Can you try with the most up-to-date packages (evolution-2.1.6 and

Please try setting CAMEL_VERBOSE_DEBUG=1 when launching Evolution;
this should give more debug info about the IMAP connection.


Comment 3 Carl Gherardi 2005-03-08 04:11:21 UTC
It was fixed with 2.1.5-1 and e-d-s-1.1.5, not to long after I filed
the report.

I'll keep in touch with updates the moment someone releases an
unborked version of yum.

Note You need to log in before you can comment on or make changes to this bug.