Re: Procmail 3.22 running out of memory

Tony asked about my suggestion to Michael,

|  Why not simply have the "trigger" on the outside, like it is, and then do
| ":0b" (or whatever it is you want) inside it... ie a second recipe?

Please give an illustration, Tony.  The problem I had (and which I'm guessing
Michael has) is that procmail gets an out-of-memory error from this:

 :0
 * conditions
 VARIABLE=| command

and I said that one could usually work around it by coding this way:

 :0
 * conditions
 { VARIABLE=`command` }

but that if the original had a `b' or `h' flag (but not both), it gets messy.
Your post sounds to me as if you were recommending this to ease the
messiness, using `b' for the example:

 :0
 * conditions
 {
   :0b
   VARIABLE=| command
 }

or this:

 :0
 * conditions
 { }
 :0Ab
 VARIABLE=| command

If Michael's problem is the same as mine, neither of those will help.  When I
was tangling with the problem on a NetBSD machine, procmail choked on
unconditional variable capture recipes just as on conditional ones.

If that isn't what you meant, please illustrate.



_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail