Brad Alpert wrote: <snip>
> What I am concentrating on is the failure of my ^Subject.*Test > condition. The /var/log/procmail log shows that the condition isn't > catching a message sent to myself with the subject line as "Test". Is this a global rule or a user rule? > Any ideas of why procmail, when invoked, won't catch the condition? The > current test is - > > :0: > * ^Subject.*Test > spam Try simplifying the test with :0 H:. No sense in searching the entire message when what you're looking for is in the Subject. Probably unrelated, but it would reduce the load a bit on larger messages. Are you looking for everything Test in subject? If not - be more specific with: :0 H: * ^Subject: Test spam or if you're looking for test then what you had is fine: :0 H: * ^Subject:.*Test spam > Procmail's response to that is - > > procmail: [6613] Sun Nov 17 13:51:10 2002 > procmail: Match on "< 256000" > procmail: Executing "spamassassin" > procmail: [6613] Sun Nov 17 13:51:13 2002 > procmail: No match on "^X-Spam Status: Yes" > procmail: No match on "^Subject.*Test" Odd indeed. Can you post the headers from the "test" message? > procmail: No match on "^Sender: [EMAIL PROTECTED]" > procmail: No match on "^From:.*21cn.com" > procmail: No match on "^Subject: .*out of (the )?office" > procmail: Assigning "DROPPRIVS=yes" Not relevant to your search, but why assign this later and not at the top of your recipe? Spamassassin loves to be the user so it can process user base rules as well. -Rick -- Rick Johnson, RHCE - [EMAIL PROTECTED] Linux/WAN Administrator - Medata, Inc. (from home) PGP Key: https://mail.medata.com/pgp/rjohnson.asc -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
