Bug 2343 - "execute immediately" seemingly ignored
Summary: "execute immediately" seemingly ignored
Status: RESOLVED DUPLICATE of bug 2325
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Message List (show other bugs)
Version: 3.7.8
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2011-01-10 20:15 UTC by Joseph Dunn
Modified: 2011-01-19 14:55 UTC (History)
1 user (show)

See Also:


Attachments

Description Joseph Dunn 2011-01-10 20:15:26 UTC
Somehow I've gotten my claws-mail install into a strange state where the "execute immediately" setting not longer seems to apply to moves.  The move completes in that the email message dragged from my local mail folder into an IMAP account appears in the new account, but it is not removed from the summary view of my inbox.

The new copy of the "moved" message is just fine.  Text on the line in the summary view is shown in blue and a small blue-box arrow is shown in the check-mark-topped column.  Apparently claws-mail thinks the message is moved and not executed.  If I click on the blue line the message view shows the default "This message can't be displayed" error.  If I restart the application then I get the same behavior, but the line is no longer flagged in blue.  It seems like the cache of message headers is out of sync.  If I rebuild the folder tree for the local account the moved message is then removed from the summary view.  Any idea what I did or how to fix it once and for all?
Comment 1 Joseph Dunn 2011-01-10 20:19:53 UTC
Moving files between folders on the local machine (i.e. not moving them to an IMAP folder) seems to work fine.
Comment 2 Colin Leroy 2011-01-17 10:36:26 UTC
That's probably a known bug that's fixed in CVS. If you can test CVS...

*** This bug has been marked as a duplicate of bug 2325 ***
Comment 3 Joseph Dunn 2011-01-19 14:55:20 UTC
Confirmed.  This is fixed in CVS.  Thanks, and I'll check there next time before filing.

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