Bug 475576 - Can not set up a "move to folder ..." filter
Summary: Can not set up a "move to folder ..." filter
Keywords:
Status: CLOSED DUPLICATE of bug 474695
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-09 17:40 UTC by Miloslav Trmač
Modified: 2008-12-09 18:00 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-12-09 18:00:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miloslav Trmač 2008-12-09 17:40:07 UTC
Version-Release number of selected component (if applicable):
evolution-2.24.2-1.fc10.x86_64
evolution-data-server-2.24.2-1.fc10.x86_64


Steps to Reproduce:
1. Receive a mail from a mailing list
2. Create a folder for the list
3. Right-click the mail, create a filter from mailing list.
4. In the "move to folder" action, chose your desired folder
5. Close all the dialogs, and press Ctrl-Y to test the filter

  
Actual results:
An error dialog / message in the status bar: (translated from Czech, roughly):
"Error filtering selected messages" Can not get folder ...: folder does not exist

Expected results:
Message moved to the target folder

Additional info:
The folder exists, moving mails to it manually works
Filters imported from older Evolution version work fine.

Looking at filters.xml, the new filter uses
          <value name="folder" type="folder">
            <folder uri="email://local@local/Lists/libvir"/>
whereas the older filters use:
          <value name="folder" type="folder">
            <folder uri="email://1219264640.7008.0@amilo/Lists/rh_friday"/>

[amilo is an old host name from wchich the older Evolution configuration was imported; this computer has a different host name.]

Comment 1 Milan Crha 2008-12-09 18:00:45 UTC

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


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