This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

* not working as wildcard in filter

  • 3 جواب دیں
  • 3 میں یہ مسئلہ ہے
  • 8 دیکھیں
  • آخری جواب بذریعہ Inperfect

Rufis.T.Farnsworth
Rufis.T.Farnsworth
more options

I have filter rules set up that run as "Manually Run" and "Getting New Mail: Filter before Junk Classification", - are of type "From is ..." and - the actions are "Move Message to ... (certain Local Folders)."

Before the latest update, sorry, not sure of version, didn't use Thunderbird that much and still learning, I had rules set using the following *@net.com. Well the star worked fine as a wildcard but since the update to 54.0b3 (32-bit) Beta it seems that the wildcards are completely nonfunctional. Any help is appreciated, thanks in advance.

I have filter rules set up that run as "Manually Run" and "Getting New Mail: Filter before Junk Classification", - are of type "From is ..." and - the actions are "Move Message to ... (certain Local Folders)." Before the latest update, sorry, not sure of version, didn't use Thunderbird that much and still learning, I had rules set using the following *@net.com. Well the star worked fine as a wildcard but since the update to 54.0b3 (32-bit) Beta it seems that the wildcards are completely nonfunctional. Any help is appreciated, thanks in advance.

منتخب شدہ حل

I don't think the star wildcard has ever worked. We use "contains", "starts with" and "ends with" instead.

The FiltaQuilla addon will give you regular expressions in certain header fields.

I wonder why, as a self-declared novice, you are using a pre-release beta version of Thunderbird? These are provided for experienced users allowing them to test upcoming versions.

اس جواب کو سیاق و سباق میں پڑھیں 👍 1

تمام جوابات (3)

Zenos
Zenos
more options

منتخب شدہ حل

I don't think the star wildcard has ever worked. We use "contains", "starts with" and "ends with" instead.

The FiltaQuilla addon will give you regular expressions in certain header fields.

I wonder why, as a self-declared novice, you are using a pre-release beta version of Thunderbird? These are provided for experienced users allowing them to test upcoming versions.

Zenos کی جانب سے میں ترمیمکی گئ

Rufis.T.Farnsworth
Rufis.T.Farnsworth سوال کا مالک
more options

I have reworked my filters and as far everything seems to be working fine. The funny thing before the last update to this last update to the beta version the "*" filters worked, and a few still do, but the "contained" seems to works better and faster.

No idea how I wound up with the beta version but I'm going to check the settings and try to adjust them.

Thanks for the help.

Inperfect
Inperfect
more options

For me it worked to use "" (two double commas) instead of * or "*", but I know it was a lucky strike, since it is not working as a wildcard or unknown name placeholder.

What I wanted to do is to find an attachment with an unknown number on it (querry was: "Your invoice N "".pdf") and it performed a "Search Your invoice N and .pdf" and it returned to me all mails with this attachment name, but also others that didn't matched the record.

What is supposed to be the expression used for * in this case? "contains", "starts with" and "ends with" doesn't work well.

FiltaQuilla addon is not supported on newer version 52.

Inperfect کی جانب سے میں ترمیمکی گئ