Karthik wrote,
| The following recipe does not work as I think it should.
|
| ==
| :0 Whb: spamprobe.lock
| SCORE=| $SPAMPROBE receive
|
| :0 wf
| | $FORMAIL -I "X-Label: $SCORE"
| ==
| Instead I get the following in the logfile.
| procmail: Out of memory
| buffer 0: "/home/karthik/bin/spamprobe"
| buffer 1: "SPAMPROBE"
| The same happens even if I put
|
| SCORE=| echo SPAM
|
| echo will run without needing swap space (I think). top shows plenty of
| swap free.
My first guess is that you're running a version of procmail where, on some
platforms, variable capture recipes always overflowed. The workaround was to
avoid the variable capture syntax. You have to use a regional lockfile
instead of a local one, but since you have no conditions on your variable
capture recipe, you don't need braces:
LOCKFILE=spamprobe.lock
SCORE=`$SPAMPROBE receive`
LOCKFILE
| Another question - since the Folder is listed as **Bounced**, does it
| mean that the spammer will get a message saying that the message cannot
| be delivered?
No, because,
1. There is no telling from just procmail's logging "**Bounced**" whether an
NDN was sent or not.
2. If an NDN was sent, it went to the envelope-sender address, which on almost
all spam is forged.
So maybe a non-delivery notification was sent or maybe not, but either way I
can tell you with confidence that the spammer will not receive one.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail