Milter-greylist

On Thu, 2006-11-23 at 09:13 +0100, manu@... wrote:
> 
*snip*
> 
> An alternative: assume the site already has some web machinery as a
> front end for its user database, and that a CGI can give the
> information. That would give something like that:
> 
> 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 
> 
> So when we have a mail for bar@..., we query
> http://www.foo.net/gr.php?rcpt=bar@... and depending on the string
> we get back, we can apply different ACL. 
> 
> That's much more simple than the LDAP stuff, but one must have a web
> middleware to handle it. I'm not sure that's a better path.
> 

I'd vote for HTTP approach as it gives you a single interface to
virtually unlimited types of data sources behind it.

I'd also include in rcpturl the "%s" for the sender part, so as to allow
the user to specify e-mail addresses or wildcards for which it does not
want to have the greylisting in place.

R.