On Wed, 5 Apr 2006, Dallman Ross wrote:
Maybe so, but you want your algorithms to be bug-free, as opposed to bug-
ridden. :-)
Like Windows? :)
Would * ()\/^Subject.* work? at least for the blank or whitespace only
versions? I'm not sure I understand about capturing the subject in a
prior recipe - or maybe you don't understand what I want to wind up with.
Here's a brief excerpt from the "spam.log" from the last couple of
fetchmail sessions:
060404:2057 : return-path address begins with _bounce_ : LinuxWorld Buzz:
Is Virtualization Ready $
060404:2057 : message-id assigned by raq2 server
: Gas Prices Soaring - Get Gas on us Teachout, Ph$
060404:2057 : foreign charset : Chase Online-Get $20 Reward Survey
060404:2057 : message-id assigned by raq2 server : Costco now offering
Health Insurance to Members
060404:2057 : not To/CC me or wife : re [4]
060404:2057 : message-id assigned by raq2 server : Ratess approved
060404:2057 : foreign charset :
=?iso-2022-jp?B?GyRCPVBEJSVbJTklSCEqSj82UTx9Rn4bKEI1Ny42GyRCS3wbKE$
060404:2058 : To contains code : Software At Low Pr1ce
I can sort this bye date:time (not likely), recipe description (usually)
or by subject (If I think there might be a valid message in here
somewhere)
I'm sorting out those recipes I can run right after the backup recipe and
those that I have to wait until after the lists get pulled to trash.
There's no sense running trash through any more recipes that absolutely
necessary.
- fleet -
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail