On Sun, 10 Feb 2002, Professional Software Engineering wrote:
If you're filtering like this - lists before spam - then the lists that you
match are being DELIVERED to the specified folders and PROCESSING
STOPS. If you use 'c'opy flags, then the one copy is still delivered and
another one continues to be processed - but that won't have the desired
effect here (since it won't REMOVE the spam). 'f'ilter recipes can be
useful - where you add a header to the message tagging it as being destined
for some certain folder, then still subject it to other filters, but you
could just as easily move the spam filters to before the list filters in
that case and achieve the end result with much less work.
Sean,
I don't follow this.
When a list message comes in, I want it delivered to the appropriate
folder and have processing stop for that message. If a spam message comes
in, I want it to pass though the mail list recipes ("no match on ...") but
be trapped by one of the specified spam recipes.
I must have missed something in the procmail docs I've read for I don't
understand where I have 'c'opy flags rather than 'f'ilter flags. Your
examples are what I'm doing, and I understand the recipe order is critical.
Don't I want to have the acceptable mail sorting done before it has to be
compared with every spam recipe?
Many thanks,
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) |
rshepard(_at_)appl-ecosys(_dot_)com
http://www.appl-ecosys.com
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail