Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

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.

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.

Learn More

Is it possible to use regular expressions when creating an email filter?

I want to move to the folder all the letters for which the header has a certain format. For example:

The regular expression for these headers will be:

  • \[(.*)\](.*)
  • \[(.*)(example\.com|example\.net)\](.*)

The second option will exclude the movement of some letters that do not match the regular expression.

I want to move to the folder all the letters for which the header has a certain format. For example: * [promo.example.com] My first message * [example.com] My second message * [foo.example.net] Third message * [bar.foo.com] Foo bar baz The regular expression for these headers will be: * \[(.*)\](.*) * \[(.*)(example\.com|example\.net)\](.*) The second option will exclude the movement of some letters that do not match the regular expression.

Modified by user240250747203422110146690518486743534925

All Replies (4)

For some reason, there is no line break in the question ...

And regex:

  • \[(.*)\](.*)
  • \[(.*)(example\.com|example\.net)\](.*)

The FiltaQuilla add-on (for TB 60 and lower) allows regex for searches, but not for filter actions. I'm not aware of any way to apply regex to message filters in TB 68. See if you can accomplish the same result using e.g. From contains example.com, or possibly create filters for custom headers.

This extension is not compatible with the installed version. I am using 68.2.1, and the extension works with version 60 and below.

Now this rule works for me (see screenshot)