Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

* not working as wildcard in filter

  • 3 svar
  • 3 har detta problem
  • 8 visningar
  • Senaste svar av 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.

Vald lösning

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.

Läs svaret i sitt sammanhang 👍 1

Alla svar (3)

Zenos
Zenos
more options

Vald lösning

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.

Ändrad av Zenos

Rufis.T.Farnsworth
Rufis.T.Farnsworth Frågans ägare
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.

Ändrad av Inperfect