No, this is not what I want. I want sb.rc to "fall through" instead of just depositing the BLOCKed mail. I.e., when I do: INCLUDERC=sb.rc I want to put stuff afterwards, such as: :0w *^x-sbclass: blocked { :0: *B??keyword1 $DEFAULT :E /dev/null } Again, this may (it looks like it would) involve a change to sb.rc. In fact, my proposed change is from: :0: * BLOCKTAG ?? yes | ${FORMAIL} -A"X-SBClass: Blocked" >>${BLOCKFOLDER} To: :0f * BLOCKTAG ?? yes | ${FORMAIL} -A"X-SBClass: Blocked" :A: *!BLOCKFOLDER??^$ $BLOCKFOLDER See? > From: http://www.hrweb.org/~ariel (Catherine Hampton) > Date: Mon Aug 24, 9:28am > > If you just set BLOCKFOLDER=${DEFAULT}, that will send all blocked email > back into your main mailbox, but with the Blocked: header intact. > > Catherine > > > I have a semi-unusual request. Is there a way to trap (& trash as appropriate) > > spam messages, but pass through blocked mail? What I mean is that currently > > if I set BLOCKFOLDER, blocked mail will go in there and the invocation of > > procmail will terminate. What I would like instead is to, say, set > > BLOCKFOLDER to "" and have it only mark the message with "X-SBClass: Blocked" > > and fall through to the rest of my .procmailrc script so that I can process > > it further. > > > > Can this be done with the current implementation of sb.rc? If not, would > > you be willing to add such a feature? > > > > Thanks.