04-03-2026
09:54 AM
- last edited on
07-04-2026
07:30 PM
by
wsm
I have one email account that is over 20 years old and gets about 300 to 400 spam messages per week (I clear each trash folder a few times a week). I do not use the SPAM mail feature because it really doesn't work well. Instead I use the Message Filter feature to just send the spam emails directly to the trash folder BEFORE the spam filter analysis' the message (Manually run, Getting New Mail [Filter before Spam Classification], Match any of the following, From, contains, website address). My filter has around 300 entries in it at this point. I shorten the offending email address`(ie: spammer@website.com) to just the website (ie: website.com) in order to automatically trash all emails from the spammer website. The problem is that the Message Filter application has been set at such a low priority that data entry lag time is anywhere from 15 to 60 seconds between mouse clicks/keystrokes when adding a new entry (I add 1 to 5 entrys per session a few times per day). So slow that sometimes it stops working entirely requiring you to exit out of the message filter application and reentry. Cannot stack keystrokes because the Message FIlter Application cannot process the keystrokes (excessive lag time) and essentially crashes. I would really appreciate it if the Message Filiter application to remove this excessive lag time. Additionally, because the spammer communty loves free gmail accounts I have been considering adding "gmail.com" to my list given the excessive number of spammers that use gmail accounts (from email field). For gmail spammers I add the complete scammer email addess rather than just the website address (ie: qwertyuiop@gmail.com vs just gmail.com)
Thanks - Dave
07-04-2026 07:29 PM
This website, Connect, is primarily for posting of feature ideas. When seeking support for problems, the best place to ask is https://support.mozilla.org/questions/new/thunderbird
To best assist you, please consider the items at https://wiki.mozilla.org/Thunderbird:Testing:Memory_Usage_Problems before posting your support issue.