Forum

Hello,

There are some messages I receive that are necessary for me to keep for a week or so, others for a month or so, but after that they can be deleted. Because I don't want to delete them when they arrive in my inbox, I realize this is the kind of filter I would need to manually run. (Maybe there's a way around doing it manually that i don't know about?)

I would envision a new filter type called something like, "date is older than" with two other selection criteria: a text box where I can type in a number (whole number only), and a dropdown list of choices for "day(s)", "week(s)","month(s)", "year(s)".

As an example, I could create a filter that said:

date is older than | 1 | week(s)

Also, despite my (gentle!) harassing of some site administrators :D I do get emails that sometimes lack a "Date:" header. I image that having the filter parse the most recent (top) "Received:" header would be very difficult, so I'd rather the filter just skip emails with no "Date:" header.

The standard filters have the "Age in Days" field which would seem to
suit your needs. What is wrong with that field for you use?

Doh! Man do I feel stupid. My face sure is red. How long has that ability been in TB and I've never noticed it? (That's a rhetorical question.) :D Sheesh.

I'm curious about something you wrote, though:

What you are describing is not really a custom filter, but a custom
extension. That is, you want a specific screen to appear that you can
select buttons on. Filters do not normally have a user interface like
that. If you wanted to do this with a filter, you would have separate
filters that you would select and run using the normal filter list
editor interface.

I must have used the wrong terminology when I described the feature request. To me the user interface already exists. When I create a brand new filter, the default "match" option is "Subject" and it has a dropdown list field defaulting to "contains" and a field to the right that allows typing freeform text. I was envisioning exactly the same kind of thing when I described this (unnecessary!) feature request.

You wrote, "Filters do not normally have a user interface like
that." What I'm wondering is how I "should" have described this feature request so that it didn't sound like I was asking for a different user interface?

Apologies again for wasting your time asking for a feature that already exists in TB.