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 252473 - define a filter that will apply only to messages in one or more specific folders
define a filter that will apply only to messages in one or more specific folders
Status: RESOLVED DUPLICATE of bug 227536
Product: evolution
Classification: Applications
Component: Mailer
1.5.x (obsolete)
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[filters]
Depends on:
Blocks:
 
 
Reported: 2003-12-23 03:58 UTC by Larry Siden
Modified: 2011-02-21 10:46 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Larry Siden 2003-12-23 03:58:24 UTC 
I would like to be able to define a filter that operates only on messages
in one or more particular folders and that have achieved a certain age. 
For example, I might like to create a filter that periodically scans my
Sent folder and deletes all message that are older than 7 days.  Another
example: create a filter that pipes all messages in my "Spam" folder thru
"spamassassin -r" that will report these messages to a server (e.g. Pyzor's
server) in order to tune its spam filter.
Comment 1 Gerardo Marin 2004-02-10 17:25:06 UTC 
Do not file bugs here. Use Evolution product instead
Comment 2 Karsten Bräckelmann 2006-03-30 14:10:11 UTC 
The first part definitely is not Filter, but vFolders (now named Search Folders) and already possible. Just create a new vFolder, select specific sources, and limit it to mails older than x days. This vFolder now *always* shows these old mails, and you can get back to it for clean-up whenever you got some time. :)

The second one... Well, is a request to watch an arbitrary mail folder fo rnew mails, I guess. Hmm.
Comment 3 Akhil Laddha 2011-02-21 10:46:02 UTC 

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