[prev in list] [next in list] [prev in thread] [next in thread]
List: procmail
Subject: Re: procmail->formail->procmail [solved]
From: Chris Cera <chris () cera ! us>
Date: 2006-12-10 0:06:18
Message-ID: 20061210000618.GF26080 () psico ! hsd1 ! pa ! comcast ! net
[Download RAW message or body]
gkreme,
Thank you very much for your prompt feedback. My problem was
that I thought a pipe caused procmail to stop processing the
remaining rules. I was trying to workaround this non-existant
issue. My main problem seems to be solved now, and I cleaned up
the locks and gratuitous copies as well. Thanks for your
additional commentary as well, it was very helpful. -Chris
* Google Kreme <gkreme@gmail.com> [061209 18:08]:
>On 9-Dec-2006, at 15:33, Chris Cera wrote:
>> Here is the recipe, the problem is that formail does not send the
>> resultant
>> mail back to procmail for processing, it just delivers it to my
>> default
>> mailbox.
>
>No it doesn't. formail doesn't deliver mail.
>
>> I would like it to come back into procmail so the first rule can
>> catch it,
>
>No. procmail runs through rules in serial order. Period.
>
>> copy it to the default mailbox, and drop it into the spam_despam
>> mbox file. Any help is greatly appreciated, and I am certainly
>> all-ears for a better way of achieving this. -Chris
>
>Er.. obviously more is going on here. When is the subject getting
>tagged, only after you check for it?
>
>> :0c
>> * ^Subject:.*\[despammed]
>> $HOME/mail/spam/spam_despam
>
>"Take a copy of the message (so two messages now), and if it has
>"[despammed]" anywhere in the Subject, save it in the spam_despam
>mbox." BTW, you need a lock.
>
>> :0Wci: pm_despam.lock
>> | $HOME/bin/despam
>
>Take ANOTHER COPY (three messages now) of the message, and whilst
>ignoring all errors, pipe it to despam.
>
>> # despam failed, mark it as spam
>> :0e fh w
>> * ^Subject:\/.*
>> | formail -I "Subject: [despammed]$MATCH"
>
>If despam failed, then feed the header to the pipe, and wait for
>completion, add "[despammed]" to subject. Two unmodified messages
>fall to default, or one modified and two unmodified if despam didn't
>fail, depending on what dpsam does with the message it gets piped.
>
>Now, how can the first recipe ever see the tag? And when this
>process is finished, you will have three copies of the message...
>
>
>I don't understand what you are trying to do with these subject tags,
>or why you think it makes sense to check for a subject tage before
>you could possibly apply it, or why you want to resubmit a message
>tot eh start of your procmailrc, where you would then end up with SIX
>copies of it instead of just three.
>
>
>
>--
>Look, that's why there's rules, understand? So that you *think*
>before you break 'em.
>
>
>____________________________________________________________
>procmail mailing list Procmail homepage: http://www.procmail.org/
>procmail@lists.RWTH-Aachen.DE
>http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
--
Chris Cera http://cera.us
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail@lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic