On 6-Sep-07, at 11:33 AM, Johan Almqvist wrote:
My idea would be that there are only two things that can be
whitelisted: connections and transactions. On the base of what
logic, and at what stage, is up to the plugin, but if the whitelist
flag is set, any DENY* return value from subsequent plugins' hooks
should be treated as DECLINED.
The way I see it is that whitelisting is basically meant as a bypass
for anti-spam filters, but not (for example) certain other filters
(like recipient checks). So I wondered if hooks should declare
themselves as skippable if whitelisted, via sub attributes:
sub hook_helo : skip_if_whitelisted {
...
}
Or something like that.
