Kevin Myers followed up,
| When I look again, it seems to be just this syntax that triggers them:
| SENDER=|$FORMAIL -b -rtzxTo:
(-b isn't going to do anything without -k, but let's continue ...)
| which happens everytime in the sandbox, and when I took that out:
| MESSAGE=| sed ':a;N;s/^\n//;s/[\n ]\{1,\}/ /g;ta;' | head -c 134
| which happens whenever the message is UNDER 5000 bytes.
Do you have any variable capture recipes that don't give the Out of Memory
error, Kevin? On one BSD system where I have a shell account, I can't use
variable capture recipes at all, because they always fail with Out of Memory
errors. Backtick assignments work. Thus,
:0
* conditions
VARIABLE=|command
bombs but
:0
* conditions
{ VARIABLE=`command` }
[or just VARIABLE=`command` with no :0 and no braces if it's unconditional]
works properly. That's with both 3.22 and 3.23pre, and I've been meaning to
write about it here for the longest time.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail