Milter-greylist

On Thu, Nov 23, 2006 at 09:13:36AM +0100, manu@... wrote:
> rcpturl "level 1" "http://www.foo.net/gr.php?rcpt=%r" "level1"
> rcpturl "level 2" "http://www.foo.net/gr.php?rcpt=%r" "level2"
> 
> acl greylist rcpturl "level 1" greylist 15m
> acl greylist rcpturl "level 2" greylist 1h 

While I think about it: delegating the decision to a web middleware
does not have to be done only on the recipient address. We could immagine
adding various information to the quesry such as sender IP, sender e-mail
and so on. 

If we introduce racl (evaluated at RCPT stage) and dacl 
(evaluated at DATA stage), we can even imagine sending the message body 
using a POST request.

Such a feature seems to allow much more flexibility than just a recipient
lookup in a LDAP directory, a SQL database, or whatever. 

The syntax would look like that:
urlfilter "level 1" "http://www.foo.net/gr.php?rcpt=%r+ipaddr=%a" "level1"
urlfilter "level 2" "http://www.foo.net/gr.php?rcpt=%r+ipaddr=%a" "level2"

acl greylist urlfilter "level 1" greylist 15m
acl greylist urlfilter "level 2" greylist 1h

In the urlfilter statement, we could use:
%r recipient e-mail
%f sender e-mail
%a sender IP
%d sender DNS name
%mfoo sendmail macro foo's value

Opinions?

-- 
Emmanuel Dreyfus
manu@...