Re: procmail keeps running out of resources?
Jason Welsh <jason-fYJcuH/[email protected]> Tue, 26 Apr 2011 16:15:38 -0400
| Newsgroups | gmane.mail.spam.crm114 |
|---|---|
| Message-ID | <[email protected]> |
> No, that looks like a good trace so far. > > The real question is what happens at the other end, when > CRM114 exits. Does it exit ordinarily, or in some abnormal > way? Found that variable Checking restriction at start 20 len 0 (subscr=0) Nothing more to do in the var-restrict. match pattern expands to =yes= len 3 flags 1 0 Regex did not match, no absent flag, failing. Parsing line 1206 : --> } Executing line 1206 : Statement 1206 is a closebracket. depth now 0. Parsing line 1207 : --> :exit_here: Executing line 1207 : Statement 1207 is non-executable, continuing. Parsing line 1208 : --> exit /:*:our_exit_code:/ Executing line 1208 : Exiting at statement 1208 with value 0 jason@beast /tmp $ so I guess exit with vlaue 0 is a good thing.. so I ran this manually on 2 "spam emails" that got through with cat "/tmp/spam/cur/1303822956.24487_1.beast:2,Sa" | crm114 -t -u ~/.crm mailfilter.crm and they both exit 0 but im sure that crm or procmail choked on it with procmail: Program failure (-25) of "/usr/bin/crm" and there were no X-CRM114 headers on the email. Jason ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd