Milter-greylist

On Wed, May 26, 2004 at 11:46:10AM +0200, Cyril Guibourg wrote:
> > This could be implemented by doing a gethostbyaddr() on the sender IP 
> > address and checking the enaswers (primary address and aliases) against
> > the regex. That does not look very complicated, but I suspect we can run 
> > into DNS resolver thread-safety and performance slowdown because of DNS 
> > lookups. Maybe this should be dealt after 1.4
> Imho this could end into another issue if for some reason reverse resolution
> is broken for a while (NXDOMAIN ?) how would whitelist code react then ?

It would just not whitelist, and the message would go through greylisting.
Not something really horrible.

> > More ideas? Opinions? Thoughts? 
> 4) Per (virtual-)domain config ?

Oh, yes, good idea. In fact, per-user config could be made more general:
per recipient config, where the recipient can be given as a regex. That
way you can give a domain if you want.

That's something for releases beyond 1.4: too intrusive. But we can 
still discuss the user interface. What about this?

rcpt /.*example\.com$/ {
	lazyaw
	report none
	autowhite 3d
}

One problem to solve: how to handle multiple matches?

-- 
Emmanuel Dreyfus
manu@...