358683 - Thunderbird custom filters could use asterisc (*) as wildcard and/or regular expressions to get more powerfull...

Status: RESOLVED DUPLICATE of bug 19442

(Thunderbird :: General, enhancement)

Description

[Sergio]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; pt-BR; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; pt-BR; rv:1.8.1) Gecko/20061010 Firefox/2.0

It's hard to understand how thunderbird - which is an open source project - doesn't use the power of Regular expressions, or AT LEAST wildcards to allow efficient custom filters.

Every day, spammers change little things in the strings sent, so
viagra, v1agra, v'agra and v|agra  could be caught if the custom filter where more powerfull.

For instance... v*gra or /v.gra/ could catch all those strings above... if that feature were added to TB filter function.

Ok, TB has a native spam filter, but those CUSTOM filters can make the task even better... 

When do you plan to work on it ? Because the way it is, the well known "proprietary mail software" is winning in this point...

I know some C programming (not an expert, just an average) and I have already suggested a fluxogram for the changes, some time ago... I don't know if any TB developer got in contact with that image. 

When I looked into the source files, I got to the function where it is done, and designed a fluxogram that shows my suggestion to improve this custom filters, or it could guive some new ideas to the active TB developers. Please, check out the fluxogram:

http://img100.imageshack.us/img100/6944/thunderbirdsuggestionca0.gif



Reproducible: Always

Steps to Reproduce:
1. Write a filter using * as wildcard ex: t*st for the subject
2. Send an e-mail to yourself with this subject: test
3. See that the filter doesn't catch it.

Actual Results:  
the filter ignores the e-mail

Expected Results:  
When we have this feature, the e-mail would be caught by the filter

It is a new feature request, not a bug.

Comment 1

[Magnus Melin [:mkmelin]]

Nobody just implemented it yet;)

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