Milter-greylist

AIDA Shinra <shinra@...> wrote:

> Sorry, I meant a monolithic file which is similar to /etc/passwd
> (or /etc/aliases).
> 
> * It can be parsed by only fgets() and strtok().
> * It can be edited by a machine without breaking comment lines.
> * No macro nor ifdef nor wildcard.

Well, that does half of the work, since we still lack a way of having
users modifying it. The point with using a directory is that there are
tools already available for that. Moreover, using a local file means
sync issues if you have multiple MX.

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.

We can also immagine querying the DNS, a la Hesiod.

I'm not sure of the best way to go.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...