On Wednesday, January 5, 2005, 02:23, Thomas Fernandez wrote: BA>> Yes, I can confirm this behavior, but can't say whether this is a BA>> bug or wanted. But I think this is wanted, because if a filter BA>> matches a message, filtering stops (if not [X] Continue processing BA>> with other filters is set).
> I just tested it and it works as you described on my home computer. > However, this is not what I want. When the first common filter > catches, I don't want the other 100 or so common filters tested. > simply because it takes minutes and on occasion, makes TB choke on it > (tried it). Create a parent filter matching all messages and make your common filters subfilters of this catch-all-filter. Make sure "Continue processing with other filters" is ticked for the parent filter. When a filter matches, TB! should stop processing filters within the same sub filter group but continue through other filters below the parent filter. I have not tested this with common filters, but it works with account level filters and it seems to be exactly what you want. -- Regards, Marcus Ohlstr�m Using The Bat! v3.0.1.33 on Windows 2000 5.0 Build 2195 Service Pack 4 PGP Public Key at http://www.canit.se/~marcus/pgp.asc ________________________________________________________ Current beta is 3.0.2.10 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
