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 319479 - Evolution filtering error messages difficult to understand
Evolution filtering error messages difficult to understand
Status: RESOLVED DUPLICATE of bug 525932
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[filters] aklapper[errormess...
Depends on:
Blocks: 502515
 
 
Reported: 2005-10-22 14:42 UTC by Javier F. Serrador
Modified: 2012-12-03 15:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Javier F. Serrador 2005-10-22 14:42:04 UTC
Have a filter that moves a mail to a folder in an imap account

Delete that folder on the imap server using other means, so that your filter
doesnt get updated and still believes there is such a folder.

The error message that is shown to the user is unintelligible. It should say
that  the filter called "<filtername>" tryes to move/copy to an unexistant
folder, and should offer button to correct that filter automatically or edit
filter from the popup.




I
Comment 1 André Klapper 2005-10-22 22:14:23 UTC
adding keywords
Comment 2 Subodh Soni 2005-11-08 09:10:47 UTC
Confirming the bug.
Comment 3 André Klapper 2005-11-27 23:45:40 UTC
changing status whiteboard term to keep namespace consistency.
Comment 4 André Klapper 2012-02-20 13:17:53 UTC
What IS the current error message that you get? Would be nice to mention in the bug report so it can be searched for...
Comment 5 Milan Crha 2012-12-03 15:36:17 UTC
I just changed this in bug #525932, thus I'm closing this as a duplicate of it. It only changes the error text, it doesn't know exact filter and such, just that one of them can be wrong.

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