advenge server ha(s|d) a headers-all-in hook when the data block switched from header to body. Sometimes the message would fail at that point and get handed to a very lightweight state that simply threw everything away until the dot arrived then issued a policy 550. Sometimes the message would pass at that point (magic phrase in subject) and we could skip the later parsing of the whole message, treating the OK message as OK for relay from that point, even going so far as to open an outbound connection for it. (as advenge server was a relay.)
Sending the whole header block instead of every line as it comes means fewer calls and simpler architecture for the plugin -- no internal per-message state. Hook response language should include TARPIT and DROP as well as the various sorts of DENY. On 5/1/06, John Peacock <[EMAIL PROTECTED]> wrote:
I've been toying with the Mail::DomainKeys and Mail::DKIM modules and they both want to have all of the data lines, which is going to get wasteful (performance-wise) really fast. Would it be reasonable to create a new data_lines hook which would receive each line as it was received? The existing data hook would fire off a copy of the line to each registered data_lines plugin, which could return:
-- David L Nicol The best way to predict the future is to invent it (Alan Kaye)
