GNOME Bugzilla – Bug 227536
Add "Message Location" filter option
Last modified: 2015-06-22 10:08:15 UTC
Package: Evolution Priority: Normal Version: 1.0.3 Synopsis: Would like to be able to attach filters to specific folders Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Description: I'd like to be able to create filters that apply to specific folders, and which are run periodically. In particular, I would like to be able to create a filter that automatically deletes/expunges messages from a folder after than are more than X days old. This would be particularly useful in the "sent" and "trash" folders. Unknown reporter: jimf@frostbytes.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Yes! Or at least have a "apply filters to all folders" option instead of just inbox. I use maildrop filters to file away my incoming mail on an imap server, and I'd like Evolution to be able to colorize certain new messages in those folders.
This is a very similar request to bug 222179 (Request for Feature: manual vs. automatic filters)
*** bug 245277 has been marked as a duplicate of this bug. ***
adding keywords
related to bug 263621
reassigning jpr's old evolution\miscellaneous bugs to harish
updating version number, still missing in 2.5. lowering priority, sorry.
Bumping version to a stable release.
*** Bug 252473 has been marked as a duplicate of this bug. ***
I've added "Message Location" filter option, thus one can create filters with conditions like: [ Message Location ] [ is ] [ IMAP/Inbox/test ] [ and ] [ Sender ] [ contains ] [ Bob ] do Action [ Move To ] [ IMAP/Inbox/Bob ] which may cover the requested functionality. Created commit e6b3f2a in eds master (3.13.3+) [1] Created commit 402d1f1 in evo master (3.13.3+) [2] [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=e6b3f2a [2] https://git.gnome.org/browse/evolution/commit?id=402d1f1
*** Bug 695461 has been marked as a duplicate of this bug. ***
*** Bug 502351 has been marked as a duplicate of this bug. ***