Milter-greylist

At Thu, 23 Nov 2006 10:01:56 +0000,
Emmanuel Dreyfus 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?

Programmers will prefer hacking milter-greylist itself to implementing
such a glue mechanism. Though PHP programming will be easier than C,
programmers still need to take much care of security and error
handling.

The more declarative, the easier. Plugin mechanism is not for simple
programs such as milter-greylist. LDAP filter is enough flexible for
most cases.