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 585583 - Add Filter creates incorrect folder uri
Add Filter creates incorrect folder uri
Status: RESOLVED DUPLICATE of bug 552583
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[filters]
Depends on:
Blocks:
 
 
Reported: 2009-06-12 15:43 UTC by Steve Rainwater
Modified: 2009-11-24 19:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Steve Rainwater 2009-06-12 15:43:09 UTC
Please describe the problem:
I created a new filter for a mailing list. Instead of moving new emails to the correct folder however, it generates the error message: 

 Error while Filtering Selected Messages.
 Cannot get folder 'directoryname/subdirectoryname': folder does not exist.

The folder does exist. When I examined the filters.xml file, I observed that Evolution is inserting an incorrect wrong folder URI. When I manually replaced the URI with a correct one, the filter functioned normally and generated no errors.

This is what evolution put in the filters.xml:

 <folder uri="email://local@local/directoryname/subdirectoryname"/>

This is what I put in that actually works:

 <folder uri="maildir:/maildirpath/directoryname/subdirectoryname" />



Steps to reproduce:
1. Right click on mailing list email
2. Select "create rule from message -> filter based on mailing list'
3. Select move to folder and pick folder
4. Manually apply the filter to a message


Actual results:
Evolution generates error message and does not move the email to the correct folder.

Expected results:
Evolution should move the email to the correct folder without displaying an error message.

Does this happen every time?
Yes, 100% of the time.

Other information:
Comment 1 Milan Crha 2009-11-24 19:14:35 UTC
Thanks for the bug report. There were quite many iterations on bug #552583 to get this working properly for all the providers, but it's fixed finally. The bug covers this one as well, thus I'm marking it as a duplicate.

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