Hi Roelof,
Le lundi 29 juin 2009 à 12:50:31, vous écriviez :
> My suggestion would be to add all list addresses to a single address
> book group and and check whether the To header is part of that AB
> group.
> And forget about 'continue processing with other filters', that's not
> necessary here, neither in the parent nor in the sub-filters. What the
> 'continue...' option does, is taking care that after a message
It could be necessary for the parent filter... example...
You have an email address (alias) dedicated for mailing lists. In your above
example, the first rule would then be to know if a message has been sent to
this specific email address, and then classify every different mailing list
with different sub-filters... so it's clean : you will not trigger a lot of
sub-filters for emails sent to your main address.
But : sometimes you may have someone from a list replying privately to your ML
address : you may prefer that this message is processed by your other filters
for "outside ML messages", like for sample flagging mails coming from peoples
in your address book..
In that case, it will be :
Filter : Lists
Condition : sent to your list address
Continue other filters
Subfilter : list one
Condition : ...
Do not continue other filters
Subfilter : list two
Condition : ...
Do not continue other filters
With this scenario : if a mail catch the first rule but not any subfilter, then
the filtering should continue.
> Off hand I can't think of any example where using 'continue
> processing' isn't contra-productive.
Two rules : one to flag messages coming from known peoples (from AB) and
another to move messages according some keywords... those two rules are not
exclusive each other : the first rule should not stop parsing the second rule...
--
Cordialement,
Stephane courrier : [email protected]
________________________________________________
Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
