GIVEN THAT, when the Postscreen internal SMTP engine is invoked, the decision to reject the message has already been made; It seems to me that this is an opportunity to tar-pit the (bad) remote host, diminishing spam throughput, and eroding the host's useful life-span.
I SUGGEST, therefore, that an additional "TAR-PIT" option be added to the list of available postscreen_mumble_action's. I envisage this as being the same as "ENFORCE", but with an added delay. It would be very nice if the tar-pit action could be invoked from within the Postscreen access control lists, but I appreciate that this could disrupt stable and well-tested code. I would be interested to hear what others make of this idea. Allen C
